Skip to content

Safe outputs MCP server returns success but outputs.jsonl is empty (v0.65.5) #24125

@yaananth

Description

@yaananth

Bug Report

Summary

The safe outputs MCP server accepts tools/call requests and returns {"result":"success"} to the agent, but never persists items to outputs.jsonl. This causes agent_output.json to be {"items":[]}, which means downstream jobs (safe_outputs, custom safe-output jobs like slack_handoff_notify) have nothing to process.

Reproduction

Evidence

  1. Agent called both safe output tools successfully:

    • create_discussion at 13:43:37Z → response: {"result":"success"}
    • slack_handoff_notify at 13:43:47Z → response: {"result":"success"}
  2. MCP Gateway confirmed healthy:

    • safeoutputs server: 2 requests, 2 tool calls, 0 errors, 0% error rate
  3. But outputs were never persisted:

    • safe-output-items.jsonl = 0 bytes (empty)
    • agent_output.json = {"items":[]}
    • safe_outputs job had nothing to process
    • slack_handoff_notify job was skipped (contains(needs.agent.outputs.output_types, 'slack_handoff_notify') = false)
  4. RPC messages confirm full payloads were sent:

    • create_discussion payload included title + full markdown body (~76KB)
    • slack_handoff_notify payload included channel, handles, discussion_title, target_repo, week_of
    • Both received proper {"result":"success"} responses from the HTTP MCP backend
  5. All 8 prior weekly runs (Feb 5 - Mar 26) worked correctly — they all had 1-2 items in agent_output.json

Impact

  • Discussion was never created in the target repo
  • Slack notification was never sent
  • Workflow reported conclusion: success despite producing no output
  • Required manual mitigation (GraphQL discussion creation + direct Slack API call)

Expected Behavior

Items passed to the safe outputs MCP server via tools/call should be persisted to outputs.jsonl so that downstream jobs can process them.

Workaround

Pinned back to v0.65.4 via gh aw compile oncall-handoff-notes --action-tag v0.65.4 as a mitigation.

Metadata

Metadata

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions