Skip to content

docs: describe back-to-back ack.sh calls in the README #228

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.

Sign up for GitHub

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

Open
tupe12334 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: describe back-to-back ack.sh calls in the README #228

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ agent retries → next item shown
action approved
```

Each checklist item requires one full hook invocation to acknowledge. The agent cannot skip ahead.
Items must be acknowledged in flow order: each `ack.sh` call advances exactly one state. `ack.sh` may be run several times in a row without retrying the gated action in between (since 0.2.1), so the hook does not guarantee the agent was shown every question before acknowledging it. The audit log records every ack.

---

Expand Down
Loading