Review live query keeps polling deleted managed worktrees until app restart

What version of the Codex App are you using?

26.803.5235.0

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

I was investigating a period when my desktop had become severely sluggish and found Codex App repeatedly checking two managed-worktree paths that no longer existed.

For example, I expected a worktree’s review activity to stop after the directory was removed. Instead, the logs continued recording failed Git status operations for that path until I restarted the app:

source=review_model
requestKind=subscribe-live-query
failureReason=wait_failed
cwd=C:/Users/<user>/.codex/worktrees/<id>/<repo>

From 2026-08-10 16:26:46Z through 17:35:13Z, the logs contained 5,591 such failures:

• Worktree f0f3: 4,044
• Worktree fb4a: 1,547

Both directories were absent when checked. Restarting Codex App stopped the activity, and it did not recur during the subsequent observation period.

The failed operations coincided with severe Windows UI and cursor lag. I have not established that this loop caused every responsiveness problem during that period, but thousands of operations against deleted paths are unexpected background work.

What steps can reproduce the bug?

I do not yet have a deterministic clean reproduction. The observed sequence was:

1. Use Codex tasks backed by managed worktrees.
2. Allow review-related live queries to run.
3. The managed-worktree directories are subsequently removed. I did not capture the precise removal transition during this incident.
4. Leave Codex App running.
5. Inspect the Desktop logs and observe continuing source=review_model, requestKind=subscribe-live-query Git operations against the missing paths.
6. Restart Codex App and observe that the operations stop.

This was observed for two separate managed-worktree paths during one app session.

What is the expected behavior?

Removing a managed worktree should also remove any review live-query subscription associated with its path. If one query races with deletion, the missing-path result should terminate or suspend that subscription instead of continuing indefinitely.

Additional information

Related reports cover neighboring failure modes but not this exact lifecycle:

• #30820 covers review_model work against restored existing repositories.
• #32113 covers scans of saved but inactive valid repositories.
• #34473 covers retries while resolving malformed Git roots.
• #33401 covers processes retaining a removed managed-worktree directory.

This report is specifically about a subscribe-live-query subscription retaining paths after the managed worktrees themselves no longer exist.

Maintainer question: Is managed-worktree removal expected to unregister every review live-query subscription associated with that path?

No /feedback ID was captured during the incident. I can provide additional sanitized log excerpts if useful.

Start by tracing the review_model subscribe-live-query lifecycle alongside managed-worktree removal handling. Reproduce the reported sequence if possible, then inspect Desktop logs for continued Git operations against deleted paths. Done means removing a managed worktree terminates or suspends its associated review subscription without requiring an app restart.