Repository navigation
Abyss v1.3.0
Highlights
- Add configurable HTTP CONNECT upstream proxy chaining for explicit-proxy traffic. The next hop resolves target hostnames, and connection failures do not fall back to direct access.
- Preserve the existing client-to-Abyss and Abyss-to-target TLS trust behavior through the proxy tunnel.
- Add native OpenCode detection, session attribution, and tool/conversation capture across supported provider protocols.
- Improve proxy diagnostics and DSH token accounting when retry results omit cache breakdowns.
Rust integration migration
Rust integrations using abyss-mitm may need source changes:
FlowContext.original_destination,InterceptedHttpOutcome.original_destination, andTransparentPassthroughOutcome.original_destinationnow useDestinationAddress. Itssocket_addr()returnsOption<SocketAddr>because target resolution can belong to the next-hop proxy. Handle an unknown target address explicitly.- Constructing
FlowIngress::ExplicitProxynow requiresupstream_proxyandproxy_endpoint; useNonefor direct flows. Existing destructuring patterns can use..to ignore these fields. - Existing flow constructors and
with_prepared_upstream(TcpStream)remain available. The AgentEvent plugin protocol is unchanged.
Downloads
The release includes macOS ARM64 and Linux x86_64 CLI archives in default and no-local variants, a Windows x86_64 runtime ZIP, the installer, and SHA-256 checksums. The broker, Rust SDK, query CLI, and supporting crates are also published to crates.io.
Full changelog: v1.2.2...v1.3.0