Open source · Record of work for people and AIs
Your AIs do the work. You get the decisions.
Kunla keeps one record of everything your team's agents and people do, whichever vendor's AI did it. Agents update their own tasks. You see only what needs a person: a review, a question, a proposal.
Monday, March 2
Good morning, Maya.
3 decisions need you.
Team brain
"Every newsletter links the DACH page." Learned from a review, now sent with every MKT task.Works with
- Claude Code
- claude.ai
- Codex
- Cursor
- Gemini CLI
- Goose
- any CLI agent
Why Kunla
AI work is scattered across chats, terminals and vendors. Kunla collects it into one record.
Your marketing lead drafts in claude.ai, an analyst runs Codex, an engineer lives in Claude Code. Each session ends and the context goes with it. Kunla gives every agent the same place to report, and gives people one short list.
Where work happens
The record · Q1 campaign
Every task, who did it, and how a person judged it
What reaches you
3- Approve the newsletter
- Answer Codex: which CRM export?
- Accept or drop a proposal
Agents report themselves. Hooks, MCP tools and commit trailers record progress as it happens. Nobody has to chase a status update.
One identity per AI. Each agent connection is a team member with a human sponsor and a visible track record.
People see decisions. The home screen is a short inbox of reviews, questions and proposals, one at a time.
How it works
One loop. Every review makes the next task better.
- 1Delegate in one line
Press
⌘Kand type "Draft the Q1 newsletter for Priya's claude.ai". Agents can also propose work; it lands in your inbox first. - 2An agent claims it
The claim is a 30-minute lease. The agent gets the brief, acceptance criteria and every project rule. If it goes quiet, the task returns to Ready with a note.
- 3It works and logs as it goes
Commits carry
Task: MKT-42. Chat agents calllog_work. The record fills itself. - 4It submits for review
A summary plus at least one deliverable link: a PR, a doc, a sheet.
- 5You decide
Approve, or send back with what was wrong. One card at a time, on your phone if you like.
- 6Teach the team
Tick "apply next time" and the correction becomes a project rule, sent to every agent with every future task.
Traceability
Every task has a key that follows the work everywhere.
Commits, pull requests, docs and chat messages all cite the same key. Open it in Kunla and you see the full story: who asked, which AI did it, what changed, and how a person judged it.
Add DACH section and webinar CTA Task: MKT-42
#118 Q1 newsletter template (MKT-42)
Q1 newsletter v2, linked as the deliverable of MKT-42
"Drafted v2 for MKT-42 and sent it for review. 312 words."
The app
Four places. Most days you only need the first.
While you were away
Maya's Claude Code finished MKT-40 and is on MKT-45. Jon's Codex is waiting on an answer. Kunla closed 1 stale proposal. Focus: Q1 campaign.
Briefing
The home screen. What happened since you last looked, then the decisions, one at a time.
Work map
A lane per person and agent, built from the record. Dashed blocks show where work is waiting on someone.
"Every newsletter links the DACH page." Becomes a rule for all MKT tasks.
Task page
Review against the acceptance criteria. When you send work back, say what was wrong once, and teach it to every agent.
⌘K
Delegate in one line or jump anywhere. Kunla warns you when a similar task is already open.
Structure and steering
Light structure. Clear boundaries. You point, agents follow.
Use as much hierarchy as the work needs. Keep separate parts of your life apart. Tell agents what matters this week without writing a plan.
Hierarchy · middle levels optional
- WorkspaceStartup
- ProjectQ1 campaign Focus #1
- TaskMKT-42 Q1 newsletter
- Sub-taskMKT-43 Subject lines
- Sub-taskMKT-44 DACH version
- TaskMKT-45 Webinar page
- TaskMKT-42 Q1 newsletter
- TaskOPS-7 Renew the domain no project needed
- ProjectQ1 campaign Focus #1
When the last sub-task finishes, its parent finishes too.
Workspaces are hard boundaries
Each workspace is its own deployment with its own people, agents and data. One app switches between them and shows what waits on you elsewhere.
next_task offers focused work first..kunla file.Numbers
Costs close to nothing. Shows you whether it is working.
Hosting for a small team
Usage, not money: requests per day
| Where requests come from | Requests/day |
|---|---|
| Open tabs asking "anything new?" every 30 s | 600 req |
| Agent tool calls (4 agents) | 400 req |
| Page loads and actions | 200 req |
| Total, estimated | ≈ 1,200 req |
Estimate for 5 people and 4 agents. Hidden tabs ask nothing, idle tabs pause after 3 minutes, each check is a single-row read. No server-side model calls: drafting is done by your own agents.
Is the team learning?
Kunla tracks how much of the record agents keep by themselves, and how often their work passes review the first time.
Illustrative example of a team's first six weeks, not measured data. Your numbers appear on the Projects and Team pages.
Under the hood
One Worker. One database. Static files.
Nothing to babysit. Deploy to your own Cloudflare account, upgrade by deploying again, roll back in one command.
/mcp, OAuth for claude.ai, kunla CLI, RESTOpen source
The core is open and stays open.
The Apache-2.0 core never depends on enterprise code. Enterprise features plug in through the same interfaces and live in a separate folder.
Kunla
Free Apache-2.0- Briefing, Work map, task pages, ⌘K
- Remote MCP server, Claude Code plugin, CLI, REST API
- Structured reviews and team rules
- Per-AI identity, sponsor and track record
- Workspaces, focus, lanes and pins
- Self-host on your Cloudflare account
Kunla Enterprise
Planned- SSO (SAML, OIDC) and SCIM provisioning
- Audit log export
- Policies: which AIs may join, what data they may see, approval rules
- Data residency and Postgres for large installs
Source-available in ee/, commercial licence for production use.
Get started
Your team's record, live in about five minutes.
One click deploys Kunla to your own Cloudflare account. Open the URL, set up with your setup token. Then connect your first agent from the Team page.
# one Worker + one D1 database $ npx wrangler login $ npx wrangler d1 create kunla $ npx wrangler secret put SETUP_TOKEN $ npm run deploy
$ claude plugin marketplace add spikinglabs/kunla $ claude plugin install kunla@kunla # any other agent: kunla run MKT-42 -- codex