Free · Available now for Windows, macOS and Linux

Your work deserves more than scattered chats.

Kavor gives you one place to delegate work, follow what your agents are doing, keep context around the work, and step in when needed. Use the coding CLI or harness you already trust — Claude Code, Codex, Antigravity, OpenCode or Grok. You stay in control.

See it in practice

See in practice →
A real Kavor session — building Kavor with Kavor.Proof / 001

Specification

Context that survives the session.

Agent sessions are disposable. Engineering context should not be. A Kavor Specification is a simple `.spec.md` file for intent, constraints, acceptance criteria and relevant decisions. It is durable context for humans and agents.

Docs · Specification →

CodingAgent + Terminal

Use the tools you already trust.

Run Claude Code, Codex, Antigravity, OpenCode and Grok as CodingAgent Nodes. Connect agents to Specifications, Files, Sticky Notes and live Terminals. Kavor does not replace your coding agents. It gives you control over the work around them.

Docs · CodingAgent →
Specification

agent-loop.spec.md

Intent
Constraints
Acceptance criteria
Evidence required
CodingAgent

Claude Code

Delegate

CodingAgent

Codex

Follow

CodingAgent

Google Antigravity

Review

Terminal

Live terminal

$ pnpm check

typecheck · tests · build

Sticky Note

Your notes

Agent collaboration

Your agents collaborate. You stay in control.

Connect each CodingAgent to the Specifications, Files and tools it needs. Connected agents can exchange messages and consult completed turns from each other’s sessions.

Follow the work, set boundaries, and step in when needed.

Try Kavor ↘
A connected Canvas. Provider labels and values belong to this reference capture.

CodingAgent Accounts

Multiple accounts? Let Kavor handle the switching.

Add Codex, Claude Code or Grok accounts, choose which ones each Workspace can use, and enable Auto Rotate. At the usage threshold, Kavor switches to an eligible account between turns, resuming the same session and its history.

New accounts stay outside Automatic until you enable them for that Workspace. Switching depends on eligible capacity; provider limits still apply.

Interface illustration with recorded reference values, not a live usage reading.
Reference capture: usage values and renewal times come from the screenshot, not a current provider query.

Agent Kavor · WhatsApp

Keep your agents moving. Even when you step away.

Stay connected to your local CodingAgents through Agent Kavor on WhatsApp. Follow progress, answer questions, and exchange attachments from your phone while work continues on your computer.

WhatsApp available now. More Channels are planned.

Keep Kavor running and signed in on your computer, with network access.

Download Kavor ↘

Docs · Agent Kavor →

A question from your phone. An answer from your local agent.

Watch the demo →

00 / The problem

More agents. More work. More things in your head.

  1. 01

    The problem

    You become the scheduler, memory and dashboard.

    One agent handles a bug. Another reviews it. A terminal runs tests. A Specification lives elsewhere. One agent is waiting; another finished twenty minutes ago. Kavor moves that operational state out of your head and onto a Canvas.

  2. 02

    The Canvas

    One place to see the work.

    See what is being built, which agents and terminals are active, what is connected, what depends on what, and where your attention is needed. Your work, laid out the way you think.

01 / The Manifesto

Software engineering deserves better.

Writing code is no longer the hardest part. Understanding problems, preserving context and making sound decisions is. These principles guide everything we build.

  1. 01

    Work is the unit. Not the conversation.

    The system revolves around work, not chat sessions.

  2. 02

    Questions build context. Context builds software.

    Good software begins with understanding, not implementation.

  3. 03

    Agents execute. Humans engineer.

    Agents are exceptional executors. Responsibility for the decisions remains human.

  4. 04

    Evidence over confidence.

    Confidence is not evidence. Every claim should be inspectable.

  5. 05

    Models evolve. Engineering endures.

    Models will change. The principles behind durable software should survive every generation.

Follow the build

Kavor is built with Kavor — every day.

Follow releases, product experiments and engineering notes from the work as it happens. No manufactured urgency. Just useful updates from the build.

Kavor Community

Help shape how we work with agents.

Share an idea. Ask a question. Show how you work. Report what breaks. Kavor Community is the public place to help shape what comes next.

Open Kavor Community↗