forge v0.2.0 — one fleet with Claude Code
One fleet with Claude Code
forge now speaks the Claude Code fleet wire protocol. On a machine running Claude Code with a fleet channel:
- Unified board —
forge statuslists Claude Code sessions alongside forge sessions (task, last prompt, last reply), and Claude Code's fleet board sees forge sessions. - Cross-runtime messaging, both directions —
forge send/ the agent'sfleet_sendreach Claude Code sessions (arriving as channel events mid-conversation); Claude Code'sfleet_sendreaches forge sessions (arriving in the agent's inbox mid-work). - Zero config — every forge session registers in the shared inbox registry and accepts the fleet's authenticated
POST /send. forge setupchecks interop on any machine — detects Claude Code, prepares the shared token, and reports exactly what works. Without Claude Code, forge's native fleet works standalone.
Verified live in both directions before release.
Full changelog: v0.1.1...v0.2.0