The Ticket view
A ticket is a task in Volli. Open one to read its Ticket Body, return to its chats, inspect files and diffs, and edit its properties. The main tab strip keeps the documents and chats you open. The rail beside it has four pages: Now, Diffs, Files, and Search.
Edit status, priority, and labels beside the title in the Ticket Body tab. Changing status updates the board. Starting a chat or an Automation Run is a separate action.
Now has two sections:
- Sessions: the ticket’s chats and terminal Sessions. Ended Sessions are folded under the section heading. Open one to return to its history.
- Automations: the saved Automations this ticket can run.
A row pinned at the bottom of Now shows the ticket’s cost. The worktree row is pinned under every page: it shows the branch and opens to the base branch, worktree, changes, and pull-request state.
A ticket chat carries the task’s context and uses its selected checkout: New worktree or Project checkout. Reconnecting it does not create a second chat history. Its Browser Tabs, subagents, plan, and background shells appear in the Activity Island above the composer.
Configure Models first. In the tab strip or Sessions
heading, select Open a tab (+), then Chat, to open a draft. Sending
the first message starts the Session. The same menu offers Terminal for a
terminal companion and Browser for a
Browser Tab.
Run an Automation on this ticket
Section titled “Run an Automation on this ticket”The Automations section lists the Automations offered to this ticket. The one armed for the ticket’s current column comes first and is marked.
Select a row, or right-click it, to see its saved Instructions. Choose the model for this Run under Run on, then select Run. Selecting a row never starts a Run by itself. You can run an Automation by hand even when Automatic triggers is off for it.
A Run opens a fresh Session. It appears in Sessions with a mark showing that a Run started it. The Automations section does not list Runs.
Select Open Automations in the section heading to create or edit Automation records; authoring lives only on that page. For one-off work that you don’t want to save, start a chat instead.
Tabs and panes
Section titled “Tabs and panes”Keep several documents and conversations open in the tab strip. To rename a chat or terminal tab, double-click its title or choose Rename from its context menu. Closing a chat tab keeps the Session’s history; closing an unsent Chat Draft discards the draft.
Use split view to arrange tabs side by side or above one another. Each pane has its own stack of tabs. The top strip shows the group as one chip with stacked icons, including provider logos for recognized chat providers. Hover over the chip or open its menu to find a grouped tab. Select an ordinary tab to show it on its own, then select the group chip to return to its arrangement.
Files and references
Section titled “Files and references”The Files rail shows file references from the Ticket Body, attached files,
and the ticket worktree’s directory tree. Use @ in the Ticket Body to add a
file reference. Selecting a file opens a preview tab. Double-click its tab,
or choose Keep Open from its context menu, to pin it so another preview
does not replace it.
Ticket files come from the worktree. The project-level Files navigator in Home reads from the main checkout, so the same path can hold different content in each place, and editing one does not edit the other.
The Diffs rail compares the ticket worktree with its base branch. Open a file to inspect its diff. The Change Set includes committed and uncommitted work, so it reflects the branch as it is on disk. See Review and publish changes for testing, commits, and pull requests.
Search
Section titled “Search”The Search rail searches files in the ticket’s worktree. For tickets and
Sessions across projects, use the command palette, ⌘K.