Skip to content

feat(crew): let a crewmate request tools for its worker (preview) - #23562

Merged
iamwhatever merged 1 commit into
mainfrom
feat/crewmate-dyncap
Oct 24, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
feat/crewmate-dyncap

Conversation

@buluoray

@buluoray buluoray commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A crewmate can find the tools, MCP servers and skills its worker is missing and ask the user for them on a card, behind a per-crewmate Dynamic capabilities preview that is off by default.

Crewmate 2.0 (#23010) gives each crewmate a worker built from its own kit. When that worker reports a missing capability, the crewmate today can only tell the user and wait: it cannot see what this gateway already runs or what the MCP registry offers, so it often says a tool does not exist without looking. After the user adds something by hand, a worker that was already running does not see it until its next spawn.

Why it matters

The crewmate's job is to get the work done. Without a way to look up and request what its worker lacks, every missing tool turns into a manual trip to the crewmate's advanced settings and a stalled task. Keeping it a per-crewmate preview lets one crewmate try it without changing any other.

Not a goal

  • Turning the preview on by default, or adding a global switch for it.
  • Letting a crewmate or its worker write its own crewmate file: every addition is still a card the user presses.
  • Any provider other than the official MCP registry for request_capabilities additions.
  • Running workers in per-crewmate git worktrees (its own pull request).

What changed (motivation → approach → change)

Goal → the crewmate looks first, then asks on a card, and the work resumes on the same worker → built on #23010's conductor/worker split, with every write still going through the existing crewmate.capabilities card and mate_capabilities.put.

  • find_capabilities (POST /api/member/self/capabilities, dashboard/handlers/member_capability_catalog.py, mate_capability_catalog.py): what the worker has, what this gateway has loaded that it lacks, and (for a query) the MCP registry, with provider fields redacted and no transport returned.

  • request_capabilities now takes named additions ({server, source: "gateway"}, {server, source: "registry", registry_id}, {skill}) that the gateway resolves into the card's operations plus an origins map; a draft of additions takes no raw operations alongside (invalid_additions), so none is folded under Details unseen. The card shows one plain line per addition, with launch lines and origins under Details (an addition with no auto-approved tool says it adds no new grant and the current approval settings still apply, not that every call asks, since a crewmate on Trust runs calls unasked); a card that only adds servers this gateway already runs carries no third-party warning, and a widening approval keeps its acknowledgement.

  • On the worker-report wake (not a user turn), only a card whose additions are all servers this gateway already runs is admitted (member_self._gateway_servers_only); anything else stays user-turn only.

  • The conductor's own session_create / session_send result names the worker's servers and the gateway's extra ones the user has not switched off (dashboard/crewmate_dispatch_capabilities.py).

  • Off (the default), request_capabilities stays, so no crewmate loses it. Its first call raises one Preview opt-in card instead of the capabilities card (member_self, mate_tool_access.py), saying in plain words what the preview does, with Turn on / Not now. Turn on writes the flag and raises the held request as its own card, so the crewmate does not ask again (member_self.continue_after_opt_in); only a card for the thread's own crewmate does this, and only once that crewmate's flag is on. The offer and held request are recorded before the card is raised: a failed write raises no card (503 opt_in_unrecorded), and a card that is not raised takes the record back. Not now leaves it off; every later call is refused with a plain line, and no second card is raised; a card the store has pruned counts as expired. Off, find_capabilities stays listed and its route answers 403 dynamic_capabilities_off: the flag is read on every call, not through the pooled kirocrew-mate server's cached tool policy, so a Turn on reaches a running conductor at once. Off, the conductor's prompts are the wording from before the preview (*_manual in crewmate_prompts.json).

  • An applied capability reloads an idle running worker in place, conversation kept, and a [Capabilities added] turn sends the waiting work back to it, only in the thread of the crewmate the card changed (dashboard/crewmate_worker_reload.py, goal_setup.schedule_capabilities_nudge).

  • The Profile card's Settings page gets a Dynamic capabilities switch with a Preview tag, stored on the crewmate's own record (KiroCrewAgentConfig.dynamic_capabilities, crewmate_dynamic_capabilities.py).

  • Rebased onto feat(crew): give each crewmate its own config, a conductor and a worker #23010 as merged: the change_card_catalog and agent hunks moved to change_card_catalog_kinds.py / change_card_catalog_plans.py / agent_parts/spec_grants.py, the suite-wide preview fixture moved to test/conftest_resets.py, and the switch uses the Settings page's row layout.

  • A gateway addition copies only a server the gateway lists as switched on, and only one whose entry sets no env or headers value and has no credential argument that agent_capabilities.safe_view would mask (--api-key <value>, -e NAME=<value>; refused carries_settings): a card's params reach the proposing crewmate, so a credential never rides on one. The card calls a server "this gateway's" only when the draft equals the gateway entry key for key (gateway_matches), so a changed env, cwd or args keeps its code warning. propose_change refuses caller-supplied origins.

  • A worker still cold-starting when a capability is applied keeps its reload owed (the busy check runs before the no-provider check).

Spec: docs/system-specs/modules/crew-mode.md, docs/system-specs/modules/config.md, docs/architecture/mcp.md, src/kiro_crew/docs/crew-members.md, src/kiro_crew/docs/agent-spec-fields.md.

Backwards compatibility

Compatible for request_capabilities: every existing crewmate keeps it with the flag off (the default), and its first use raises the Preview opt-in card. A config without dynamic_capabilities loads as off. Writer sweep on origin/main @ 5d7a22d. What is still taken away, one line each:

Reader: src/kiro_crew/dashboard/handlers/change_cards.py:api_cards_agent_propose -- chat -- propose_change refuses a crewmate.capabilities card from a crewmate whose flag is off, so the opt-in is the only way in, and refuses caller-supplied origins; test/test_crewmate_dynamic_capabilities.py, test/test_mate_capability_catalog.py

The take-away check also fires on src/kiro_crew/mate_config_migration.py, which changes only in its module docstring (one paragraph added); no migration code changes. Its readers:

Reader: src/kiro_crew/dashboard/server.py:migrate_existing_crewmates -- release -- the startup migration's code is unchanged; test/test_mate_config_migration.py
Reader: src/kiro_crew/mate_config.py:uncarried_restrictions -- crew page -- the create path's restriction check is unchanged; test/test_mate_config_migration.py
Reader: src/kiro_crew/mate_worker_kit.py:_worker_base_or_none -- crew page -- Advanced > Re-copy from template reads the same base; test/test_mate_worker_kit.py

Tests

  • test/test_crewmate_dynamic_capabilities.py: the flag is per crewmate, off by default, read from the record on every call (off, find_capabilities answers 403, and a Turn on takes effect on the next call); both capability tools stay listed; the conductor and worker prompts follow it.
  • test/test_mate_capability_catalog.py: catalog order, redaction, additions resolved into operations, every refusal code (a switched-off server, one carrying env, headers or a credential argument, while plain arguments still pass), the card's rows and warnings, a changed env/cwd/args not counted as the gateway's, additions with raw operations refused, and propose_change refusing origins.
  • test/test_mate_tool_access.py: off, the first request_capabilities raises the opt-in card and holds the request; Turn on raises that request as its card, once; Not now (and an expired or switched-off-again card) refuses with no second card; a waiting card is not raised twice; it is per crewmate; on, the request is its card unchanged; a pruned card counts as expired while an unreadable store leaves it waiting; the record is written before the card, a failed write raises none, a refused card takes it back, a lost card id waits then ages out, and two calls claim one ask. test/test_crewmate_worker_reload.py also checks that a card for another crewmate wakes nobody in this thread.
  • test/test_crewmate_dispatch_capabilities.py: only the conductor's own hand-off carries the capability line, and a switched-off server is not offered.
  • test/test_crewmate_worker_reload.py: an applied card reloads an idle worker in place, leaves a busy one alone, and keeps a cold-starting one owed.
  • test/test_goal_setup.py, test/test_member_goals.py, test/test_member_mate_tools.py, test/test_mate_config_migration.py: the nudges, admission and prompt wording.
  • website/src/pages/members/CrewProfileSettings.test.tsx, website/src/cards/CardChanges.test.tsx, website/src/cards/ConversationCard.test.tsx, website/src/i18n/toolAccessCopy.test.ts: the switch, the card's summary and Details, the opt-in card's Turn on / Not now (no other card has them), and the copy.
  • Re-pinned: test/test_agent_refactor_spec_bytes.py (conductor, worker, kirocrew, kirocrew-worker specs) and test/test_dashboard_server_composition_contract_reach.py (the added routes).

Proof: not provable -- other: new feature, the new tests exercise code this pull request adds

Manual verification

Rendered the built SPA against stubbed APIs: the Settings page shows the switch off with its Preview tag, and pressing it sends PUT /api/agents/<name> with {"dynamic_capabilities": true} and shows it on, in light and dark. The catalog, card and reload paths were not run against a live gateway.

Screenshots / video

Settings page, light, off and on:

Dynamic capabilities off, light

Dynamic capabilities on, light

Dark

Dynamic capabilities off, dark

Dynamic capabilities on, dark

Related Issues

Follows #23010.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license.

@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners October 23, 2026 21:22
@buluoray
buluoray requested a review from iamwhatever October 23, 2026 21:22
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 23, 2026
@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ human override accepted

@buluoray overrode this lane for 1c14ef174fd357e90b3be654df8180db452b26ab via /ai-review override (this commit only).

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)

