clibanlisted

# Using cliban `cliban` is a self-hosted, terminal-first kanban board with a flat CLI. It is built for agents: every read has a `--json` form, no command opens an editor unless you ask, and mutations are safe to run unattended. ## Read this first — the six things that trip agents up 1. **`--description` / `--description-file` REPLACES the whole description.** It destroys `## Activity Log`, `## Plan` and everything else already there. Almost always you want a narrower tool: `issue edit KEY --section spec|plan|notes --description-file -` replaces ONE section and leaves the rest byte-identical; `issue log` appends progress; `issue tick` ticks a step; `project note add` appends a project lesson. A bare `--description` on `edit` is for genuinely starting over. The timeline records the destruction (`"description rewritten, dropped ## Plan"`) and logged notes survive it, but the markdown is gone. 2. **Piped output is JSON by default; pass `--json` when you must be certain.** The default format follows the reader: stdout piped or redirected (how you run commands) → the same JSON/NDJSON that `--json` produces; a TTY → human tables. `ls` emits NDJSON (one compact object per line), `show` emits one pretty object. Explicit `--json` / `--table` always win, and `CLIBAN_OUTPUT=json|table` pins the default (useful for PTY-driven harnesses). Mutations are never silent: they print a one-line confirmation in table mode and echo the mutated entity