You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b73f8fe
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): only a calling thread's modes carry over a link
eee5e3b started any linked launch that omitted runtimeMode at the
forwarded T3-Mode-Limit. For a calling thread that limit is its own
running mode, which is what should carry over. For an MCP client outside
a thread it is only an approval ceiling, so a full-access client launching
through a full-access link got a full-access thread there. The same
client launching locally gets the project default.
The forwarder now marks the limit as inheritable with T3-Mode-Inherit: 1,
and only when the caller is a thread. The receiving /mcp records that
beside narrowedTo. t3_thread_launch skips the project default only for
a caller that sent it. A client outside a thread starts at the far
side's project default, within its ceiling and the link, as it does here.
Mixed versions keep today's default: an old receiver ignores the header,
and an old sender never sends it. docs/internals/remote.md states the
rule.
Fails before: the new client case in PeerForwarding "launches in a
linked environment with the caller's modes" received full-access,
expected approval-required. After: PeerForwarding, RemoteDelegation,
project handlers, linkOrigin and McpHttpServer tests 66/66; tsc, fmt and
lint clean on the changed files.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01A1D6J2UMPo7YBWQFvbg1br
0 commit comments