fix(codex): keep background memory out of chats

[AksharP5]

What Changed

Codex memory consolidation runs in background threads, but T3 treated their notifications as part of the active chat. Internal messages and tool activity could therefore appear in the user's conversation.

T3 now recognizes both current and legacy memory-thread metadata and filters notifications from those threads before provider events are emitted. Tracking is removed when the internal thread closes.

Why

This keeps background memory maintenance isolated without hiding normal commentary, review or compaction work, or user-created subagents.

Fixes #4683

Validation

• vp test run apps/server/src/provider/Layers/CodexSessionRuntime.test.ts
• vp lint apps/server/src/provider/Layers/CodexSessionRuntime.ts apps/server/src/provider/Layers/CodexSessionRuntime.test.ts
• vp run --filter t3 typecheck
• vp fmt --check apps/server/src/provider/Layers/CodexSessionRuntime.ts apps/server/src/provider/Layers/CodexSessionRuntime.test.ts

Checklist

• This PR is small and focused
• I explained what changed and why
• Screenshots are not applicable because no UI code changed
• Video is not applicable because no animation or interaction changed

Built with gpt-5.6-sol using the Codex harness in T3 Code.

Note

Filter memory consolidation thread notifications out of Codex session events

• Adds makeMemoryConsolidationNotificationFilter in CodexSessionRuntime.ts that tracks threads with threadSource === 'memory_consolidation' (or legacy { subAgent: 'memory_consolidation' } source) and returns a predicate to suppress their notifications.
• Integrates the filter into makeCodexSessionRuntime so that CodexSessionRuntime.events never emits notifications for memory consolidation threads; suppression ends after thread/closed is received.
• Behavioral Change: clients consuming CodexSessionRuntime.events will no longer see any events from memory consolidation sub-agent threads.

^{Macroscope summarized a13c20c.}

---

Note

Low Risk
Scoped to Codex notification routing with unit and integration coverage; does not change auth, persistence, or visible collab subagent behavior.

Overview
Codex memory consolidation background threads were surfacing in the user chat because their app-server notifications flowed through CodexSessionRuntime like normal conversation traffic.

This PR adds makeMemoryConsolidationNotificationFilter, which registers threads marked threadSource === "memory_consolidation" or legacy source.subAgent === "memory_consolidation", suppresses all subsequent notifications for those thread IDs, and clears tracking on thread/closed. handleRawNotification returns early for suppressed notifications so they never become provider events, while other subagent types (review, compact, collab spawns) stay visible.

The collab Stop integration test now replays a memory-consolidation thread and asserts it is interrupted with collab children but does not appear as chat output.

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

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d54fcbda-8bca-4b07-8ba6-9b2c2cfba298

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces runtime behavior that filters memory_consolidation thread notifications from chat, preventing them from appearing in the UI. While well-tested, this is a meaningful change to notification visibility that warrants human review.

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

[AksharP5]

#5219 routes registered thread_spawn collaboration agents into the Agents surface. Memory consolidation is not registered through that path, and its item/agentMessage/delta notifications can still reach the parent chat.

This PR specifically recognizes memory_consolidation, tracks that thread, and suppresses its notifications without affecting normal subagents.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 78cec14. Configure here.}

Dismissing prior approval to re-evaluate 48b0235