Machine connection
A bounded request, stream and close contract. It does not know whether bytes travelled through HTTPS, a private network or a relay.
Technology
Durable sessions, agent adapters and authenticated transports meet behind narrow, testable boundaries.
Fleet, terminal and agent screens call one authenticated machine API. Connection strategies compete below that boundary and must prove the expected machine identity.
Endpoints hold payload keys while the service routes encrypted frames. Admission sees an authenticated Iroh EndpointId, validates its short lease and never receives terminal plaintext or a machine bearer.
Release candidateValidated end to end; hosted DNS and TLS rollout remains.
A bounded request, stream and close contract. It does not know whether bytes travelled through HTTPS, a private network or a relay.
The PTY survives client churn. Snapshots and ordered catch-up restore the mobile projection without taking ownership from the machine.
Each provider exposes only the conversation, work, runs and decisions it can substantiate. Raw terminal access stays independent.
Machine identity, token domains, authority, limits and log hygiene are executable checks shared by every transport provider.
Adapters project useful provider context beside the PTY. They are optional modules, not a dependency of the raw session path.
Delivery status
Durable PTYs, Fleet, raw terminal, structured Claude Code, Codex, OpenCode and Pi surfaces.
Verified machine connections through the authenticated API boundary.
Originless enrollment, public signed bootstrap, post-auth lease promotion, distributed quotas and true relay-only encrypted RPC pass locally. Hosted DNS/TLS and operational gates remain.
Container-scoped workspaces will reduce blast radius, but are not a current product guarantee.