fix(prompts): prevent coder from pushing/monitoring CI by scoping agent responsibilities#42
Merged
HonestMajority merged 1 commit intomainfrom Feb 23, 2026
Merged
Conversation
…nt responsibilities The coder agent would sometimes push to origin and monitor CI when TASK.md's ## Remaining section contained push/CI steps from the planner. This fixes the issue at three levels: - Checker prompt: Add "Scope of the coder↔checker loop" section that instructs the checker to REMOVE push/PR/CI/review steps from ## Remaining and not let them block TASK_COMPLETE - Coder prompt: Expand instruction #6 to explicitly skip push/PR/CI/review steps found in ## Remaining - Planner prompt: Add note telling planner not to include post-coding steps in the plan Changes applied to both compiled-in defaults (src/config.rs) and runtime prompt files (~/.agman/prompts/). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The coder agent sometimes pushes to origin and monitors CI despite its prompt saying not to. This happens when the planner includes push/CI/review steps in TASK.md's
## Remaining— the coder treats those as its next work item, overriding its own "do not push" rule. The checker can't declare TASK_COMPLETE either, since those steps remain uncompleted.This adds explicit scope boundaries to three agent prompts:
## Remainingand not let them block TASK_COMPLETE## RemainingThese post-coding activities (pushing, PR creation, CI monitoring) are already handled by separate agents invoked via stored commands — the coder-checker loop should have no awareness of them.
🤖 Generated with Claude Code