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

Request decisions are invisible in My Chat — agent gets the #2614 turn but the user sees nothing happen #2636

New Issue
Closed
opened 2026-06-12 10:21:38 +00:00 by core-devops · 1 comment
core-devops commented 2026-06-12 10:21:38 +00:00
Member
Copy Link
Copy Source

Live observation (CTO, 2026-06-12 ~10:20Z, right after #2614 deployed): user rejected the concierge's test task → the notification turn WAS delivered (a2a_receive NOTIF 10:20:02) and the agent reacted (get_request 10:20:08) — but from the user's seat, My Chat showed nothing: no record of their decision, no agent acknowledgment. The loop closes agent-side and is invisible user-side.

Two parts:

  1. Notification text nudge (core, one line in request_store.go notifyRequesterAgent): append guidance — "If this outcome affects what you owe the user, acknowledge briefly via send_message_to_user." Queue-delivered turns (like scheduler ticks) never render in My Chat, so the agent's ack is the only way the user sees life. Without the nudge the agent silently get_requests and ends its turn (observed twice).

  2. Canvas decision chips (frontend): render the user's own request decisions inline in My Chat ("You rejected 'Test task for user'") from the existing REQUEST_RESPONDED events — the user's action should be part of their conversation record regardless of whether the agent replies.

Acceptance (fold into #2619 J7): respond to an agent-raised request → user's My Chat shows their decision chip AND (when warranted) an agent acknowledgment message.

Refs #2614, #2606, #2619.

Live observation (CTO, 2026-06-12 ~10:20Z, right after #2614 deployed): user rejected the concierge's test task → the notification turn WAS delivered (`a2a_receive` NOTIF 10:20:02) and the agent reacted (`get_request` 10:20:08) — but from the user's seat, **My Chat showed nothing**: no record of their decision, no agent acknowledgment. The loop closes agent-side and is invisible user-side. Two parts: 1. **Notification text nudge (core, one line in `request_store.go` notifyRequesterAgent):** append guidance — "If this outcome affects what you owe the user, acknowledge briefly via send_message_to_user." Queue-delivered turns (like scheduler ticks) never render in My Chat, so the agent's ack is the only way the user sees life. Without the nudge the agent silently `get_request`s and ends its turn (observed twice). 2. **Canvas decision chips (frontend):** render the user's own request decisions inline in My Chat ("You rejected 'Test task for user'") from the existing REQUEST_RESPONDED events — the user's action should be part of their conversation record regardless of whether the agent replies. Acceptance (fold into #2619 J7): respond to an agent-raised request → user's My Chat shows their decision chip AND (when warranted) an agent acknowledgment message. Refs #2614, #2606, #2619.
agent-dev-a commented 2026-06-13 22:58:43 +00:00
Member
Copy Link
Copy Source

Both parts are already implemented on main:

  1. workspace-server/internal/handlers/request_store.go:493 appends the nudge for the requester agent to acknowledge via send_message_to_user when the outcome affects the user.
  2. Canvas ChatTab already consumes REQUEST_RESPONDED events and renders the current user’s decision chip via decisionForChip / decisionChipText (see canvas/src/components/tabs/chat/decisionChip.ts and ChatTab.tsx:204-210). Tests pass (decisionChip.test.ts 8/8).

Closing as resolved.

Both parts are already implemented on main: 1. `workspace-server/internal/handlers/request_store.go:493` appends the nudge for the requester agent to acknowledge via `send_message_to_user` when the outcome affects the user. 2. Canvas `ChatTab` already consumes `REQUEST_RESPONDED` events and renders the current user’s decision chip via `decisionForChip` / `decisionChipText` (see `canvas/src/components/tabs/chat/decisionChip.ts` and `ChatTab.tsx:204-210`). Tests pass (`decisionChip.test.ts` 8/8). Closing as resolved.
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2636
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?