| name | anu-recurse |
| description | Use when an agent hits friction with anu itself or is asked to capture, triage, or act on an anu rough edge with `anu recurse`. Covers the recurse backlog, the safety rule for live config, and when to auto-fix versus propose only. |
anu-recurse
Use recurse when the tool substrate gets in the way: pane delivery, spawn ergonomics,
chat pad behavior, box containment, swarm coordination, hooks, or cross-harness
instructions.
Capture
Record the rough edge immediately:
anu recurse "pane spawn has no --cwd for project-routed workers"
Good notes include the capability, symptom, likely surface, and a minimal repro.
Optional inline tokens help classification: capability=pane surface=bin severity=low.
Act Policy
anu recurse act <id> follows two tiers:
- Small/safe:
surface=bin and severity low or med. Act on a branch/worktree,
implement the narrow fix, run the relevant tests/bash/* plus
tests/bash/smoke_test.sh, commit, and open a PR with gpr. Do not merge.
- Risky:
surface=config or severity high. Propose only. Leave the item with
status proposed and a concrete fix sketch for a human or reviewer agent.
Safety Rule
Never hot-patch live config/ to fix anu mid-session. The config tree is loaded by
the running IDE and can break every pane at once. Recurse work is always:
branch/worktree -> test -> PR/gate -> merge
Plugin/bin surfaces are safer than config because they are invoked per command, but
on this machine they may still be the live installed tool through the anu repo
symlink. Treat all recurse changes as branch-first.
Before Finishing
- Update the recurse item status or activity.
- Run the smallest relevant test and
tests/bash/smoke_test.sh.
- Commit the change on the recurse branch and open a PR.