UX-level review of 1c14ef174fd357e90b3be654df8180db452b26ab — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

cannot evaluate: missing the chat cards this PR exists to add. No screenshot shows the Preview opt-in card (Turn on / Not now) or the capabilities card with its addition lines and Details.

Evidence gaps

  • Preview opt-in card (ChangeCard.tsx: the tool_access_title heading, the Preview badge in the title, the Turn on / Not now buttons) is in no screenshot. The blind reader said: "'A card in this chat': no chat is visible here, so I don't know what the card looks like." To close: a screenshot of the pending opt-in card in a crewmate thread.
  • Capabilities card with additions (AdditionLine: "Give {{name}}'s worker {{server}}." plus the gateway, registry and card origin lines, the runs-unasked line or "Adds no new grant…", and the skill line) is in no screenshot. To close: one card with a gateway server, a registry server and a skill.
  • The card's Details section (change-card-details) is in no screenshot. To close: the same card with Details expanded.
  • The refusal after Not now, and the [Capabilities added] resume turn: whatever the user sees for these is in no screenshot. To close: a screenshot of each in the thread.
  • The switch's save-error state (profile_dynamic_capabilities_failed) is in no screenshot. To close: a screenshot of the failed toggle.

Notes

  • The screenshots are from an older revision. The switch row shows the Sparkles icon, but the diff renders Puzzle. The blind reader thought "Model" and "Dynamic capabilities" were linked because they had the same icon. Retake shots 01–04 at this HEAD.
  • The hint profile_dynamic_capabilities_hint names "{{name}}'s advanced settings" with no link to it. The reader said: "I see no link or button to get there on this page." Make that phrase a link to the Advanced page.
  • tool_access_title packs two sentences into the card heading. Keep the question ("Allow {{name}} to ask you for tools its worker needs?") as the title and move "Each one still needs your approval." into the card body.

