Skip to content

MCP profiles: carry the parent's profile with a cross-machine delegation #532

Closed

Description

@scuttletoby

A task delegated to another machine starts there with no parent thread (parentThreadId is null), so its MCP profile is that machine's profile for its role (mcpSubagentProfile, else mcpProfile), not the delegating thread's. With the sub-agent rule inherit, a child of a t3-only thread on machine A can get every outside server on machine B.

This is the decided behaviour for now (PR #528): server names on two machines need not mean the same servers, so the parent's list cannot be applied as is. The docs say so (docs/fork/README.md, MCP profiles).

Proposal: carry the parent's resolved profile (its name and its servers, or at least whether it was all, t3-only or a list) in the delegation request, and let the receiving machine:

  • apply t3-only / an empty list as is (no outside servers means the same on any machine);
  • for a named list, keep only the servers both lists name, or refuse when the receiving machine has none of them;
  • never widen past its own role default.

Open questions: what the request carries for an older sender (fall back to today's rule, with a log line), and whether the owner can opt out per machine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions