Agent capability changes
Use the installed build’s help to check its capabilities. A newer app can have commands and tools that an older Session has not received.
Inspect the installed build
Section titled “Inspect the installed build”volli help changesvolli helpvolli help changes prints the CLI bundle’s source revision and capability
record. When the app is reachable, it also reports the running app version.
The CLI bundle and app version are separate facts.
Inside a Session, volli help also lists its recorded tools. A tool described
in the latest docs may be unavailable to that Session. Use the tools it holds,
or start a new Session after configuring the capability you need.
Existing Sessions and new tools
Section titled “Existing Sessions and new tools”A Session keeps its original tool record. Reopening it does not replace that record with the current defaults.
Volli can add eligible capabilities without removing or renaming the tools already recorded. Additions that change what the model sees wait for a new context-cache boundary, such as compaction or a model switch. Tools available only through Code Mode can be announced without changing that cached prefix. An app update or a settings change does not guarantee an immediate addition.
See Agent operating model for Session roles and Code Mode for tool routing.
Recent capabilities
Section titled “Recent capabilities”| Capability | Where to look |
|---|---|
| Background commands and exit notices | Use a chat |
| Browser actions and replay | Browser Tabs |
| Typed classification with an optional decision model | Models and usage |
| Secure credential requests | Session credentials |
| Tool calls combined in JavaScript | Code Mode |
Smaller ticket listings with --no-body |
CLI commands |
What’s new in 0.3 covers the desktop changes.