[MaelRB]

Problem

In Codex code mode, one exec tool call can run several commands. The output has one JSON part per command, with that command's exit_code:

{"chunk_id":"a4b7b0","wall_time_seconds":0.0,"exit_code":2,"output":"rg: path: No such file or directory ..."}

The exec span is DEFAULT because the script itself finished. A failing command inside it is only visible in the output text. Filtering or alerting on level misses it.

Change

• Parsing: extractNestedResults (in parse.ts) reads text parts of function_call_output / custom_tool_call_output that are JSON objects with a numeric exit_code. It skips non-JSON or malformed parts without throwing.
• Child spans: emitToolCall adds one exec_command child tool span per nested result, with codex.exit_code (and codex.chunk_id when present) as metadata and the nested output.
  • exit_code >= 2: ERROR, with a status message.
  • exit_code 0 or 1: DEFAULT. rg and grep use 1 for "no match".
• Parent span: level and status message are unchanged. It gets codex.nested_failed_count, but only when that count is above zero.

Tests

• parse.test.ts: the extraction cases, including malformed parts.
• trace.test.ts:
  • an exit-2 child is ERROR with its chunk id and output;
  • an exit-1 child is not ERROR;
  • the parent level and status are unchanged;
  • nothing is emitted when no part can be parsed.

pnpm run lint and pnpm test pass (125/125). I also ran the parser on a real Codex rollout: the failing nested rg came out as exit code 2.

🤖 Generated with Claude Code

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.