During a review session, a parallel bash tool call had two gh api repos/.../pulls/.../comments calls return HTTP 404. The tool result itself was handled, but the next Codex API request failed with:
Invalid body: failed to parse JSON value
Trace evidence: .graff/traces/1334ab719e05af58.jsonl records tool call_id=5 with is_error=true, followed by api turn=1 ... req_bytes=104591 ... is_error=true. Earlier API requests in the same turn succeeded. This suggests an error tool result (possibly combined with parallel tool output) is not being safely JSON-escaped before being included in the next request. Repo/repro details available in the local trace.
During a review session, a parallel bash tool call had two
gh api repos/.../pulls/.../commentscalls return HTTP 404. The tool result itself was handled, but the next Codex API request failed with:Invalid body: failed to parse JSON valueTrace evidence:
.graff/traces/1334ab719e05af58.jsonlrecordstool call_id=5withis_error=true, followed byapi turn=1 ... req_bytes=104591 ... is_error=true. Earlier API requests in the same turn succeeded. This suggests an error tool result (possibly combined with parallel tool output) is not being safely JSON-escaped before being included in the next request. Repo/repro details available in the local trace.