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 durable 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.
Planning
Section titled “Planning”Project. A tracked codebase folder. Removing it from Volli does not remove the folder from disk.
Home. The project’s tabbed workspace. A project opens here. Its first tab is the Board and cannot be closed. Project 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 workspace. The working surface for one task. Its main tabs hold the Ticket Body, chats, files, and diffs. Its rail groups repository state, properties, and chats under Now, with separate Diffs and Files views.
Display ID. The project-local handle shown to people, such as VC-12.
Session. The durable record for a chat or terminal. It remains available after its live connection, turn, or run ends.
Chat. Volli’s built-in agent conversation. It uses the model you choose in Model Access 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 Body and resolved context, and works in the ticket’s worktree.
Project 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. Choose a default model here before you start a chat. Credentials do not enter chat history.
Terminal companion. A manual terminal or external TUI you open for work in a project or worktree: Claude Code, Codex, OpenCode, or your own. Open it from the caret beside Chat. Volli never opens one as a fallback when a chat fails.
Git work
Section titled “Git work”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 is disposable checkout state. Volli can
recreate it from the retained branch after cleanup.
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.
History and control
Section titled “History and control”Session Event. An immutable fact in a Session’s local history, such as a message, command outcome, interaction, attachment outcome, or recovery signal.
Command. Explicit user intent recorded before the runtime is asked to act.
Receipt. The recorded outcome of a Command: accepted, rejected, completed, or unreconciled.
Attention. A reconstructed view that shows when a Session needs recovery or input. It is derived from Session history rather than a source of truth.
In development
Section titled “In development”Automations are in development. They will be saved board triggers that open Sessions with instructions, a runtime, and recorded outcomes. They are not available to configure yet.