[UX-REVIEWED] 1c14ef1

Description read

[DESCRIPTION-READ] 579e7a552df2f234b8f034dd5cd1821bf3fbe8157c59023007e4ef5e8151a4c4

That sha256 names everything this verdict read: the PR description, plus the 7 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 1c14ef174fd357e90b3be654df8180db452b26ab — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: the preview is per crewmate and off by default, every write still goes through a card the user presses, and the one thing taken away (propose_change from a crewmate whose preview is off) is listed.

Notes

  • _crewmate_drives_capabilities_off checks the caller's own preview flag, not the flag of the crewmate the card targets. So a crewmate with the preview off can no longer propose a crewmate.capabilities card for another crewmate either, and the get_member_capabilities guide text in mcp_guide.py still tells it to.

[DESIGN-REVIEWED] 1c14ef1

Description read

[DESCRIPTION-READ] e479b83b78d9231036de12a3b1432af153db6e9bb2ffeba3afd3ae8ea2a75d9c

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 1c14ef174fd357e90b3be654df8180db452b26ab — this comment is updated in place on each push.

Review details

No findings.

Notes:

  • The [Capabilities added] hidden turn is filled with the card's title ("Change tools for “X”"), not the capabilities that were added (change_cards.py _complete).

[OPUS-REVIEWED] 1c14ef1

