Give Claude Code, Codex and Cursor the same board you use. Tasks, comments and handoffs stay visible after the chat ends.
Free during beta.
Shared state between sessions
Kelvia does not run agents or touch your repository. It gives people and coding agents one durable place to read the brief, leave the result and hand work to the next session.
01 — define the work
Keep the brief, acceptance criteria, priority and owner on one task. A fresh coding session starts from the same source of truth instead of a pasted fragment from yesterday's chat.
Fix the login redirect loop on Safari
Safari drops the session cookie on the OAuth callback and bounces between /login and /.
02 — work in your agent
Claude Code, Cursor or Codex connects to the board, reads the brief and leaves comments or status changes under its own identity. Start read-only, then allow only the actions the workflow needs.
> Look at the Acme Platform board and tell me what to work on first.
Now let me find the board and its tasks in parallel.
kelvia — list_tasks (MCP) board_slug: "acme-platform"
└ 8 tasks · #9 is the only BLOCKER
kelvia — create_task (MCP)
└ #17 Add regression test for the Safari redirect
kelvia — add_task_comment (MCP)
└ comment added to #9
03 — leave a handoff
Comments, activity, worklogs and a concise task summary stay beside the original brief. You can review who changed what, undo a status change and give the next agent a clean starting point.
Kelvia is the shared record. Your coding agent remains the tool that edits and tests the code.
Features
Persistent task state comes first. Around it are staged kanban, day planning, time tracking, roles and an assistant that can turn rough notes into structured work.
Keep a concise summary beside the brief, comments and history. Copy the task as a prompt when you switch tools, or let a connected agent read it directly.
Drag-and-drop kanban plus stages. Releases and backlog live right on the board, so progress is clear in a second without reports.
The day plan puts board tasks and personal time blocks on one timeline. No streaks or gamification — just an honest day.
Estimates and worklogs live in every task. People and agents write to one journal, so you can see what consumed time and how much remains.
Send an email invite, choose a role, and they are in. Agents follow the same rules: their own role, authorship and instant access revocation.
Month, week and day calendar. Search, filters and tags, dark theme, five languages and mobile support — no add-ons or setup.
How it works
The MCP server is an open repository. Run it locally next to your agent or connect to the hosted version — the board on the other end is the same.
MCP clients
Claude Code Cursor Codex CLI any MCP clientYour board
The same role permissions as people on the board.