active-worklisted

# active-work — durable workspace state across Claude sessions `active-work` keeps a small filesystem-backed record for every engineering initiative the user has in flight. Files live under the active root (`~/Library/Application Support/active-work/<slug>/` on macOS — resolved via `env-paths`, which ignores `XDG_DATA_HOME`) and include `brief.md` (frontmatter + prose), `tasks/*.yml`, `sessions/*.md`, `artifacts.yml`, and `sources/` (including `sources/notes/` for durable notes). There is no `handoff.md`: current state is *derived* from the open-loop ledger in the session files, so it cannot go stale. The CLI is `active-work`; `aw <slug>` is a thin launcher that bootstraps a Claude session for an initiative. A long-running daemon, `active-work mcp serve`, exposes MCP tools to Claude Code over HTTP and serves a read-only dashboard at `http://127.0.0.1:7400/ui`. ## When to engage Engage whenever the user signals they want to inspect, mutate, or hand off persistent workspace state. Trigger phrases: - "active work" / "what am I working on" — list initiatives, surface current focus - "bootstrap session" / `/active-work` — load the bootstrap prompt for an initiative - "new initiative" — scaffold a slug with `active-work new` - "add a task" / "mark X done" / "what's blocking me" — task ops via `active-work task` - "record this session" / "update handoff" / "wrap up" / "I'm done" — session capture via `active-work wrap` (there is no handoff file; the phrase still means wrap) - "a