docs(roadmap): correct v3.0.0 — opt-in stays, only the form changes
Earlier wording claimed --dangerously-load-development-channels "goes away" at v3.0.0. That overstated what we know. Some opt-in mechanism is always required for Claude Code to accept external runtime events from a third-party process — that's a security invariant, not a quirk of today's flag. What changes at v3.0.0 is the FORM of the opt-in (stable settings entry, native transport subscription, etc.), not its existence. The "dangerously" / "experimental" / "development" framing is what disappears, because the underlying API graduates from experimental to stable. The flag itself, or its successor, lives on as a normal config entry that claudemesh install writes once. Public roadmap and internal spec both updated to reflect this. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -214,13 +214,27 @@ Migration target, not a planned feature — depends on Anthropic
|
||||
shipping first-class agent-to-agent channels in Claude Code. When
|
||||
that lands:
|
||||
|
||||
- The MCP wrapper from v2.0.0 disappears entirely
|
||||
- The daemon plugs directly into the native channel primitive
|
||||
- `--dangerously-load-development-channels` flag goes away
|
||||
- **Two possible shapes**, depending on Anthropic's choice:
|
||||
- *(a)* MCP-channel notifications graduate from
|
||||
`experimental.claude/channel` to a stable API. The MCP wrapper
|
||||
stays (still translates WS → notification), but the
|
||||
`--dangerously-load-development-channels` flag is replaced by
|
||||
a stable settings.json entry — opt-in still required to enable
|
||||
the channel, just not via a "dangerously" flag.
|
||||
- *(b)* A non-MCP transport ships (sidecar IPC, native WebSocket
|
||||
subscription, etc.). The MCP wrapper from v2.0.0 disappears;
|
||||
the daemon plugs into the new transport directly. Some opt-in
|
||||
config is still required somewhere (settings.json or similar)
|
||||
so Claude Code knows to subscribe.
|
||||
- claudemesh becomes a "hosted backend for Claude's native
|
||||
multi-agent feature" — marketing simplifies
|
||||
multi-agent feature" rather than a "Claude Code extension" —
|
||||
marketing simplifies regardless of which shape ships.
|
||||
- The `experimental.`/`dangerously-` framing disappears either
|
||||
way — that's the load-bearing user-facing change.
|
||||
|
||||
Until then, v2.x ships with the MCP bridge.
|
||||
Until then, v2.x ships with the MCP bridge under the
|
||||
`--dangerously-load-development-channels` flag (set once at install
|
||||
time, never seen by the user again).
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user