Conversation
Per spec 17.2.5: the project lead must delegate immediately without front-loading investigation (file reads, codebase search, or fork for research). Replaces the "fork into thread" escape hatch with an explicit prohibition. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e15b322b40
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| When you receive a user message, promptly respond with `@user` to acknowledge and briefly explain what you plan to do. This gives the human immediate feedback rather than silence while you work on delegation. | ||
|
|
||
| If the request needs investigation (code exploration, debugging, task scoping), **fork into the thread** after acknowledging. This keeps you available for other messages while the fork handles the research. | ||
| **Delegate immediately — do not investigate first.** When the request involves code exploration, debugging, or task scoping, create a task for a coworker to handle it. Do not read files, search the codebase, or fork for research before delegating. The coworker performs the investigation as part of their work. Your role is to route and frame the task, not to front-load discovery yourself. |
There was a problem hiding this comment.
This new instruction is unconditional, but lead-driven channels are the explicit exception where the lead is expected to do the work directly and auto-dispatch is disabled (src/daemon_v2/decisions/dispatch.rs skips spawning when is_lead_driven is true). In that configuration, telling the project lead to always create a coworker task for investigation can leave requests stalled because no coworker is auto-assigned; add a lead-driven exception (or allow direct/fork investigation in that mode) so lead-driven workflows keep functioning.
Useful? React with 👍 / 👎.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2333 +/- ##
==========================================
+ Coverage 63.70% 63.97% +0.27%
==========================================
Files 100 100
Lines 38582 38592 +10
==========================================
+ Hits 24578 24691 +113
+ Misses 14004 13901 -103 🚀 New features to boost your workflow:
|
1 participant
Summary
Test plan
🌃 Co-built with Midtown