Skip to content

fix: deliver MoltyBot bridge response attachments#1513

Draft
xiguatailangmaixigua wants to merge 3 commits into
chenhg5:mainfrom
xiguatailangmaixigua:codex/moltybot-remote-agent
Draft

fix: deliver MoltyBot bridge response attachments#1513
xiguatailangmaixigua wants to merge 3 commits into
chenhg5:mainfrom
xiguatailangmaixigua:codex/moltybot-remote-agent

Conversation

@xiguatailangmaixigua

Copy link
Copy Markdown

Summary

  • Decode MoltyBot bridge response attachments into EventResult image/file payloads.
  • Send EventResult attachments through the existing ImageSender/FileSender platform path after final text delivery.
  • Add regression coverage for bridge response attachment decoding and engine delivery.

Root cause

MoltyBot image generation produced files successfully, but the remote bridge path only returned reply text to cc-connect. Generated artifacts were dropped before the Weixin outbound media layer could see them.

Validation

  • go test ./agent/moltybot ./core -run 'TestSessionSend|TestProcessInteractiveEvents_SendsEventResultAttachments|TestEngineSendToSessionWithAttachments' -count=1
  • go test ./cmd/cc-connect -count=1
  • go test ./core -run 'TestCUJ_A3_ImageReachesAgent|TestCUJ_A5_FileReachesAgent' -count=1

Note: full go test ./agent/moltybot ./core -count=1 still hits an existing testing.TempDir RemoveAll cleanup flake in unrelated CUJ attachment tests; those failing cases pass when run directly.

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.

2 participants