Skip to content

What's new in 0.2

0.2.0, September 30, 2026.

These notes describe the 0.2 release. For current controls and the latest canary changes, see What’s new in 0.3 and the linked guides.

0.2 adds Automations, lets agents drive Browser Tabs you can watch and take over, and shows what each chat is holding in the Activity Island. It also adds split view, MCP servers, model tiers for delegated work, provider usage limits, and a new terminal engine.

Update from Settings → Updates, or download the build from volli.app/download.

An Automation is a saved, named way to start work. It keeps its Instructions, Trigger, and Runtime together, so you can start the same setup by hand, when a ticket enters a board column, or on a schedule.

  • Instructions are the first message of the fresh Session a Run opens.
  • Trigger is what starts it besides you. The default, Only when I run it, means nothing else does; the other choices are Ticket enters and On a schedule.
  • Runtime is the model policy: a project default, a named default tier, or an exact model and reasoning level.

Create and edit Automations on the Automations page. Run one by hand from that page, a ticket’s Automations section, a board card’s context menu, or the command palette. No Automation starts on its own until you turn on Automatic triggers for this Mac and, for a column Trigger, arm the column. Then only a Deliberate move into that column starts a Run, after a short delay you can Cancel. Schedules use presets, need Volli to be open, and record a missed due time as Skipped.

Each Run opens a fresh Session and records the model and reasoning it ended up using. See Automations for the full behavior.

A Browser Tab is a web page inside Home or a Ticket view. Open one yourself from the Browser item in the menu beside Chat, or let a chat open one to check a page it is building.

  • A tab a Session opens stays off screen at first. It shows as a card in that chat and in the Activity Island. Choose Open beside chat to show it in a tab group beside its owner, without a miniature preview above the composer.
  • While a Session drives a tab, the Session cursor shows where its input goes, in that Session’s colour and with its name.
  • Only one party drives a tab at a time. Use Take over, Ask to leave, or Hand back to change who has it. Your own input into the page always goes through.
  • A Session sees your tabs and its own, and cannot see another Session’s tabs.

Volli treats whatever a page says as untrusted content, and tabs run apart from the app itself. See Use Browser Tabs to open a page and change who controls it.

The Activity Island is a pill above a chat’s composer that shows what that Session is holding besides the conversation:

  • Browser Tabs it opened.
  • Subagents it started. A chat can delegate work to child Sessions. Hover a subagent to see its progress, peek at it, open it as a tab, or stop it. Subagents do not appear as separate rows in Session lists.
  • Plan: the checklist the agent keeps for multi-step work, shown as done over total.
  • Background shells: long-running commands such as a dev server or a watch build, which keep running while the turn goes on. Open one to read its output. They stop when the Session’s connection ends and do not survive a relaunch.

The island appears only when there is something to show. The ticket’s Now rail keeps what is true of the whole ticket. See Use a chat for Session activity and returning to a conversation.

Home and the Ticket view can each be split into Panes. Drag a tab, Session, or file to the right or bottom edge of a pane to split there, or use ⌘\ to split right and ⇧⌘\ to split down. Each surface keeps its own split, and tabs do not move between the two. See Arrange a split view for steps and shortcuts.

Configure → MCP Servers adds Model Context Protocol servers to a project, over stdio or streamable HTTP, and picks which of their tools chats may use. MCP tools run through Volli like any other tool and appear in Session history. A change applies to new Sessions; a running Session keeps the tools it started with. See MCP servers for discovery, tool selection, and transport limits.

Settings → Models adds three default tiers by kind of work: Fast for quick, low-cost tasks, Deep for complex reasoning, planning, and review, and Visual for images, screenshots, and pages. Leave a tier unset and it uses the Ticket Sessions default. Model pickers list the defaults you set, and an agent that starts another Session or delegates to a subagent can ask for a tier by name. An Automation’s Runtime can name a tier too.

A subagent that names neither a model nor a tier runs on its parent’s model. See Models and usage for how defaults resolve and which models you can use.

The usage-limits icon beside the ⌘K search opens a popover that shows how much of each subscription window you have used and when it resets. It covers these provider subscriptions: Anthropic (Claude Pro/Max), OpenAI Codex, GitHub Copilot, Kimi Code, OpenCode Go, xAI, and Z.ai. Readings are live and are not saved in Session history.

  • Peek at a Session from the sidebar. Rest the pointer on a Session in the sidebar or a ticket’s Now → Sessions to see its state, its latest work, and any question it is waiting on. Answer or message it from the card without leaving what you are doing. See Peek at a Session.
  • Images render inline in chats, ticket bodies, comments, and queued messages. Remote image URLs are not loaded; a refused image shows its reason instead of a blank space.
  • The terminal uses xterm.js. Its appearance still comes from your Ghostty configuration. VoiceOver can read the output, and Control+Shift+M lets Tab move focus out of a terminal. See Keyboard shortcuts.
  • Recovery after a crash. A Session whose turn was running when Volli quit unexpectedly can be resumed, and a message you send to a disconnected Session reconnects it instead of waiting in the queue. See Recover a Session.

Board columns draw only the cards near the visible area, long chats load earlier messages when you select Show earlier, and opening a ticket does less work. Large boards, long chats, and many Sessions open at once stay responsive.