Is this a reproducible bug?
Current behavior
A Claude Code screen with no dialog on it is detected as blocked. The screen only has agent output that says "Would you like to … yes". herdr agent explain reports state: blocked, rule legacy_no_prompt_blocker.
Removing that sentence gives idle. Adding a visible prompt box also gives idle.
Live effect, seen once: herdr agent prompt to a Claude agent returned agent_blocked. A minute later herdr agent list showed that agent working, with no dialog open. The message was not delivered. I could not capture which rule fired at that moment.
Expected behavior
A Claude screen with no approval or question dialog should not be detected as blocked. Plain prose from the agent should not cause agent prompt to reject a message.
Reproduction
cat > blocked.txt <<'EOF'
● I finished the refactor and the tests pass.
Would you like to open a pull request? If yes, I will push the branch.
⏺ Bash(git status)
⎿ On branch feature
EOF
cat > control.txt <<'EOF'
● I finished the refactor and the tests pass.
⏺ Bash(git status)
⎿ On branch feature
EOF
herdr agent explain --file blocked.txt --agent claude | grep -E '^(state|rule):'
herdr agent explain --file control.txt --agent claude | grep -E '^(state|rule):'
Output:
state: blocked
rule: legacy_no_prompt_blocker (region=whole_recent priority=300)
state: idle
rule: none
Impact
I run several Claude Code sessions that message each other with herdr agent prompt. A false blocked rejects the message, so it is silently lost. The sending session then tells me a session needs a person when it does not.
Environment
- Herdr version: 0.8.2 (client and server)
- Update channel (stable or preview): stable
- Operating system: Arch Linux, kernel 7.2.3
- Terminal: Ghostty
- Shell, if relevant: bash
- Relevant config, if any: Claude detection manifest
2026.09.11.1 (remote, reported current). Claude Code 2.1.266.
Is this a reproducible bug?
Current behavior
A Claude Code screen with no dialog on it is detected as
blocked. The screen only has agent output that says "Would you like to … yes".herdr agent explainreportsstate: blocked, rulelegacy_no_prompt_blocker.Removing that sentence gives
idle. Adding a visible prompt box also givesidle.Live effect, seen once:
herdr agent promptto a Claude agent returnedagent_blocked. A minute laterherdr agent listshowed that agentworking, with no dialog open. The message was not delivered. I could not capture which rule fired at that moment.Expected behavior
A Claude screen with no approval or question dialog should not be detected as
blocked. Plain prose from the agent should not causeagent promptto reject a message.Reproduction
Output:
Impact
I run several Claude Code sessions that message each other with
herdr agent prompt. A falseblockedrejects the message, so it is silently lost. The sending session then tells me a session needs a person when it does not.Environment
2026.09.11.1(remote, reported current). Claude Code 2.1.266.