-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat(todo-continuation): respect awaiting_input status for interactive workflows #739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
feat(todo-continuation): respect awaiting_input status for interactive workflows #739
Conversation
…e workflows Add support for 'awaiting_input' todo status to allow agents to signal intentional pauses while waiting for user input at interactive checkpoints. This enables multi-phase agent workflows (e.g., discovery agents, planning agents) to pause for user confirmation without triggering continuation prompts, while preserving auto-continuation for unintentional stops. Changes: - Add 'awaiting_input' to excluded statuses in getIncompleteCount() - Add getAwaitingInputCount() helper function - Add logging when tasks are awaiting user input
|
All contributors have signed the CLA. Thank you! ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
|
recheck |
|
I’ve signed the CLA with the required comment and retriggered the check, but the CLA job is failing with: Could not update the JSON file: Repository rule violations found. Could someone please check the CLA workflow/branch rules on dev for this? Thank you! |
|
recheck |
Summary
Add support for
awaiting_inputtodo status to allow agents to signal intentional pauses while waiting for user input at interactive checkpoints.Problem
The
todo-continuation-enforceris excellent for ensuring agents complete their work—it's one of the key features that makes Sisyphus so effective. However, some agent workflows intentionally require user input at specific checkpoints:Currently, when an agent pauses to ask for user input while having pending todos, the enforcer interprets this as "agent stopped prematurely" and injects continuation prompts—preventing the user from interacting.
Solution
Add
awaiting_inputas a recognized todo status that signals "this task is intentionally paused waiting for external input."This is a minimal, semantic change that:
Changes
Also added:
getAwaitingInputCount()helper functionExample Usage
When an agent needs user input:
awaiting_inputin_progressorcompletedand continueWhy This Approach
skipAgentsconfigawaiting_inputstatusBackward Compatibility
awaiting_inputbehave exactly as beforeTesting
The existing test file should be extended with:
awaiting_inputstatusawaiting_inputtask is changed toin_progressThank you for building such a powerful agent framework—the todo-continuation-enforcer is genuinely one of the features that makes oh-my-opencode stand out. This small addition would make it even more flexible for diverse agent workflows.
Summary by cubic
Add support for the awaiting_input todo status so agents can pause at interactive checkpoints without being forced to continue. This keeps normal auto-continuation for all other cases.
Written for commit 8ca8ace. Summary will update on new commits.