feat(cli): add wait mode to agent send#83
Merged
Conversation
Add agent send --wait so scripts can send a prompt to an existing interactive agent session and capture the new assistant response from stdout. - seed transcript length before terminal delivery - poll the target session transcript for new assistant messages - complete when the agent returns to waiting, or idle after assistant output - keep status and warning output on stderr in wait mode - validate missing session files and unsupported adapters before sending - add focused wait-loop and command coverage
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.
Summary
Adds
agent send --waitso scripts can send a prompt to an existing interactive agent session and capture the new assistant response from stdout.Notes
This keeps the existing fire-and-forget
agent sendbehavior when--waitis not provided. The first version uses a fixed 10-minute defensive wait cap; configurable--timeoutremains a separate backlog item.