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

Regular workspaces lack the unified request tools (create_request/list_inbox) — npm mcp-server isn't wired into ordinary workspace boxes #2606

New Issue
Open
opened 2026-06-11 20:42:20 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-11 20:42:20 +00:00
Member
Copy Link
Copy Source

Surfaced while shipping the core#2573 fix chain (CTO architecture question, 2026-06-11).

Intent (SSOT): the platform agent is a normal workspace differing only in image + config overlay (core#2495), and registerRequestTools (mcp-server requests.ts) registers create_request/list_inbox/check_requests/respond_request in BOTH workspace and management modes from one function. So every workspace should be able to raise a task/approval to the user.

Reality: ordinary workspace boxes never load the npm @molecule-ai/mcp-server at all:

  • the base workspace-template-claude-code image does not install it (only Dockerfile.platform-agent does);
  • the template config.yaml has no mcp_servers: block;
  • tenant workspace agents get their agent-facing tools from the runtime wheel's python a2a bridge (delegate_task, send_message_to_user, commit_memory, …), which has no request tools;
  • external runtimes go through their adapters — same story.

So today only the concierge (management mode, as of mcp-server 1.6.1) and management/canvas-side consumers have create_request/create_approval. A regular workspace asked to "request user approval" has no tool for it — the same improvisation hazard class as core#2573.

Options (pick via RFC/design review):

  1. Bake @molecule-ai/mcp-server (workspace mode) into the base template image + add an mcp_servers: overlay fragment (mirror of the concierge's mcp_servers.yaml mechanism, default mode instead of management).
  2. Port the request tools into the runtime wheel's a2a bridge (single wheel delivery, but duplicates the tool surface — weakens the npm SSOT).
  3. Hybrid: bridge proxies to the unified /workspaces/:id/requests endpoint (thin client, SSOT stays server-side).

Option 1 keeps the SSOT story cleanest; needs the PATH-collision care from the pilot RCA (molecule-mcp vs molecule-platform-mcp symlink).

Refs: core#2573, mcp-server#61/#62/#63, template#111/#112/#113.

Surfaced while shipping the core#2573 fix chain (CTO architecture question, 2026-06-11). **Intent (SSOT):** the platform agent is a normal workspace differing only in image + config overlay (core#2495), and `registerRequestTools` (mcp-server requests.ts) registers `create_request`/`list_inbox`/`check_requests`/`respond_request` in BOTH workspace and management modes from one function. So *every* workspace should be able to raise a task/approval to the user. **Reality:** ordinary workspace boxes never load the npm `@molecule-ai/mcp-server` at all: - the base `workspace-template-claude-code` image does not install it (only `Dockerfile.platform-agent` does); - the template `config.yaml` has no `mcp_servers:` block; - tenant workspace agents get their agent-facing tools from the runtime wheel's python a2a bridge (`delegate_task`, `send_message_to_user`, `commit_memory`, …), which has no request tools; - external runtimes go through their adapters — same story. So today only the concierge (management mode, as of mcp-server 1.6.1) and management/canvas-side consumers have `create_request`/`create_approval`. A regular workspace asked to "request user approval" has no tool for it — the same improvisation hazard class as core#2573. **Options (pick via RFC/design review):** 1. Bake `@molecule-ai/mcp-server` (workspace mode) into the base template image + add an `mcp_servers:` overlay fragment (mirror of the concierge's `mcp_servers.yaml` mechanism, default mode instead of management). 2. Port the request tools into the runtime wheel's a2a bridge (single wheel delivery, but duplicates the tool surface — weakens the npm SSOT). 3. Hybrid: bridge proxies to the unified `/workspaces/:id/requests` endpoint (thin client, SSOT stays server-side). Option 1 keeps the SSOT story cleanest; needs the PATH-collision care from the pilot RCA (molecule-mcp vs molecule-platform-mcp symlink). Refs: core#2573, mcp-server#61/#62/#63, template#111/#112/#113.
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 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#2606
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?