They write. You review.
Every task is a chat on the left and a diff on the right. You never scroll a file tree looking for what changed; the change is the screen. Read it, ask for a fix, merge.
df.groupby("city").revenue.sum().plot.bar()Build Great Things
A lightweight agent IDE for builders.Run 10 agents in parallel, seamlessly. Ship only what you approve.
Refund rounds down a rupee⎇ nodebackend…
Message…Send to DevFable 5.1 · highSend
Changes · 2+8 −1
- src/payments/refund.ts+2 −1
- src/payments/refund.test.ts+6 −0
Waiting for Test…Merge
The home screen, live. Click a task on the left to replay its run.
What makes it different
Five things Zokie does that an editor with a chat panel does not.
Ten agents on one MacBook.
Zokie is a 14 MB native app on the system webview, not an Electron editor. Open ten tasks, let ten agents run, and the fan stays quiet. That is the whole reason it exists.
Every task on its own branch.
Your first message names the task, picks feat, bug or chore, and gives each attached repo a git worktree on a fresh branch. Ten agents never touch each other's files.
Claude Code and Codex. Your subscriptions.
Pick Opus, Fable, Sonnet or any GPT model with its effort level, per task. Zokie runs the first-party CLIs you already pay for. No relay, no markup, no keys handed over.
A team, not a chatbot.
God Skills come built in. Send a task to Dev and it builds; Test proves it; the answer comes back as a pull request with evidence. Questions and permissions land as amber cards you cannot miss.
And the rest of the box
Smaller things you will use every day.
Data mode
Swap the diff for a notebook. Ask for a chart or a table and the agent fills the cells in; Python, pandas and matplotlib are ready in a uv env, and the file is a plain .ipynb you can open anywhere.
Your Day
One pill at the top right: spend today against a daily cap, each CLI's plan limits and when they reset, and a 30-day timeline of what shipped, with your hours and Zen score beside it.
PR status and Merge
When a task opens a pull request, its checks show on the board. Green means one click to merge, through gh, without leaving the chat.
Terminal and language servers
Every task has its own login shell in its own worktree. Hover and go-to-definition come from gopls, pyright and tsserver, so reviewing a diff feels like reading in an editor.
Attachments
Drop screenshots, PDFs or CSVs into the chat, several at a time. They show as thumbnails and cards; the agent gets the paths and reads them itself.
Local by default
Settings in a JSON file you can edit by hand, tasks and chat in SQLite, worktrees on disk, a log with no message text. Agents talk to their providers with your own keys. Nothing else leaves the machine.
Why another IDE
I am a product manager who ships code on the side, and for years I did it in VS Code. It was fine. Then agents arrived, and the editor became the bottleneck. With three or four of them running at once, VS Code and everything around it would bring my MacBook to a halt, fans first, then the cursor.
That limit no longer makes sense. Today you can have ten agents working for you in parallel, each on its own branch, each waiting for nothing but your review. The work was never the problem. The tools were too heavy to hold it.
So I fixed it in two steps. God Skills came first: every job goes to a specialist agent with its own rules, its own checks and a memory of what went wrong last time. That alone made me about ten times faster.
Zokie is the second step. It is a small native app built around those agents, where they write the code and I read the diff. It stays light enough to keep ten of them running side by side, and that is how I get from 10x to 100x.
— Rahul (Founder)
Questions?
What is Zokie?
Zokie is a small native macOS app for working with coding agents. Agents such as Claude Code and Codex write the code inside git worktrees, and you review the diff against main on an Agent Board. It is built in Go with Wails and a React frontend, uses the system webview, and weighs about 14 MB.
How is Zokie different from Conductor or Cursor?
Zokie is a review surface, not an editor. It runs the first-party Claude Code and Codex CLIs locally on your own subscriptions, keeps each task in its own worktree on its own branch, and stays light enough that ten agents run side by side on a laptop. God Skills come built in, so every run ends in a tested pull request rather than a wall of edits.
What do I need to run it?
macOS and Claude Code (npm install -g @anthropic-ai/claude-code). Codex adds the GPT models, gh adds PR status and Merge, uv adds Data mode, and gopls, pyright or typescript-language-server add hover and go-to-definition. All four are optional.
Can I still use my editor?
Yes. Every task lives in a normal git worktree under ~/.zokie/tasks, so you can open it in VS Code, Cursor or vim at any time. Zokie is where the agents work and where you review; nothing stops you from editing by hand.
Where does my data go?
Nowhere. Settings live in ~/.zokie/config.json, tasks and chat in ~/.zokie/zokie.db, worktrees under ~/.zokie/tasks. The log holds no message text. The only network calls are the ones Claude Code and Codex make to their own providers with your keys.
What does a task cost?
Whatever the agent's provider charges; Zokie adds nothing. It records Claude Code's cost per turn, shows it on the task, and stops to ask before a turn when today's spend reaches your daily cap. Codex reports tokens, so its plan limits show under Your Day instead.
Is Zokie free?
Yes. Zokie is invite only for now: email xhanthis5@gmail.com to get one. You bring your own Claude Code or Codex subscription.