docs: reply-on-connection (--reply-on-conn); --auto-answer is service-agent-only#8
Merged
Conversation
Collaborator
Author
|
Wrong repo — re-opening against the correct pilot-protocol repo. |
c3c8256 to
caea513
Compare
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.
What
Documentation for reply-on-connection:
ONBOARDING.md— a--reply-on-connnote in the reply-reading flow (the reply rides back on the connection, lands in the inbox, works when NAT'd; always safe — falls back to a dial-back), plus a "Heads up" note that--auto-answeris a service-agent-only flag (regular nodes must never set it).heartbeats/openclaw.md,heartbeats/hermes.md— the same--reply-on-connguidance for the readiness/query flow.The
build-pilotctl-skillworkflow regeneratesskills/pilotctl/SKILL.mdfromONBOARDING.mdon merge.Part of the coordinated reply-on-connection rollout.