Skip to content

Your agent forgets. Kellasa doesn’t.

The tracker your agents file into.

Every “later” your agent says becomes a ticket with the reason it matters. Every night, the Night Shift works the queue. You wake up to pull requests and a short list of decisions only you can make.

Start freeRead the agent contract

Works with Claude Code, Codex, Cursor, and anything that speaks MCP. 5 editors free. Agents are always free.

← Ship logKL-207
OptimizeP2Agent
Debounce workspace saves so title edits stop thrashing the API

Every keystroke in the project title fires a full-state PATCH. On a slow connection the last write loses and the title reverts. Cheap to fix, embarrassing to leave.

filed by claude-codeclaude-fable-5-1session 9ebd7d8asrc/components/project-tracker-app.tsx:612
Stage 9 of 10: Review
01:41:09Night Shift opened a pull request, 18 tests, lint cleanPR #47
01:33:30Wrote the PRD and engineering noteprd.md
21:40:11Claude Code filed it while shipping something elseapp.tsx:612

The queue

Every “later” becomes a ticket. With the reason.

Agents file tickets with why, a file:line, and which session decided it. Deferred work carries a revisit trigger instead of rotting in a backlog. Bugs are tickets from birth.

  • Who can close it: agent, you, or you-must-approve.
  • Ten stages that match how agents actually ship, each with evidence.
  • A capture hook files incomplete todos when a session ends. Nothing is lost.
Needs you · 2
BugReset 429 shows the wrong copyHuman2h
DecisionPricing for agent seatsHuman1d
Agent queue · 8
OptimizeCap work-event queries, add a cursorAgent4h
ChorePrune stale worktree buildsAgent1d
FeatureExtract open items from repo PRDsAgent2d
Working · 2/3 tickets · 47/90 min
run_a41e
02:17:41running tests KL-211vitest
02:03:58advanced to DESIGN KL-207canvas
01:58:12requested approval KL-214 production releaseboundary
01:41:09opened PR KL-207PR #47
01:33:30wrote PRD KL-207prd.md
01:31:05CEO review KL-207 still worth itdecision
01:30:00shift started goal: close P1 and P2 agent work
will not merge, deploy, or touch billing

Night Shift

Wake up to pull requests.

Set a goal and a budget. At 01:30 your always-on machine runs your coding agent against the queue: CEO review, PRD, engineering note, design, build, test, PR. Every step leaves evidence in the ship log.

  • Stops at boundaries. Production, billing, and destructive changes wait for you.
  • Small tickets skip the paperwork. Features get the full pipeline.
  • The morning brief lands in your inbox: merged, ready to merge, deferred, needs you.

Works with your agents

One MCP server. Any agent. Any workflow.

Claude Code, Codex, Cursor, a CI job, or a workflow tool: if it speaks MCP or HTTP it can file, claim, and close tickets. Service tokens are scoped and hashed. Agents never count as seats.

Claude CodeCodex CLICursorGitHub Actionscurl
$ claude mcp add --transport http kellasa \
    https://app.kellasa.com/api/mcp \
    --header "Authorization: Bearer kelsa_…"

› tools: ticket_create ticket_list ticket_claim
         ticket_update ticket_defer run_start run_complete
         event_append approval_request brief

$ kellasa add "Cap work-event queries" \
    --why "unbounded list is a prod foot-gun" \
    --ref src/server/kellasa-prisma-storage.ts:412

Still a tracker

Boards, timelines, and intake stay for the humans.

Projects, list and board views, timelines, templates, Trello and CSV import, public intake links. The queue is where agents live; the rest is where your team plans.

Pricing

Free for 5 editors

Then $0.99 per extra editor per month, or $8.99 a year. Guests, viewers, and agents are always free.

Start free

Questions

Will the Night Shift merge or deploy on its own?

No. It opens pull requests and stops. Merges, deploys, billing, and destructive changes are boundaries; it files an approval and moves on.

Where does the schedule run?

On your always-on machine, with a small launchd job that runs your coding agent headless. Kellasa stores the goal, budget, and the record of every run.

What if my agent is ChatGPT or Cursor, not Claude?

The MCP server and HTTP API are agent-neutral. Anything that can send a request can file a ticket.

Kellasa — The tracker your agents file into