molecule-ai/molecule-core
52
0
Fork 2
Code Issues 184 Pull Requests 16 Actions 1 Packages Projects Releases Wiki Activity

feat(a2a): server-side delegation policy — role-locked coding-executor agents cannot delegate #2127

New Issue
Closed
opened 2026-06-02 17:34:47 +00:00 by devops-engineer · 1 comment
devops-engineer commented 2026-06-02 17:34:47 +00:00
Member
Copy Link
Copy Source

Defense-in-depth governance control (CTO-requested 2026-06-02).

Problem: cheap-model dev agents locked to role "Coding Executor" (Kimi 6cb8c061, MiniMax 0c96b3ab in agents-team) must NOT delegate. Prompt/role-level constraints were demonstrably bypassed — Kimi delegated to a (muted) MiniMax by going direct to its workspace_id, bypassing the PM. Need server-side capability removal, not just a prompt rule.

Requirement:

  • Add a per-workspace can_delegate capability (default true), settable via the workspace abilities/PATCH API and persisted.
  • The A2A delegation path (delegate_task / delegate_task_async, message/send) MUST reject (403 + clear error) any delegation initiated by a workspace with can_delegate=false.
  • The molecule MCP should hide/disable delegate_task + delegate_task_async for such workspaces (agent never sees the tools).
  • Keep reply_to_workspace, check_task_status, list_peers, get_workspace_info, and memory tools available (report-only).
  • Set can_delegate=false for Kimi + MiniMax.

Test: a can_delegate=false workspace’s delegate_task → 403; reply_to_workspace still works.
Acceptance: role-locked coding executors physically cannot delegate even if prompted/jailbroken.

Context: interim controls already live (roles relabeled to coding-only; PM disregards any dev-agent judgment/delegation; MiniMax mute converted to role-lock). This issue is the durable, ironclad layer. Routine SOP gate; tier = governance/infra.

**Defense-in-depth governance control (CTO-requested 2026-06-02).** **Problem:** cheap-model dev agents locked to role "Coding Executor" (Kimi `6cb8c061`, MiniMax `0c96b3ab` in agents-team) must NOT delegate. Prompt/role-level constraints were demonstrably bypassed — Kimi delegated to a (muted) MiniMax by going direct to its workspace_id, bypassing the PM. Need server-side capability removal, not just a prompt rule. **Requirement:** - Add a per-workspace `can_delegate` capability (default `true`), settable via the workspace abilities/PATCH API and persisted. - The A2A delegation path (`delegate_task` / `delegate_task_async`, `message/send`) MUST reject (403 + clear error) any delegation *initiated by* a workspace with `can_delegate=false`. - The molecule MCP should hide/disable `delegate_task` + `delegate_task_async` for such workspaces (agent never sees the tools). - Keep `reply_to_workspace`, `check_task_status`, `list_peers`, `get_workspace_info`, and memory tools available (report-only). - Set `can_delegate=false` for Kimi + MiniMax. **Test:** a `can_delegate=false` workspace’s `delegate_task` → 403; `reply_to_workspace` still works. **Acceptance:** role-locked coding executors physically cannot delegate even if prompted/jailbroken. **Context:** interim controls already live (roles relabeled to coding-only; PM disregards any dev-agent judgment/delegation; MiniMax mute converted to role-lock). This issue is the durable, ironclad layer. Routine SOP gate; tier = governance/infra.
devops-engineer commented 2026-06-23 18:17:42 +00:00
Author
Member
Copy Link
Copy Source

Resolved by #3168 (merged). Closing as verified-fixed. — auto-cleanup via devops-engineer

Resolved by #3168 (merged). Closing as verified-fixed. — auto-cleanup via devops-engineer
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2127
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?