Celesteops tasks

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:

  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 INSTALL.md). Don't keep retrying unauthenticated.

The /api/auth/* client-management endpoints are first-party only (the desktop app's own UI); an MCP-client token gets 403 there by design.

1. Confirm the app is running

/health is the one endpoint that needs no token — use it as the liveness probe:

curl -s http://127.0.0.1:43121/health

Expect {"ok":true,...}. Connection refused means the desktop app is closed: ask the user to launch it. Don't start it yourself.

2. Find a project's work (minimal prompting)

1. projects_list — every project with open-task and doc counts.
2. tasks_list({ repo: "<repo>" }) — that project's tasks. Add status:"todo" for actionable, or tag:"<theme>" for cross-cutting work.
3. documents_list({ folder: "<repo>" }) — its specs, plans, notes, and drafts.

Over HTTP (with the bearer header from §0): GET /api/tasks?repo=<repo>&status=todo, GET /api/documents?folder=<repo>.

3. Create a task

curl -s -X POST http://127.0.0.1:43121/api/tasks \
  -H "Authorization: Bearer $TOKEN" \
  -H 'content-type: application/json' \
  -d '{
    "title": "Sync baseline in repo-b to match repo-a abc1234",
    "description": "repo-a changed lib/baseline.json (commit abc1234). The mirrored copy in repo-b/baseline.json is stale. Apply the same three-line diff.",
    "area": "ops",
    "priority": "P2",
    "status": "todo",
    "tags": ["repo-b", "repo-a", "sync"],
    "repo": "repo-b",
    "task_kind": "ai"
  }'

Field rules:

• area: content, stream, interview, ops, or health.
• priority: P0 (blocker), P1 (today, max 3 active per due-date), P2 (this week), P3 (backlog).
• status: todo, doing, blocked, done. Default todo.
• repo: the affected repo slug. Makes the task filterable by project.
• task_kind: ai for agent-authored tasks, human otherwise.
• description: put the reasoning, file paths, and commit SHAs here. The title alone rarely carries enough.

4. Update a task

curl -s -X PATCH http://127.0.0.1:43121/api/tasks/<id> \
  -H "Authorization: Bearer $TOKEN" \
  -H 'content-type: application/json' -d '{"status":"doing"}'

Patch any subset: {"status":"done"} to finish, {"status":"blocked"} when waiting on something, {"description":"..."} to add context.

5. Documents

Specs, plans, and notes live as documents foldered by project: <repo>/specs, <repo>/plans, <repo>/notes, <repo>/drafts. Create one with POST /api/documents (or document_create), attach it to its task with document_attach, and cross-link via [[task:<id>]] / [[doc:<id>]] wikilinks.

Decisions and comments (collaborative review)

When you author a spec or plan and hit a genuine fork the user must settle, don't guess. Attach a decision to the doc and let the user resolve it:

• document_decision_create({ document_id, prompt, options: [{label, description?}] }) (min 2 options). Set review_status to in-review and add free-form document_comment_add notes for context. Comments + decisions form an append-only reasoning chain.
• The user resolves decisions (in the app or document_decision_resolve); you can't pick for them. Poll documents_decisions (no args = open queue; pass since to wait on changes) to learn the outcome, then document_get (returns {document, comments, decisions}) to read the chosen option + note, and proceed. document_decision_cancel supersedes a moot one. (Review state uses documents_review the same way.)

Prototypes (embeddable sandboxed HTML)

You can author self-contained HTML artifacts that render inside a doc — page mockups, inline SVG/JS charts, small interactive tools.

• prototype_create({ title, html, tags? }) → id; prototype_update, prototype_get (returns approved), prototype_list, prototype_delete.
• Embed by adding a fenced block to the doc body: a ```prototype fence whose first line is the prototype id (optionally <id> height=640).
• The user must approve a prototype before it first renders. It runs in a strict sandbox (no network, no token/app access). There is no prototype_approve tool — you cannot self-approve, and editing the html re-arms the gate. So: create it, embed the block, tell the user it's awaiting approval, and poll prototype_get.approved to know when they signed off.

Document lifecycle & close-out

Docs have two flags beyond review_status: pinned (evergreen reference — voice guides, procedures, conventions; stays in the Reference tab forever) and archived_at (closed work — hidden from active lists but still searchable). Set either with document_update({ pinned }) / document_update({ archived }). List with documents_list({ includeArchived, archivedOnly, pinnedOnly }).

Tag a sprint's docs cycle:<id>; close it out with documents_archive_cycle({ cycle }) (archives them, skipping pinned).

At the end of a validated piece of work: mark its tasks done, confirm the spec/plan are approved, then archive the cycle's specs/plans/notes so they leave the active set (they remain searchable for history). Never archive pinned reference docs — pin evergreen material instead.

See ../../MCP.md for the full tool contracts.

Don't

• Don't write R2 credentials over the API. The user sets those in the app's Settings panel.
• Don't delete tasks unless asked. Use {"status":"done"} to preserve history.
• Don't bulk-create more than ~10 tasks at once without telling the user.