Repository navigation
feat: a headless conversation reply has a deadline - #224
Merged
Merged
Conversation
With --with-dialogue the run waits for an answer, but only for BARO_CONVERSATION_REPLY_TIMEOUT_SECS (default 30 min); then baro decides on its own as it does without a peer. conversation_needs_input carries reply_timeout_secs so a client can show the deadline, and the runner closes its front-door gate on conversation_clarification_resolved so a late reply is rejected instead of delivered to nobody. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
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
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.
Groundwork for answering baro's front-door question from the cloud dashboard.
--with-dialogue, headless waits for a reply only forBARO_CONVERSATION_REPLY_TIMEOUT_SECS(default 30 min), then decides on its own viaresolve_clarification_without_a_human. Without it nothing changes (0.118.9: decide immediately).conversation_needs_inputcarriesreply_timeout_secsso the cloud can show the deadline.conversation_clarification_resolved, so a late reply is rejected (command_ack) instead of written to a gate nobody waits on.baro-cloud gates
conversation: trueon runner >= 0.119.0, so this ships as 0.119.0.🤖 Generated with Claude Code