Skip to main content
A thread is a durable conversation with one Capy agent, stored on Capy’s servers: close the laptop mid-run and the agent keeps working, and the thread wakes on its own when CI finishes, a review lands, or a PR merges. Use one thread per piece of work, and message it the way you’d message a colleague; it holds the full history of the conversation, the machines, the tasks, and the PRs that came out of it.

​
Sending messages

Every message you send carries a delivery mode that decides how it reaches a busy agent: Enter sends as interrupt by default, Cmd/Ctrl+Enter sends as queue, and Option/Alt+Enter sends as steer. All three gestures are configurable in Settings → General under Input, and each gesture has one stable meaning. When the thread is at rest there’s nothing to interrupt, queue behind, or steer, so every send just delivers immediately.

​
Thread statuses

A thread’s status is derived from what the agent and its tasks are doing, in this precedence: active beats error, error beats needs-attention, and so on down to idle. The sidebar and threads page fold statuses into five buckets: Skim the needs-attention and ready-for-review buckets first; those are the threads waiting on you. Active and waiting threads don’t need you yet.

​
Marking status by hand

You can move a resting thread between buckets yourself: the Status submenu in any thread’s context menu offers Ready for review, Needs attention, and Idle. Marks are the human’s word until someone speaks again: your next message or the agent’s next turn-ending reply overwrites them, and you can’t mark a thread that’s actively working. A thread sitting in ready-for-review settles to idle on its own when a merge lands and no PR anywhere in its task tree remains open.

​
Archive is dormant

Archiving removes a thread from your lists and puts it fully to sleep: no CI result, task completion, or reminder wakes it. Events that arrive meanwhile still land as pending context (nothing is lost), but nothing runs. Archived threads can still be revived with a human message. Sending to an archived thread unarchives it and wakes the agent with everything that accumulated while it slept. Archive is for threads you’re done looking at. To mark work finished without hiding it, mark the thread idle instead.

​
Todos are the agent’s visible plan

For multi-step work the agent keeps a todo list: its working plan, updated as it goes. Items move through pending, in_progress, completed, cancelled, and deferred, with at most one item in progress at a time.

​
Voice input

The microphone button in the composer dictates straight into the message, live, at your cursor; you can keep typing around it while you talk. Accept commits the transcript, discard throws it away, and a recording auto-accepts at the 10-minute cap so nothing you said is lost. Undo reverts the dictation as one edit.

​
Attachments

Attach images and files to any message from the composer; they land on the agent’s machine, where it reads them with its ordinary tools.

​
The command menu

Cmd+K opens the command menu from anywhere:
  • Typing searches your threads full-text: titles, thread codes, and message content.
  • It also finds pull requests, automations, and settings pages as you type.
  • At rest it lists your most relevant threads in the same priority order as the sidebar, plus navigation and theme actions.
  • Tab hands off to a full new-thread composer seeded with whatever you typed, so a thought becomes a thread without leaving the keyboard.
Every keybinding here and in the composer is configurable at Settings → Shortcuts.

​
Folders

Folders are flat, org-level groupings of threads. A folder is either private (only you see and edit it) or shared (every member of your organization sees and edits it), and a thread can sit in any number of folders at once. Folder membership changes nothing about the thread itself, and the All threads, status, and search views stay complete: filing a thread adds a view, it never removes the thread from ordinary results. Pinned is a reserved private folder that always renders first. Pinning a thread is just membership in that folder, so pins reorder like any other folder and unpinning is removal. Pinning an already-pinned thread again moves it to the front. Folder and tag memberships survive archiving, so an unarchived thread comes back exactly where you filed it.

​
Tags

Tags are organization-wide labels: one shared vocabulary across every project, each tag with a name and color. A thread carries up to 20 tags. Tags filter and decorate thread lists; they don’t place threads anywhere, so use folders for “where does this live” and tags for “what kind of thing is this”. Search is full-text over titles, thread codes, task titles, and message content, both what you wrote and what the agent replied. That matters because most thread titles are auto-generated: searching for the error string you pasted three weeks ago finds the thread even if its title never mentioned it. Search from Cmd+K anywhere, or from the search box on the threads page.

​
Titles

Every thread titles itself from your first message: a compact phrase of at most 50 characters, generated while the agent starts working. There are two ways you can manually change a thread’s title, both in the thread’s context menu:
  • Rename sets your own title. Explicit titles stick; regeneration and auto-titling never overwrite a name you typed.
  • Regenerate asks for a fresh title from the conversation so far, and clears the explicit-title mark so the thread is auto-titled again.