fix(server): dedupe codex subagent item events by t3-code[bot] · Pull Request #5634 · pingdotgg/t3code

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

t3-code · 2026-08-07T17:59:41Z

What Changed

dedupe Codex child item lifecycle notifications by provider item id
preserve a stable provider item id while allowing completion-only notifications through
cover paired and completion-only child item events in the Codex runtime integration test

Why

Codex emits both item/started and item/completed for one subagent tool item. T3 Code translated both into agent activity, so every subagent tool call appeared twice.

Tracking emitted ids for the child thread keeps one logical activity per item, including when completion arrives late, without dropping completion-only notifications.

Checklist

This PR is small and focused
I explained what changed and why
Screenshots are not applicable because this is a server-only fix
Video is not applicable because this is a server-only fix

Created with T3 Code using GPT-5.4.

Note

Medium Risk
Changes collab child notification → synthetic agent event mapping, which drives subagent UI activity; scope is narrow and covered by an integration test.

Overview
Fixes duplicate subagent tool activity when Codex sends both item/started and item/completed for the same child thread item.

CodexSessionRuntime now tracks seen provider item ids per child thread and emits at most one collabAgent/item per id (first lifecycle wins). Synthetic events carry itemLifecycle (started | completed) and a stable itemId; completion-only notifications still surface when no start was recorded. Per-child state is cleared on thread/closed.

The collab integration test replays schema-valid child tool lifecycle from the wire fixture and asserts one agent item for a paired lifecycle plus a separate completion-only case.

^{Reviewed by Cursor Bugbot for commit c20db19. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Dedupe `collabAgent/item` events for child agent tool calls in `makeCodexSessionRuntime`

Introduces a collabChildSeenItemsRef map to track which item ids have already been emitted per child agent thread, suppressing duplicate collabAgent/item events for the same item id.
Emitted collabAgent/item events now include a top-level itemId field and payload.itemLifecycle set to 'started' or 'completed'.
Clears the seen-items entry for a child thread when thread/closed is received.
Behavioral Change: only the first lifecycle event (started or completed) for a given child item id produces a collabAgent/item emission; subsequent events for the same id are suppressed.

^{Macroscope summarized c20db19.}

Assisted-by: T3 Code (GPT-5.4)

github-actions · 2026-08-07T18:04:30Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.4 KiB	11.3 KiB	−11 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−3 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−8 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+1 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	0 B (0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 5661c61 · PR result: c20db19 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 94.6 KiB
Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-08-07T18:06:44Z

Approvability

Verdict: Approved c20db19

This is a straightforward bug fix implementing standard deduplication logic to prevent duplicate agent activity events. The scope is limited to collab child item handling, the pattern is simple (seen-set tracking), and comprehensive integration tests validate the behavior.

^{You can customize Macroscope's approvability policy. Learn more.}

t3dotgg · 2026-08-28T13:31:40Z

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch covers the same Codex child-event duplication problem as #6004. We are keeping that PR as the active implementation, so this branch does not need a second review path.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

fix(server): dedupe codex subagent item events
c20db19
Assisted-by: T3 Code (GPT-5.4)

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 7, 2026