Skip to content

Concepts

Use this page when a Volli label is unfamiliar. The table translates the common workflow into the terms you see in the app.

What you want to do Volli term
Plan and track a unit of work Ticket
State the task’s outcome and constraints Ticket Body
Run an agent conversation Chat
Keep a lasting record of a chat or terminal Session
Give a task its own Git checkout Ticket worktree
Inspect a task’s branch changes Change Set

These terms have the same meaning across the app and its documentation.

Project. A tracked codebase folder. Removing it from Volli does not remove the folder from disk.

Home. The project’s tabbed workspace. Opening a project lands here. Its first tab is the Board, which you cannot close. Board chats and Project Files open as tabs beside it.

Ticket. A task on the board. It holds a title, status, and Ticket Body. A ticket can provide the context for a ticket chat and its worktree.

Ticket Body. The task’s Markdown brief and starting instruction. It is part of the ticket record, not a repository file.

Ticket view. Where you work on one ticket. Its main tabs hold the Ticket Body, chats, files, and diffs. Its rail groups repository state, chats and offered Automations under Now, with separate Diffs, Files, and Search views. Edit status, priority, and labels beside the title in the Ticket Body tab.

Display ID. The project-local handle shown to people, such as VLT-12.

Chat Draft. A composer you have opened without sending its first message. It has no Session history or running agent yet. Sending the first message creates the Session.

Session. The saved record of a chat or terminal. It stays available after its connection, turn, or run ends.

Chat. Volli’s built-in agent conversation. It uses the model you choose and shows the agent’s messages, tool steps, and questions in the app.

Ticket chat. A chat for one task. It carries the ticket’s Ticket Body and the context resolved for it, and works in the ticket’s worktree.

Board chat. A chat for broad project work, started from Home. It works in your main checkout and can create and edit tickets. Use it to turn a rough idea into tasks.

Model Access. The accounts, subscriptions, credentials, and models that Volli can use. Manage it under Settings → All projects → Models. Choose a default model there before you start a chat. Credentials never enter chat history.

Terminal companion. A shell you open yourself in a project or worktree. Use it to run your own commands, or start an external terminal UI, such as Claude Code, Codex, or OpenCode, from that shell. Open it from Open a tab → Terminal. Volli never opens one as a fallback when a chat fails.

Ticket worktree. An isolated Git checkout for a task. Volli creates its branch as volli/<DISPLAY-ID>-<slug> and stores the checkout under ~/.volli/worktrees/. A worktree holds only checkout state. After cleanup, Volli can recreate it from the branch it keeps.

Main checkout. The repository folder you added as a project.

Change Set. Committed and uncommitted work in a ticket worktree, measured against its base branch.

Ticket Files. The files in a ticket’s worktree.

Project Files. The files in the main checkout.

A Session keeps its conversation after a turn ends or you close its tab, and reopening it returns to that history. Recovery reconnects the same Session.

See Use a chat for starting and recovering a Session. If you write instructions for agents, the agent operating model explains roles, tools, and what each command does.

Automation. A saved, named way to start work. It contains a Trigger, Instructions, and a Runtime. Every Automation can be run by hand; its Trigger describes what else may start it.

Trigger. What starts an Automation besides running it yourself. A new Automation uses None, which means nothing else starts it; the other choices are Columns and Schedule. A column Trigger makes an Automation available in selected columns; a schedule uses one of Volli’s hourly, daily, weekdays, or weekly presets.

Instructions. The message an Automation sends as the first message of the fresh Session a Run opens. It uses the chat composer’s / templates and Skills and @ file references.

Runtime. The model policy for a Run. It can inherit the project default, name one of the configured default tiers, or pin an exact model and reasoning level. A Run records the model and reasoning it ended up using.

Run. One start of a saved Automation and the record of the fresh Session it opened. Run history stays even if you delete the Automation later.

See Automations for how Runs start. The column-trigger guide explains Automatic triggers, arming a column, and choosing a Run while you drag a ticket.