istosandClaude Fable 5
e10b5cf1ed
AGENTS.md is the cross-vendor name (opencode, Codex, Gemini CLI read it natively; so does current Claude Code), and the brief goes to every vendor's agents — an opencode work agent previously launched with no project brief at all. The content moves verbatim to AGENTS.md at the root and in manager/local/; each CLAUDE.md becomes a load-bearing compatibility pointer (@AGENTS.md import) for older Claude Code CLIs. update.sh's core-owned file list now carries both names, so updating an old-layout install lands AGENTS.md and replaces the full CLAUDE.md with the pointer instead of resurrecting it. All four core prompts, README, the board.py/taskfiles.py docstrings, the task template and the adapter contract docs now name AGENTS.md; adapters/README.md notes that vendors reading AGENTS.md from the working tree need no adapter work. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Bench
A live kanban for coding-agent work: task files in stage directories are the only source of truth; a stdlib-only board narrates everything that happens to them — agents working in git worktrees, PRs opening on review, CI and Copilot state on the cards, drives of the app from a task's own branch, and an archive that is never a delete.
Install into a repo
git clone <this repo> .task-manager && rm -rf .task-manager/.git
./.task-manager/start.sh # wires the project (idempotent) and serves
The first start.sh clears the distribution's own cards from tasks/,
plans/ and reference/ (printing each removal), so a fresh install
starts with an empty board.
Commit .task-manager/ into the host repo — core is vendored on purpose,
so clones work offline and updates show up in the host's own diffs.
The workflow brief ships as .task-manager/AGENTS.md — the cross-vendor
name coding agents read natively — with CLAUDE.md beside it as a one-line
compatibility pointer. Both live inside .task-manager/, so a host repo's
own root AGENTS.md is never touched.
Update
# in manager/local/.env: BENCH_SOURCE=<this repo's git url>
./.task-manager/update.sh # latest
BENCH_REF=v1 ./.task-manager/update.sh # a specific release tag
Updates replace manager/core/ and the top-level scripts wholesale and
touch nothing else — tasks, plans, reference, and everything under
manager/local/ (your driver, commands, prompt overrides, settings,
state) survive every update. Then python3 .task-manager/install.py and
restart the board.
The three-layer law
Core knows about tasks, worktrees, PRs and events. It knows nothing about
any particular app (drivers do: local/driver/start), agent vendor
(adapters do: core/adapters/), or project (local/ does). Full docs in
AGENTS.md; the adapter contract in manager/core/adapters/README.md.