ac-list
Skill1 starsChanged 50 days agoMITView on GitHub
Check Auto-Claude kanban card status for any project without the GUI. Shows all specs with [OK] (complete), [--] (pending), [>>] (in-progress) status. Use when checking what specs are pending, complete, or running in any Auto-Claude project.
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-ideateSkill
- ac-roadmapSkill
- agentbridge-mcpSkill
- almanacSkill
- almquist-shellSkill
- ansible-fleetSkill
- apfsSkill
- apple-siliconSkill
- arena-actorsSkill
- asustor-nasSkill
- a-teamSkill
- atem-miniSkill
- at-tuiSkill
- autoresearchSkill
- babysitSkill
- bonzibuddySkill
- bop-brainstormSkill
- bop-catalogSkill
- bop-onSkill
- bop-teamSkill
- bop-workflowSkill
- bsd-portabilitySkill
- code-refactoringSkill
- codex-personasSkill
- context-graphSkill
- councilSkill
- datadog-backupSkill
- dd-tagsSkill
- delegateSkill
- deming-pdsaSkill
- deterministic-replaySkill
- dispatch-nuSkill
- durable-commitSkill
- elixir-gastown-opsSkill
- ergo-ircSkill
- esp32-tang-bridgeSkill
- fleet-evalSkill
- fleet-ircSkill
- freebsd-build-vmSkill
- freebsd-piSkill
- freebsdSkill
- ganttSkill
- gastown-opsSkill
- gastown-slingSkill
- gh-authSkill
- gitea-releaseSkill
- gitea-runnerSkill
- henshuSkill
- irclaw-cluster-opsSkill
- irclaw-research-teamSkill
- irc-taskSkill
- jail-factorySkill
- jjSkill
- jobcard-systemSkill
- kubernetesSkill
- leptosSkill
- loreSkill
- lower-bound-reviewSkill
- macvlan-netSkill
- The first 60 shown.
The file
Files
ac-list — Auto-Claude Headless Kanban Status
Shows all specs and their kanban state for a project without opening the GUI.
Command
PYTHONPATH=/Applications/Auto-Claude.app/Contents/Resources/python-site-packages \
env -u CLAUDECODE \
/Applications/Auto-Claude.app/Contents/Resources/python/bin/python3 \
/Applications/Auto-Claude.app/Contents/Resources/backend/run.py \
--list --project-dir /path/to/projectStatus symbols
| Symbol | Meaning |
[OK] | Complete — all subtasks done |
[--] | Pending / initialized — not started |
[>>] | In progress — currently running |
[XX] | Failed |
Filter examples
# Count pending specs
... --list --project-dir $HOME/efi | grep "\[--\]" | wc -l
# Show only complete
... --list --project-dir $HOME/efi | grep "\[OK\]"
# Show only pending
... --list --project-dir $HOME/efi | grep "\[--\]"
# Show in-progress
... --list --project-dir $HOME/efi | grep "\[>>\]"Projects
| Project | Path |
| dub (EFI bootloader) | $HOME/efi |
| bop (jobcard system) | $HOME/bop |
| zam (unikernel VM reader) | $HOME/zam |
Notes
env -u CLAUDECODEis required — strips the Claude Code env var so run.py uses OAuth, not an API key- This reads directly from
.auto-claude/specs/*/on disk — no GUI, no network - Complements
./dispatch.nu statuswhich tracks wave-level completion; this shows Auto-Claude's own subtask-level view [OK]in ac-list + entry indispatch-state.jsoncompleted = fully done[OK]in ac-list but NOT indispatch-state.json= completed butmark-donenever fired → run./dispatch.nu mark-done NNN
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

