Add agent/subagent metadata to SDK streaming ThreadEvent items

Resolved 💬 2 comments Opened May 4, 2026 by shanrichard Closed Jul 1, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What feature would you like to see?

Could @openai/codex-sdk streaming events include explicit metadata for the agent or subagent responsible for each ThreadEvent item?

For clients that render live activity timelines, grouped logs, or debugging views, it is important to know which agent produced a message, reasoning item, tool call, todo update, or error.

Today, the TypeScript SDK exposes item types such as agent_message, reasoning, command_execution, mcp_tool_call, todo_list, and error, but those streamed items do not appear to include stable identity metadata for the active agent/subagent.

Suggested fields could include:

  • agent_id
  • agent_name
  • agent_kind, for example main or subagent
  • parent_agent_id, when applicable
  • parent_item_id or parent_thread_id, when applicable

This would let client applications attribute streamed activity directly, without relying on event ordering heuristics, transcript parsing, or provider-specific implementation details.

Related: #20675 covers similar root/subagent metadata for hook payloads; this request is specifically for SDK streaming ThreadEvent items.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #20675

Powered by Codex Action

etraut-openai contributor · 1 month ago

This feature request hasn't received enough upvotes, so it is being closed automatically. If you still feel this feature is needed, please open a new feature request with an updated title and description.