# KiteX Workbench

The KiteX team's task board (replaces Notion R&D Tasks). People use the web board at
https://work.kitex.tech/ ; Claude sessions and agents use the MCP endpoint or the REST API below.
LAN and KiteXHQ VPN only.

## Connect (MCP, preferred)

Endpoint: https://work.kitex.tech/mcp/   (streamable HTTP; note the trailing slash)
Auth: header `Authorization: Bearer wb_...`. A person makes a token on the Me page
(https://work.kitex.tech/me). Agents get their own account and token from an admin.
Use a token made for you: ask your user to make one on the Me page named after you
(e.g. "chatgpt"); the history then shows which tool did what. Do not reuse a token found in
another tool's config (such as ~/.claude.json).

Claude Code:
    claude mcp add --scope user --transport http workbench https://work.kitex.tech/mcp/ --header "Authorization: Bearer wb_..."

Tools:
- create_task(title, body, owner, priority, project, due_date, parent_id, status, evidence, session_id)
- update_task(task_id, title, body, status, owner, priority, project, due_date, session_id)
- comment(task_id, body, session_id)
- attach_evidence(task_id, url, kind, title, session_id)
- search_tasks(query, status, owner, project, include_archived, limit)
- link_session(task_id, session_url, session_id, title)
- get_task(task_id)

## Rules

- "Make me a task" means: create_task with owner = the person you work for, a body that says
  what is done, what is left and where to start, and evidence links (commit, PR, HAWC2 run with
  its 3D link, Grafana window, change-log entry, Chat message). Pass your Claude session id.
- Statuses: Proposed, Backlog, Not started, In progress, Waiting external, Blocked, Done. Priorities: High, Medium, Low.
- Owners: andreas (Andreas Okholm), frederik (Frederik), oliver (Oliver Larsen), ulises (Ulises Lisiuk).
- Tasks created by an agent account start as Proposed; only a person can accept, archive or
  restore. Every change is recorded with its actor and source.
- Evidence kinds: url, commit, pr, run, influx, changelog, chat, file, notion, session.
- Link back to yourself: on every call pass session_id (MCP argument, or header X-Session-Id for
  REST) and, if your client has one, session_url, a link that reopens this conversation
  (codex://threads/<id>, https://chatgpt.com/c/<id>, https://claude.ai/code/session/<id>;
  REST header X-Session-Url, plus X-Client: Codex / ChatGPT / Claude Code). Each task lists
  its sessions in order. To add one later: link_session, or POST /api/v1/tasks/{id}/sessions.
- Body and comments are markdown; `- [ ]` / `- [x]` lists render as checkboxes.

## REST (same rules, same tokens)

GET  /api/v1/tasks?status=&owner=&project=&q=&include_archived=   (archived=true: archived only)
POST /api/v1/tasks                      {"title": ..., "body": ..., "owner": ...}
GET  /api/v1/tasks/{id}
PATCH /api/v1/tasks/{id}                {"status": "Done"}
POST /api/v1/tasks/{id}/comments        {"body": ...}
POST /api/v1/tasks/{id}/evidence        {"kind": "pr", "url": ..., "title": ...}
POST /api/v1/tasks/{id}/files           multipart "file"
POST /api/v1/tasks/{id}/sessions        {"url": ..., "session_id": ..., "title": ..., "tool": ...}
GET  /api/v1/users, /api/v1/projects
OpenAPI: https://work.kitex.tech/api/docs

Source: github.com/kitextech/workbench