fix(server): stop completed Codex threads from staying stuck on working - #7937
All clear
All clear
Details
Note
Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.
🔍 Agent activity — 3 tool calls
💭 Looking at the diff, it's a small behavior change in CodexAdapter.ts plus a new test. Let me check the relevant files for convention issues.
1. browse_code — apps/server/src/provider/Layers/CodexAdapter.ts
2. browse_code — apps/server/src/provider/Layers/CodexAdapter.ts
💭 This is a pure behavior change confined to a mapping function, with no import or service definition changes, so adding a focused test for it seems justified rather than excessive. I want to check the test file itself for convention issues, like whether imports from "effect" are consolidated properly.
3. browse_code — apps/server/src/provider/Layers/CodexAdapter.test.ts
💭 The existing test file patterns are legacy and outside the PR's changed scope, and the new test additions use proper namespaced imports with Effect.gen, Stream, and Fiber correctly. Since the behavior change is accompanied by a focused test satisfying the requirement, I have no findings to report, though I need to make sure my response still conforms to the expected JSON schema.
Agent Credits: 25 credits