33 features, grouped by what you are doing. Where it matters, a card says whether it works
with Claude Code and Codex on your Mac, and in a remote folder over SSH. Koloft also runs
Meta's Muse Code and Google's Antigravity CLI; the
docs pages say what each does for them.
✓ works
◐ works, with a difference (see the note)
– not there
⌘P, one box for everything
Type a line. It starts, finds or searches.
The one box you keep coming back to: new work, any old session, anything you said.
One sentence → a working session
Press ⌘P, type “add a forgot-password link to the login page” and hit ⏎. Assist picks
the folder, opens a worktree when the folder is a git repo, names the session, and the
agent you picked starts on your words. Type @ and a folder's name to pick the folder
yourself. The ▾ beside the button, or ⌘⏎, picks another agent; ⇧⏎ starts a new line.
✓ Claude Code
✓ Codex
✓ Remote
Needs Assist on (Settings ▸ Assist); with it off, ⏎ opens the folder picker and keeps
your words, unless you named a folder with @. In a remote folder the session opens on
that machine.
Type “timer” and press ⌥⏎: every session in every folder that mentions it, with a line
of context. Click one to carry on. Nothing is copied into an index of ours.
Breathing orange: working. Amber: waiting for your OK. Green: its turn is done. A red
dot means it is your move, and stays until the session works again. In the sidebar, a
short line under an open row says what it did last, or what it asks.
Nine tabs and no idea which to look at? The bell by the sidebar button counts the
sessions waiting for you. Click it, or press ⌘J, to go to the one that has waited
longest; the next click goes to the next one.
After about half an hour of quiet a session’s program goes to sleep; its row, tab,
screen and Workbench stay. Click it, or send it a message, and it wakes in the same
tab. Quit and reopen Koloft: running ones run again, sleeping ones stay asleep.
Each worktree session gets KOLOFT_PORT_OFFSET (1–99, the same number for the same
worktree name), so two dev servers do not fight over port 3000. Files listed in
.worktreeinclude, such as .env, are copied into each new worktree.
The agent keeps its screen. Everything else hangs beside it.
The middle is the agent’s own terminal; Koloft draws nothing over it. Beside it hangs a
Workbench for that one session. Each folder has
a Workbench of its own too.
Every change, live
Each file the agent touches appears in Changes; open it for a live diff. Compare
against where the branch started, or against what is not committed yet.
In a web tab, click the pick button, then any part of the page: its HTML, its CSS and
a picture of it land in the session’s input box for you to add to and send.
The GitHub button shows the branch’s pull request and a light for its checks. Commit
and push from there, and one click opens GitHub's new-PR page for the branch; when a
check fails, one click sends its log to the session.
Every session Koloft starts gets a koloft command and a real browser.
It drives your browser
With the playwright-cli that ships inside, the agent opens pages in its own Workbench
tabs, clicks, fills and reads them, signed in as you.
✓ Claude Code
✓ Codex
◐ Remote
In a remote folder, Claude Code only, with a playwright-cli Koloft fetches there with
npm; it can never open your Mac's files or its local web servers.
When the agent runs open report.md or open http://localhost:3000, it shows in that
session’s Workbench, not a new browser window, and your cursor stays in the terminal.
✓ Claude Code
✓ Codex
◐ Remote
In a remote folder it works only with "Let agents use Koloft" on, and localhost still
means your Mac, not the machine.
Your butler, Alfred until you rename it, is Koloft’s own AI: one Claude, Codex, Muse or
Antigravity session on an account you added, first in the sessions list.
Starts sessions, hears them finish
Say “have tidewatch fix the login bug”: your butler starts the session, answers its
questions the way you tell it, and tells you when it is done. A job outside your
projects, or a ⌘P request Koloft cannot do by itself (with Assist on), goes to a
helper of its own, which hangs under its row, does the job and reports back.
✓ Claude Code
✓ Codex
✓ Remote
The butler runs on your Mac; it can start, message, read and resume a session in a
remote folder too.
Bind your butler to your own Discord bot and talk to it in one channel: it reaches
your sessions for you, sends you files and pictures of pages, and a form asks you for
an admin password or a sign-in code a session needs. No server of ours in between.
✓ Claude Code
✓ Codex
✓ Remote
Questions from your butler and its helpers come to the channel when you are away from
Koloft. A session in your folders asks only at the Mac; tell your butler what to pick,
and it answers. While you are away, your butler hears when a session finishes or
waits, and tells you if you are needed.
One click: a helper of your butler makes the bot, and a server and channel if you have
none, doing the clicking on Discord’s site. You sign in, pass the human checks, and
press the few buttons only a person may.
A session stuck on a menu? Tell your butler “pick the second one”: it reads the screen
and presses the keys, so you do not have to walk back to the Mac.
Several Claude, Codex, Muse and Antigravity accounts in one pool, and always a look at
how much is left.
Several accounts, one pool
Add your Claude, Codex, Muse and Antigravity accounts. A new session starts on the one
with the most room; a resumed one stays on its own account until it is 95% used.
Little bars at the bottom of the sidebar: hover for each Claude, Codex, Muse and
Antigravity account’s 5-hour and 7-day use and when it resets. Codex accounts also
show credits and saved resets. Settings ▸ Usage shows what your sessions would cost at
API prices, by day, session, workspace and model.
Under each Claude session: which account, how much context is used, the branch, the
worktree, the model, and what the session has cost. Codex sessions get a status line
too, made of Codex's own items: context used, the 5-hour and weekly limits left (when
the account has them), branch, Codex version, model and its reasoning level, pull
request number and folder, and for Enterprise accounts an estimated cost. Antigravity
sessions get Koloft's own status line. Turn off Settings ▸ Appearance ▸ Built-in
status line to get your own back.
Every hour, day or week, once, or a set wait after each run, a new session runs what
you wrote; in a git repo, in a worktree of its own. Tell it to close when done and it
tidies up, unless work is left uncommitted or unmerged.
git, gh, playwright-cli and a Nerd Font ship inside, so a fresh Mac needs no Homebrew.
One click on the welcome page installs Claude Code, Codex, Muse Code or Antigravity
CLI.
No Koloft account and no analytics. It reads the tools’ own records; a remote folder’s
are read from that machine so its list works, and nothing goes anywhere else. Every
place it talks to is listed.
Koloft