REST API feature - cline kanban ticket management using cline

[umiodrag]

First of all - GREAT JOB!!! THANK YOU ALL! YOU'RE JUST AWESOME!!! :)

I have an idea or maybe a few...

Why do we use kanbanat the first place - to improve work overview. But if we use cline at the first place as an agent manager why shouldn't we use it as itself kanban manager?

Than we would need some modifications:

1. kanban should be renamed to 'CLINEBAN' so the cline should know what user is talking about (i mean you can create custom rules for this but why if this is already packed with cline itself?)
2. we would need some rest api endpoints so the cline can manage tickets
3. the best cline has done itself is editing board.json but that's not the way it should work anyways

---

This way user can create/edit/change status of any ticket but using web interface or using cline itself. Any toughts?

---

I've prepared the endpoints my cline is missing - if i misunderstood something please add those things to documentation. THANKS!!! :)

---

REST API for programmatic card management (create, move, update, delete)

Clineban currently has no programmatic API. It is a single-page application that reads board.json on startup and manages state entirely in memory. This makes it impossible for external tools — AI assistants, CI/CD pipelines, CLI scripts — to create, read, update, move, or delete cards without manual browser interaction.

I propose adding a REST API under /api/v1 with the following endpoints:

Health

GET /health → { status: "ok", version: "...", timestamp: ... }

Boards

GET  /boards                  → list all boards [{ id, name }]
GET  /boards/:boardId         → full board state (columns + cards)

Columns

GET  /boards/:boardId/columns → [{ id, title, cardCount }]

Cards (full CRUD)

GET    /boards/:boardId/cards                → list (?column=backlog|in_progress|review|done)
GET    /boards/:boardId/cards/:cardId        → single card
POST   /boards/:boardId/cards                → create { title, prompt, ... }
PUT    /boards/:boardId/cards/:cardId        → update fields
PATCH  /boards/:boardId/cards/:cardId/move   → { column: "in_progress" }
DELETE /boards/:boardId/cards/:cardId        → delete

Card Dependencies

POST   /boards/:boardId/cards/:cardId/dependencies       → { dependsOnCardId }
DELETE /boards/:boardId/cards/:cardId/dependencies/:depId → unlink

Card JSON schema (for all create/update responses):

{
  "id": "string",
  "boardId": "string",
  "column": "backlog | in_progress | review | done",
  "title": "string",
  "prompt": "string",
  "startInPlanMode": false,
  "autoReviewEnabled": false,
  "autoReviewMode": "commit",
  "baseRef": "main",
  "dependencyIds": ["id1"],
  "createdAt": 0,
  "updatedAt": 0
}

Use cases enabled:

1. AI assistants can create, start, and complete cards during a session
2. CI/CD pipelines can post failure/status cards automatically
3. CLI scripts can bulk-create from templates or migrate boards
4. Board state can sync with version control automatically
5. Headless server usage without requiring a browser

This would make Clineban a fully automatable project management tool instead of a manual-only UI.