Skip to content

Commit a95b03a

Browse files
committed
Document three-attempt incomplete todo retry budget
1 parent 3beeeb4 commit a95b03a

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎docs/TODO_FOLLOWUP_CONFIGURATION.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ todo_gate_digest = true
1111

1212
Set `todo_gate_digest = false` to disable it again. Auto-poke must also be enabled for a model follow-up to run (`features.auto_poke`, or `/poke on` in the TUI). `/poke off` does not hide completion reports. This setting does not disable the existing incomplete-todo, long-session review, ownership, completion-confidence, confidence-spike, or final-response follow-ups.
1313

14+
With auto-poke enabled, an unchanged incomplete todo list receives at most three automatic continuation attempts. A change to the incomplete list or a new todo cycle resets that budget. The TUI preserves its remaining budget across self-development reloads. Explicitly turning auto-poke off still stops these retries.
15+
1416
When enabled, recorded todo gate observations produce the existing aggregate reminder once per completion cycle, after open work finishes and before the completion gates. Repeated observations during that cycle do not trigger another aggregate reminder. New open work starts another cycle. The TUI and headless `jcode run` both respect this setting.
1517

1618
SDK clients using the pure shared policy should apply their configuration explicitly:

0 commit comments

Comments
 (0)