enesyaks/Kervan

English · Türkçe
Run your coding agents on your own server. Drive them all from your Mac.
A server that runs Claude Code, Codex and Gemini on a Linux machine at home or in the cloud,
and a native macOS app that manages them from one place.
Work goes on while your Mac sleeps; when you come back, you pick up where the agents are.
A project session: the agent shares its plan, edits files and runs the tests; the diff sits in the side panel, one click to commit.
## Contents
Why Kervan
Features
How it works
Installation
Agents and keys
Security
Development
Project layout
Contributing and license
## Why Kervan
Coding agents work for hours on long tasks. On a laptop, the lid closes, the Wi-Fi changes, the battery dies
and the turn is cut off. Kervan moves the agents to a machine that is always on and keeps the controls on your Mac:
Work keeps going. Agents run on the server; a turn continues even when the Mac disconnects, and the
history streams back when it reconnects.
All in one place. Claude Code, Codex and Gemini in the same app, the same project, even the same team.
Everything stays yours. Code, session history and API keys stay on your machine; keys never reach the Mac.
Set up in minutes. The app installs the server on a fresh Ubuntu machine over SSH by itself.
## Features
### See changes, undo them, commit them
Every edit the agent makes opens as a line-by-line diff in the chat. The Changes panel lists the files
changed since the session's first or last message; revert one file or all of them, and commit from there
when the folder is a git repository. Kervan snapshots the folder before every message in a store of its own,
so your git history is never touched.
### Plan, commands, files
As the agent shares its to-do list, a plan card fills in above the composer. Type / for the agent's own
commands (/review, /compact…) or @ for files in the folder; a picked file is attached to the message.
Paste a screenshot with ⌘V and it reaches agents that see images as an image; the mic button starts
macOS dictation.
### You stay in control
Before running a command or deleting a file, the agent stops and waits for your approval; the Dock icon
and a notification tell you. You can edit and resend a message, or rewind the folder to before any
message. The conversation stays, and the agent is told what happened. For a task you trust, tick Auto-approve
when you create it or under the message box: the agent then only stops before major changes, such as pushing, deleting folders, rewriting
git history, deploying, or touching secrets or files outside the task's folder. It is a convenience, not a sandbox: a
script the agent writes can still do these things unseen.
### Projects
Make a project from a folder on the server, a git repository the server clones, or a new empty folder. The
project's instructions (code style, test command, things to watch out for) are given to every agent in
it before its first message. In a git repository each session works on a branch of its own (a worktree), so several
agents can work on one project at once without touching each other's files.
### Scheduled tasks
"Run the tests at 09:00 on weekdays and fix what breaks" or "summarize new issues every hour". The server is