Sessions and threads

A thread is one conversation with one agent in one folder. The thread keeps its provider, model, working directory, git state, and full transcript together, so switching between projects means switching threads, not reconfiguring anything.

Organizing threads

The sidebar groups threads by repository. Threads running on a git worktree stay grouped under their main repository, so a branch experiment does not scatter your sidebar. You can pin threads you return to often and archive finished ones.

Jump between recent threads with ⌘1 through ⌘9.

Fleet overview

The fleet overview is a full-window board of every active thread: which ones are running a turn, which are waiting on a permission prompt, and which failed their last turn. Use it to supervise several agents working in parallel without clicking through each thread.

Persistence and resume

Threads persist to disk as you work. Saves debounce for about a second and always flush when a turn ends, when you archive or delete, and when the app quits, so closing Cone mid-project is safe. An in-flight turn stops when the app quits. The conversation does not.

Each thread also stores its provider-side session id. When you send the next prompt after a relaunch, Cone resumes the provider’s own conversation state (--resume for Claude, thread/resume for Codex), so the model continues with full context rather than a transcript replay. Switching a thread’s provider clears the stored id, because a Claude session id means nothing to Codex and vice versa.