Repository navigation
docs(operations): the wake delivers the caller's reason, not its payload - #137
Merged
Merged
Conversation
The pager section claimed the free-text `reason` is bucketed to an enum before it reaches the woken agent. It is not: it is carried verbatim into the run's context and arrives as `PAPERCLIP_WAKE_REASON`, as `reason` in `PAPERCLIP_WAKE_PAYLOAD_JSON`, and as a rendered line in the wake summary. The bucketing is done by the `diagnostics/wakes` response projection, which is what a drill reads, not the path to the agent. Two gaps are real, and they are different ones. The wake's `source` is never copied into the agent's payload, so no delivered field says a wake came from automation. And a wake that arrives after a run has been dispatched is absorbed into it without reaching it, which is what the 2026-10-05 pair observed: the assignee read a continuation label while the absorbed wake row carried the pager's sentence. That makes `reason` a second channel rather than a substitute, and leaves the description as the only one that survives both. Co-Authored-By: Daedalus <daedalus@agents.flopbut.local> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 54 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 pager section claimed the free-text
reasonis bucketed to an enum before it reaches the woken agent. Reading the wake path shows it is not:wakeup'sreasonlands on the run's context aswakeReasonand is delivered three ways - thePAPERCLIP_WAKE_REASONenvironment variable, thereasonfield ofPAPERCLIP_WAKE_PAYLOAD_JSON, and a rendered- reason: ...line in the wake summary. The enum bucketing belongs to thediagnostics/wakesresponse projection, which collapses an unrecognised reason toother- that is the artifact a drill reads, not what the agent gets.Corroborated on the 2026-10-05 pair: the run the green half's wake was absorbed into carries, on its stored context, the pager's full sentence naming the recovery and the green run URL.
Two gaps are real and are different from the one the doc named:
sourceis not copied into the agent's payload at all, so no delivered field says a wake came from automation.reasondoes not survive coalescing. The payload a run is handed is built once, at dispatch; a wake arriving afterwards is absorbed without reaching it. That is why the assignee read a continuation label while the absorbed wake row carried the pager's sentence.So
reasonis a second channel, not a substitute - delivered on the ordinary production shape where a standing alert has no live run, swallowed in exactly the case these drills keep landing in. The description stays the only channel that survives both.Docs only; no behaviour change. Verification is the Docs workflow building VitePress on this PR.