Threads
One chat with one agent about one piece of work, in its own worktree on one device
A thread is one chat with one agent about one task. It works on a branch of its own, in a git worktree of its own, on the device you picked when you started it. Threads keep their history through crashes and restarts, and threads in Keko Cloud keep working when your Mac sleeps.
Start a thread
⌘T or New thread opens the composer. The strip above it holds what's picked once, before the thread runs:
- Project and branch on the left, in one picker: a folder on this Mac, a GitHub repository, and the branch to start from.
- Device on the right: Keko Cloud, This Mac or one of your servers. Online devices have a green dot; offline ones are greyed out with when they were last seen, and can't be picked. See Devices.
The strip goes away once the thread runs. The row under the message stays: + (files, images, connections and skills), the model, the permission mode (Ask before running or Auto, see Approvals and Auto) and send. The model picker also sets the thinking level, from off to max, as far as the model supports it.
Type @ to mention a file, a folder or a teammate, and / to run a command. Paste or drop images, or use + → Add
images…; models that take images see them.
Send and steer messages
A message to a thread that's working goes out one of three ways:
| Mode | Key | What happens |
|---|---|---|
| Steer | Enter | The agent reads it at its next step, without stopping |
| Interrupt | ⌘Enter | The agent stops what it's doing and reads your message next |
| Queue | ⌥Enter | It waits above the composer until the current work ends |
Queued messages can be sent now, edited, deleted or dragged into another order. ↑ in an empty composer brings back your last message. The keys can be changed in Settings → Shortcuts.
Read a thread
Every action the agent takes is one step: reading, editing, running a command, searching, browsing. A step shows what it's doing while it runs ("Running pnpm test") and what happened after ("pnpm lint exited with code 1"). Steps start closed; a running step opens while it streams and a failed one stays open. A finished turn folds into one line, such as "Worked for 3 min".
When a run fails, an error card stays where it stopped, with what happened, where to fix it and Try again. The raw error is behind Details.
Questions and approvals
When the agent needs a decision it asks with a question card, which takes the composer's place. Answer it, put it off or dismiss it; your answer shows in the chat as your message.
A request to run something risky is an approval card above the composer: the command, what it does, and Don't allow · Allow ⌘↵. Whatever you type in the composer goes back with Don't allow, so you can say what to do instead. An answered card becomes one line, such as "Allowed by Ada, 09:33".
Needs you
A thread that's waiting for you is marked in orange, and its sidebar row shows the question itself. Needs you is a flag, not a status: a thread can be working and need you at once. Notifications go out for this and for failures by default; everything else is opt-in in Settings → Notifications.
The header
The header shows the project, the thread's code, the branch, any previews, the cost and the device. Cost is what the thread's tokens would cost at the provider's API prices, in dollars, whether it runs on a subscription or a key.
The header also shows what the model was given before your first message: system instructions, AGENTS.md and
CLAUDE.md, skills, tools and connections, with an estimate of the tokens each takes. See
Skills and instructions.
Thread codes
Every thread has a short code from its project, such as SHOP-14. It's on the sidebar row and in the header (click to
copy). Search with ⌘K finds threads by code, and typing a whole code jumps straight to it. Majors understand codes
too: "look at SHOP-14".
The work pane
Beside the chat, ⌘⇧B opens the work pane, with tabs for Changes, Terminal, Browser, Desktop (on cloud machines) and Designs (for threads that work in Paper). + opens another. Drag its edge to resize it, move the chat to the other side, or maximise it for review.
Every turn that changed files is a checkpoint. From Changes you can see what a turn did and restore the worktree to an earlier turn.
Review and pull requests
Maximise the work pane on Changes to review. The top bar shows the branch, the lines changed and the checks, with Ask for changes and Create pull request. Tick files as reviewed, and comment on a line to send the comment to the thread.
With the GitHub App installed, GitHub reaches the thread:
- When checks finish, the row says Checks, PR failing or PR ready.
- A failed run sends the thread the failing checks and the end of their logs, once per commit, and wakes it if it's idle.
- A review or comment from someone on GitHub arrives as their message, with a link to GitHub. While the thread is idle it waits for you to send it on, and the thread needs you until you do.
- A merged or closed pull request updates the thread.
Organize threads
- The sidebar lists majors first, then threads: grouped by nothing (yours, then your team's) or by project. Row times are the time since the last activity, and unread threads have a bold title.
- Every row and tab has a context menu: rename, pin, archive, move to a major, copy link.
- Archive puts a thread away and ends its background commands; it can come back. Delete exists only in Settings → Archived, which also cleans up worktrees.
Keyboard shortcuts
| Keys | Action |
|---|---|
| ⌘T | New thread |
| ⌘W | Close tab |
| ⌘1–9 | Jump to a tab |
| ⌘⇧[ and ⌘⇧], Ctrl-Tab | Move between tabs |
| ⌘K | Search everything |
| ⌘B | Show or hide the sidebar |
| ⌘⇧B | Show or hide the work pane |
| ⌘, | Settings |
Every shortcut is also a menu item, and Settings → Shortcuts lists them all.