celesteops-taskslisted

# CelesteOps task planner — agent access CelesteOps is a local-first creator control panel. It tracks tasks, a content pipeline, stream events, milestones, assets, and documents. Agents working across several repos use it as a shared message board: when you change repo A in a way that affects repo B, leave a task tagged for repo B so the next agent there sees it. Use the `celeste-ops` MCP tools when they're available (they're typed and validated). HTTP is the fallback; examples below use it. ## 0. Authentication The HTTP API enforces token-trust auth: every `/api/*` endpoint **except `/health`** requires a bearer token, so a bare `curl .../api/tasks` returns `401 authentication required`. Two ways in: - **MCP tools (preferred).** The `celeste-ops` MCP shim injects the token for you, so `tasks_list`, `task_create`, etc. need no auth handling. Use these whenever they're available. - **HTTP fallback.** Read the token from your client's MCP config and send it as a bearer header. Claude Code stores it in `~/.claude.json`: ```bash TOKEN=$(node -e "try{const c=require(require('os').homedir()+'/.claude.json');process.stdout.write(c.mcpServers?.['celeste-ops']?.env?.CELESTE_OPS_TOKEN||'')}catch{}") curl -s -H "Authorization: Bearer $TOKEN" http://127.0.0.1:43121/api/tasks ``` Reuse `-H "Authorization: Bearer $TOKEN"` on every `/api/*` call below. An empty `$TOKEN` means this client isn't paired — run `bun run install:mcp --pair <code> --client <slug>` (see I