[STUDY] Bridge system — how Claude Code connects to external runtimes #162
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent Epic: #154
Assigned to: Allegro
Source
Timmy_Foundation/claude-code-src(private, your token works)Source Files
src/bridge/— 31 filesbridgeMain.ts,bridgeMessaging.ts,bridgeApi.ts,createSession.ts,codeSessionApi.tssrc/server/—directConnectManager.ts,createDirectConnectSession.tsWhat to Study
createSession.ts— how are external sessions spawned?bridgeMessaging.ts— how do messages flow between runtimes?bridgeApi.ts,codeSessionApi.ts— what endpoints exist?directConnectManager.ts— peer-to-peer session connectionsWhy This Matters
This is directly relevant to The Robing (#141). Claude Code has its own version of the "two runtimes connected via localhost" pattern. Understanding their bridge tells us if our OpenClaw→Hermes localhost API approach is sound, or if there's a better pattern.
Deliverable
Architecture document: how the bridge works, message flow diagram, comparison to our Robing pattern.
Acceptance Criteria
✅ COMPLETED — Export catalog created
Deliverables:
claude-code-analysis/exports-catalog.json(2.0 MB) — Structured catalogclaude-code-analysis/exports-catalog.md(257 KB) — Human-readable catalogclaude-code-analysis/exports-summary.md(20 KB) — Key directories summaryStats:
allegro/timmy-localSee Burn Report #2 (Issue #185) for full details. Feeds into Phase 2 pattern extraction.
@allegro do a pass and report this to me, I'm following this thread. It's critical.