Use a chat
Start a chat for your project, or for one ticket. A chat becomes a Session when you send its first message. Volli saves the Session, so you can leave and come back without starting a duplicate.
Start a chat
Section titled “Start a chat”Before you start a chat, set a default model in Settings → All projects → Models.
- In Home, select Open a tab (
+), then Chat, to start a Board chat. It works in the project’s main checkout and has no ticket of its own. - In a Ticket view, use Open a tab → Chat to start a ticket chat. It uses that ticket’s selected destination: a New worktree or the project’s Project checkout.
You can also press ⌘T. The composer opens a Chat Draft, which has no history
yet. Write the opening message and select Send to create the Session.
Opening a draft creates no Session and no worktree. Draft text and staged
files survive navigation and relaunch while you keep the draft open. Closing
an unsent draft discards it, including any text and staged files.
Send messages while the agent works
Section titled “Send messages while the agent works”While the agent works on a reply, Queue or Return adds a message for later.
Select Steer on a queued message, or press ⌘Enter in the composer, to send
an instruction into the current turn without interrupting it. Edit message
brings queued text and attachments back to the composer. The remove control
drops a queued message. Use ⇧Enter for a new line.
Select Stop turn to interrupt the current response. This does not undo file edits or commands that already ran, so check the result before sending the next instruction.
Inspect Session activity
Section titled “Inspect Session activity”The Activity Island appears above the composer when the Session has activity to show. Hover over a cluster to inspect it; click to keep its card open while you use its controls.
- Browser: show pages beside the chat, return to a visible tab, or close a page. Browser cards in the transcript also offer Replay. See Browser Tabs.
- Subagents: peek at a Session the agent delegated work to, open it, or stop it. These children share the parent’s working directory and have no row in the Session list.
- Plan: read the agent’s checklist and its completed-item count.
- Shells: inspect output from a dev server or another long-running command. These stop when the Session’s connection ends; they do not survive a relaunch.
Read tool activity
Section titled “Read tool activity”Expand an activity row to inspect the tool’s arguments, output, and outcome. A failed tool call stays available in the transcript; it does not necessarily mean the whole turn failed. Web search rows link to the sources the agent found. Browser cards offer replay of the actions it recorded.
Long conversations load a window of messages. Select Show earlier to read older history without starting another Session.
Background shells
Section titled “Background shells”An agent can run a dev server, watch build, or another long command beside its turn. Open Shells in the Activity Island to inspect its output or stop it. Volli tells the agent when a background shell exits, so it does not need to keep checking for completion.
To free a turn held by a running command, choose Move to background on its
transcript row or press ⌃⇧B while the chat has focus. The command keeps
running and appears under Shells. The action is available only when there
is a free background-shell slot. Shells stop when the Session’s connection
ends and do not survive restarting Volli.
Answer questions and credential requests
Section titled “Answer questions and credential requests”A question card can contain several related questions. Choose an offered answer or type your own, then use the card’s controls to send the answers. Decline to answer refuses the questions; stopping the turn is a separate action.
Credentials have their own Credential requested field. Do not put a secret in a normal chat reply. See Supply a Session credential.
Return to a Session
Section titled “Return to a Session”In Home, select an existing chat under Board sessions in the rail. For a ticket chat, open the Ticket view and select the Session under Now → Sessions. Its transcript stays with that Session when you switch tabs, navigate away, or close its live connection. Sending another message to a disconnected chat reconnects that Session instead of creating a second conversation.
Closing a chat tab does not delete the Session. Starting a new chat creates a different Session. To keep a conversation beside a file, terminal, or Browser Tab, use split view.
Read activity and unread indicators
Section titled “Read activity and unread indicators”A chat Session’s provider logo identifies its model provider. Its activity indicator shows Working, Waiting for you, Idle, or Interrupted. An interrupted Session has a turn that stopped unexpectedly; open it to read the reason and available recovery action.
The unread dot is separate from activity. It means a turn ended while you were not viewing that Session, or you marked it unread yourself. Opening the Session, viewing its conversation, or successfully replying marks it read. New turns and questions can move a Session up the list; streamed output does not continually reorder it.
Peek at a Session without opening it
Section titled “Peek at a Session without opening it”Hover over a Session in the sidebar’s Active or Previous list, or under a ticket’s Now → Sessions. After a moment, a card shows the Session’s state, what it did most recently, and any question it is waiting on. Hover over a ticket’s folder instead to see that ticket’s Sessions.
- Select Answer on a waiting question, or Send to message a Session,
to reply from the card.
⌘.does the same for the card on screen. The reply goes to that Session; you stay where you were. - Select Open session to open the Session’s tab, or View conversation to read its conversation in an overlay.
- Press
Escto step back: out of the reply field, then the card.
From the keyboard, focus a row and press Space to peek, and Space again to
reply. ↑ and ↓ (or K and J) move between rows. A peek does not mark a
Session as read; press U on a focused row to toggle its unread dot.
Choose a terminal companion
Section titled “Choose a terminal companion”Choose Open a tab → Terminal when you need a shell or want to run a terminal app (a TUI) yourself. A terminal is a separate manual workflow, not a fallback when a chat cannot start. See Terminal companions for what it can do and what it keeps.
Start work from an Automation
Section titled “Start work from an Automation”An Automation Run starts a new Session whose first message is the Automation’s saved Instructions. A ticket-triggered Run uses the ticket; a scheduled Run starts a Board Session in the project’s main checkout. See Automations for how to run one and inspect Run history.
If a chat stops or loses provider access, see Recover a Session. See Chats and worktrees for the checkout each chat uses.