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

A2A delegate_task is text-only: peer agents can't pass files (screenshots/video) for review #2222

New Issue
Closed
opened 2026-06-04 06:51:02 +00:00 by RenoStarsAI-production-client · 0 comments
RenoStarsAI-production-client commented 2026-06-04 06:51:02 +00:00
Copy Link
Copy Source

Summary

A peer agent cannot send a file (image, video, etc.) to another agent or to its parent over A2A. The delegate_task / reply_to_workspace schema is text-only (task: string, workspace_id: UUID) — no attachments field. This forces every visual review to detour through the human's canvas.

Where it bit (2026-06-04)

The Marketing Agent produced a video (Dreamina before/after morph) that needed a §8 visual review by the supervising parent before posting. The agent could deliver the clip + frames to the human's canvas via send_message_to_user (which DOES accept an attachments array), but had no way to send those same files to the parent agent doing the review. The parent had to ask the human to forward the frame back — a manual hop in the middle of an otherwise autonomous pipeline. For unattended runs (the whole point), there's no reviewer-in-the-loop file path at all.

Ask

Add an attachments capability to the peer-to-peer path, mirroring what send_message_to_user already supports:

  • reply_to_workspace / delegate_task (and the async variants) accept an attachments: [{path|url, mime, name}] array.
  • Attachments are delivered to the receiving agent in a form it can read (local path it can open, or a fetchable URL).

Why it matters

Visual QA (screenshots, generated media, before/after proofs) is core to autonomous marketing/design agents. Without peer file-passing, any review gate breaks the autonomy loop or silently skips the visual check. send_message_to_user already proves the platform can move files on the canvas path; this just extends the same to A2A.

Related

  • #2200 (native-input reliability) — same agent, same autonomous-pipeline goal.
## Summary A peer agent cannot send a file (image, video, etc.) to another agent or to its parent over A2A. The `delegate_task` / `reply_to_workspace` schema is text-only (`task: string`, `workspace_id: UUID`) — no `attachments` field. This forces every visual review to detour through the human's canvas. ## Where it bit (2026-06-04) The Marketing Agent produced a video (Dreamina before/after morph) that needed a §8 visual review by the supervising parent before posting. The agent could deliver the clip + frames to the **human's canvas** via `send_message_to_user` (which DOES accept an `attachments` array), but had **no way to send those same files to the parent agent** doing the review. The parent had to ask the human to forward the frame back — a manual hop in the middle of an otherwise autonomous pipeline. For unattended runs (the whole point), there's no reviewer-in-the-loop file path at all. ## Ask Add an `attachments` capability to the peer-to-peer path, mirroring what `send_message_to_user` already supports: - `reply_to_workspace` / `delegate_task` (and the async variants) accept an `attachments: [{path|url, mime, name}]` array. - Attachments are delivered to the receiving agent in a form it can read (local path it can open, or a fetchable URL). ## Why it matters Visual QA (screenshots, generated media, before/after proofs) is core to autonomous marketing/design agents. Without peer file-passing, any review gate breaks the autonomy loop or silently skips the visual check. `send_message_to_user` already proves the platform can move files on the canvas path; this just extends the same to A2A. ## Related - #2200 (native-input reliability) — same agent, same autonomous-pipeline goal.
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#2222
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?