Chats and worktrees
Volli lets you run independent tasks in parallel. Start a project chat to shape a broad idea into tasks, then start a ticket chat for each task that needs code changes. In Volli, a task is a ticket.
Project chats and ticket chats
Section titled “Project chats and ticket chats”| Chat | Use it for | Working directory |
|---|---|---|
| Ticket chat | One task and its brief | That ticket’s worktree |
| Project chat | Broad project work before you have a task | The project’s main checkout |
Choose a default model in Settings → Model Access before you start either kind. Volli records the model for the chat and does not silently switch to a different model or account.
Ticket worktrees
Section titled “Ticket worktrees”When a ticket needs isolated repository work, Volli prepares a ticket worktree
on a branch named volli/<DISPLAY-ID>-<slug>, for example
volli/VC-12-mcp-server. Worktrees live under ~/.volli/worktrees/.
The project folder you add to Volli remains the main checkout. A ticket’s files and changes come from its worktree, so parallel tasks can work on separate branches.
You can inspect a ticket’s branch from a terminal companion:
volli worktree status VC-12volli worktree diff VC-12worktree diff compares the ticket branch with its base branch. Add
--working-tree to see uncommitted changes.
Chat history
Section titled “Chat history”A chat is not tied to an open tab or terminal pane. Its history remains available when you navigate away, when its live connection ends, or when you reopen the app. Open the ticket workspace to return to a ticket chat and inspect its recorded work.
A chat can reconnect without creating a second conversation history.
Terminal companions
Section titled “Terminal companions”Open a terminal companion when you want a shell or a specific TUI workflow. It can run in a project or ticket worktree, but it does not replace Volli’s built-in chat.
The volli CLI is available to supported terminal companions over a local Unix
socket. It can inspect ticket context and report work to the app. See the
CLI reference for its commands.
Change sets and retained worktrees
Section titled “Change sets and retained worktrees”A ticket’s change set includes committed and uncommitted changes relative to its base branch. Volli reads it from git rather than storing a copy.
Archiving a ticket retains its worktree. You can remove a worktree from the ticket context menu, or use Archive & clean when Volli offers it. A clean worktree can also be reclaimed after the ticket has spent the configured retention period in Done with no open pull request and no work running there. The ticket, branch, commits, and pull-request URL remain.
To remove one yourself after its branch is landed, run:
git worktree remove ~/.volli/worktrees/<project-dirname>-<short-id>/<TICKET-ID>-<slug>