One window for fourteen coding agents.
It drives the agent CLIs already on your machine, over their own protocols, with your sessions and transcripts on your own disk.
First install is manual · then updates
What you get
Built to run where you work,
not somewhere else.
No browser engine
Rust and GPUI, drawn on the GPU in one process. Nothing embeds Chromium.
Your logins stay yours
It drives the CLIs you already installed and authenticated. No second account, no key handed over.
Nothing forgotten
Working tree and provider conversation are checkpointed together, so a rollback returns both.
Getting started
Running before lunch
Install a harness
Install and authenticate the CLI you already trust.
your own logins · no new keys · nothing to subscribe to
- Harnesses
- OpenCode, Claude Code, Codex CLI, Cursor CLI and ten more
- Logins
- Your existing accounts and rate limits
- Cost
- Nothing new to buy
- Licence
- GPL-3.0-only
Point it at your machine
It finds each binary on launch and talks to it.
found on launch · one window · per-harness protocols
- Protocols
- stream-json, JSON-RPC, ACP, SSE, NDJSON
- Model
- One provider-neutral session model
- Switching
- Each harness keeps its own context
- Storage
- SQLite, blob store, your user profile
Take it with you
Windows for the desk, Android for the room you are in.
desktop and phone · one daemon · in-place updates
- Desktop
- Windows x86_64 and arm64
- Phone
- Universal APK, paired to the daemon
- Reach
- Over Tailscale, with no port forwarding
- Updates
- In place, from a signed feed
In practice
Hand your agents the work you do every day.
A harness works your repository, and you review the diffs it leaves behind.
Every conversation is one long-lived process. Run as many as your machine and your providers allow.
What is this?
A native desktop app for running and managing local coding agents. One window holds your projects and their sessions. It drives the agent CLIs already installed and authenticated on your machine, so your existing logins and rate limits apply unchanged.
Do I need new API keys or subscriptions?
No. Kerenzikov does not replace the agents, it drives them. Install and authenticate at least one CLI first, and it does the rest with what is already there.
How does one app drive fourteen harnesses?
It reaches each provider through its strongest native interface: stream-json, JSON-RPC, the Agent Client Protocol, HTTP with server-sent events, or NDJSON, and normalizes all of them into one provider-neutral model. Each agent keeps its own context when you switch mid-project.
What happens when an agent edits my code?
Kerenzikov checkpoints your working tree under a hidden git ref before each prompt. When you roll back, the code and the provider conversation return to that point together, so they stay in step. You can also branch from an earlier turn.
Where does my data live?
On your disk. Tasks and transcripts go in a local SQLite database, attachments in a blob store, and settings in your user profile. Your data does not pass through any server we run.
How do updates work?
The first install is manual. After that, the Windows build checks a signed update feed on launch and replaces itself in place, and the Android build checks a release manifest and hands the new APK to your installer. Both checks can be turned off in Settings, and a release installs only when you accept it.
Does it phone home?
Only if the build includes an analytics endpoint, and then only coarse events: app version, platform, and which provider ran. Prompts, file paths, project names and provider output stay on your machine. The switch is in Settings.
What about macOS and Linux?
Not built here. This fork targets Windows. The macOS-native desktop code is still in the source tree, but no one maintains or ships those builds, so treat them as unavailable rather than broken. On macOS or Linux, use the upstream project linked in the footer.
Is this a fork?
Yes. It is a fork of an open-source GPL-3.0 coding-agent client, tuned here for Windows, with OpenCode as the best-supported harness. Upstream is credited in the footer.