Verdict parsed from the review's SHA-scoped output markers for commit 1c14ef174fd357e90b3be654df8180db452b26ab.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 1c14ef174fd357e90b3be654df8180db452b26ab false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 1c14ef174fd357e90b3be654df8180db452b26ab and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 1c14ef1

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 1c14ef174fd357e90b3be654df8180db452b26ab false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 23, 2026
@buluoray
buluoray force-pushed the feat/crewmate-dyncap branch from 47c43fd to 7101dcf Compare October 23, 2026 22:02
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 23, 2026
@buluoray
buluoray force-pushed the feat/crewmate-dyncap branch from 7101dcf to 26afd4e Compare October 23, 2026 23:24
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 23, 2026
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 24, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

🤖 Kiro Crew Auto-Pipeline [operator: buluoray]: Answer to the First Principles BLOCK on the default removing an existing tool. Product decision by Ray (buluoray): default off, first use raises a Preview opt-in card, so no existing crewmate loses the tool. With the flag off, request_capabilities stays mounted; its first call raises one Preview opt-in card (Turn on / Not now). Turn on writes the flag and raises the held request as its own card; Not now leaves it off, later calls are refused with a plain line, and no second card is raised. Implemented at head 2530157; ## Backwards compatibility is rewritten to match.

@buluoray
buluoray force-pushed the feat/crewmate-dyncap branch from 26afd4e to 2530157 Compare October 24, 2026 00:33
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

AI-review override not recorded: 25301579d47a14ae6c689c3fd13d0fe2fb84b6d7 is not the current PR head. Re-run the command with 25301579d4f1a13aee9f19fa1f7a62753e74cbaa.

@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 2530157: Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 24, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 6b8fd74: Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray recorded a legacy release (class legacy) for the first-principles AI finding on 6b8fd74376bdb01155268dad2ba80bee943ac286.

Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

