🌉 Bridge Protocol: Remote Session Support

[yacosta738]

Summary

Implement the Claude-style remote bridge protocol layer for Corvus, including remote session transport, authentication, and client/session isolation.

Why this matters

Corvus already has local/mobile bridge scaffolding, but Claude Code parity requires a more explicit remote bridge model for long-running remote sessions and streamed interaction.

Current reality in Corvus

Already present:

• KMP/mobile runtime bridge scaffolding
• gateway and session infrastructure that can support remote workflows

Still missing for parity:

• explicit Claude-style bridge protocol contract
• authenticated remote-session lifecycle
• JWT-based access control for bridge clients
• SSE and WebSocket transport support at the bridge layer
• hardened remote-client/session isolation semantics

Scope

• define bridge protocol contract
• implement authenticated remote session bootstrap
• add SSE transport for streaming output
• add WebSocket transport for bidirectional remote interaction
• isolate remote sessions per client and identity
• document bridge lifecycle and failure handling

Non-goals

• replacing existing mobile bridge abstractions unless necessary
• terminal UI redesign

Dependencies

• Related to ⌨️ Slash Commands: Command Registry Implementation #527 for command/session entrypoints
• Related to existing gateway/session contracts in the runtime

Acceptance criteria

• bridge protocol is documented and implemented
• remote clients can authenticate and create isolated sessions
• SSE transport supports streamed responses
• WebSocket transport supports bidirectional interaction
• remote session cancellation/reconnect semantics are defined and tested
• security tests cover unauthorized access and session-crossing failures

References

• tmp/CLAUDIO_ROADMAP.md
• tmp/claurst-main/spec/09_bridge_cli_remote.md
• tmp/Product Requirements Document (PRD) _ Specifications for Replicating Claude Code.md §8

[linear]

DALLAY-270