docs: say what Devin CLI actually carries - #6
Merged
Merged
Conversation
The message table did not distinguish the two CLIs, so it read as though a finished Devin turn shows the reply that ended it. It does not: Devin's Stop payload reports stop_hook_active and no reply text, so `done` has a state and an age and nothing under them. Verified by putting Devin's documented event set through the hook with DEVIN_PROJECT_DIR set. It carries a message for the two states that matter most — the prompt it is working on, and the tool it wants to run — and nothing for done. `err` and `ask` never arise at all, since Devin has neither StopFailure nor Elicitation; the states table already said so, the message table did not. Also noted that notifications fire for both, since notify() keys on the state rather than on which agent reached it — a blocked Devin session notifies exactly like a Claude Code one, which was not written down anywhere. Co-Authored-By: Claude Opus 5 (1M context) <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.
The message table did not distinguish the two CLIs, so it read as though a
finished Devin turn shows the reply that ended it. It does not — Devin's
Stoppayload reports
stop_hook_activeand no reply text, sodonehas a state andan age and nothing under them.
Verified by putting Devin's documented event set through the hook with
DEVIN_PROJECT_DIRset:UserPromptSubmitbusy+refactor the parserPostToolUsebusy, prompt survivesPermissionRequestperm+exec: rm -rf buildStopdone, message emptySo Devin carries a message for the two states that matter most — what it is
working on, and what it wants to run — and nothing for
done.errandasknever arise at all, since Devin has neither
StopFailurenorElicitation. Thestates table already said that; the message table did not.
Also written down for the first time: notifications fire for both CLIs, because
notify()keys on the state rather than on which agent reached it. A blockedDevin session notifies exactly like a Claude Code one.
Docs only — no code changes. The mapping itself was already correct and
future-proof: if Devin ever gains those events, the hook already handles them.
🤖 Generated with Claude Code