This override used the old command without a class. It was recorded as class legacy, and the old command stops working on 2026-12-09. Name a class from now on. Use /ai-review override <fable|gpt|design|ux|first-principles|scope|all> <current-sha> <class>[ #N]: <reason, 20 to 500 characters>, where <class> is one of false-positive, not-applicable, pre-existing, evidence-supplied, infra-failure, reissue, deferred, owner-decision. What each class needs: docs/ci/ci-and-reviews.md#risk-release-records.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Oct 24, 2026
@buluoray
buluoray force-pushed the feat/crewmate-dyncap branch from 6b8fd74 to 6ef2f7a Compare October 24, 2026 06:57
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 24, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 6ef2f7a: Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray recorded a legacy release (class legacy) for the first-principles AI finding on 6ef2f7ae2616947cca5a9b430d186e811a3ce683.

Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

This override used the old command without a class. It was recorded as class legacy, and the old command stops working on 2026-12-09. Name a class from now on. Use /ai-review override <fable|gpt|design|ux|first-principles|scope|all> <current-sha> <class>[ #N]: <reason, 20 to 500 characters>, where <class> is one of false-positive, not-applicable, pre-existing, evidence-supplied, infra-failure, reissue, deferred, owner-decision. What each class needs: docs/ci/ci-and-reviews.md#risk-release-records.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 24, 2026
…view)

Dynamic capabilities, a per-crewmate preview off by default, on top of
Crewmate 2.0's conductor and worker.

- find_capabilities reads what the worker has, what this gateway has
  loaded that it lacks, and the MCP registry; request_capabilities takes
  named additions the gateway resolves into the card's operations, with
  where each comes from and what runs without asking.
- The hand-off result names the worker's servers and the gateway's extra
  ones.
- ask_tool_access: one Preview card per crewmate asking whether it may
  request tools, while its flag is off.
- An approved capability reloads a running worker in place, conversation
  kept, and the [Capabilities added] turn sends the waiting work back to it.
- The Profile card's Dynamic capabilities switch.
@buluoray
buluoray force-pushed the feat/crewmate-dyncap branch from 6ef2f7a to 1c14ef1 Compare October 24, 2026 07:47
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 24, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 1c14ef1: Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray recorded a legacy release (class legacy) for the first-principles AI finding on 1c14ef174fd357e90b3be654df8180db452b26ab.

Product decision by the maintainer (buluoray): dynamic capabilities stay off by default, and the first request_capabilities call while off raises a one-time Preview opt-in card, so no existing crewmate loses the tool.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

This override used the old command without a class. It was recorded as class legacy, and the old command stops working on 2026-12-09. Name a class from now on. Use /ai-review override <fable|gpt|design|ux|first-principles|scope|all> <current-sha> <class>[ #N]: <reason, 20 to 500 characters>, where <class> is one of false-positive, not-applicable, pre-existing, evidence-supplied, infra-failure, reissue, deferred, owner-decision. What each class needs: docs/ci/ci-and-reviews.md#risk-release-records.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 24, 2026

@cruisercohen cruisercohen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed as security scope (crewmate capability / access-gate paths), comment only — not approving. No default-on widening; the design is fail-closed.

What it adds: a crewmate can discover (find_capabilities) and request (request_capabilities) skills / MCP servers for its own worker. The security-relevant properties I checked:

  • Off by default, per crewmate. dynamic_capabilities is a per-crewmate preview flag; there is no global key and the default is off. With it off, find_capabilities is refused at its route (403 dynamic_capabilities_off), request_capabilities raises a Preview opt-in card instead of acting, and a proposed crewmate.capabilities card is refused — the user's "Turn on" is the only way in.
  • Nothing applies without the user. Every capability change is a change card, inert until the user presses it; the set_* / request_* tools only offer a card. find_capabilities is read-only (worker tools + gateway-loaded servers + registry search).
  • Scoped to the crewmate's own file. A requested registry server is installed into the crewmate's own worker file, never the user's MCP config; gateway_matches marks a server as gateway-provided only when it is byte-for-byte equal to the gateway's enabled entry (command/args/env/headers/cwd), so a tampered or switched-off spec can't borrow gateway provenance.
  • Workers can't reach it. Both tools are in MATE_WORKER_EXCLUDED_TOOLS; only the crewmate's own conductor thread reaches them, and the hand-off capability summary is added only when the caller is a crewmate conductor and the target its own worker (member-id match) with the preview on.

Verified on the merge with current main: 0 failures across the dynamic-capabilities, catalog, dispatch, tool-access and goal-setup suites; and a mutation making the flag default-on turns 9 off-gate tests red (including the 403 route refusal) — so the off gate has teeth.

No security-default change. Final sign-off is a maintainer's.

@iamwhatever
iamwhatever merged commit 071eb5b into main Oct 24, 2026
110 of 111 checks passed
@iamwhatever
iamwhatever deleted the feat/crewmate-dyncap branch October 24, 2026 20:45
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants