Apps
An app is a bundle of related tools that the agent can use. Apps are turned on per project — so your GitHub project might have the GitHub app on, while your CRM project has HubSpot on. You control what the agent has access to, project by project.
Built-in apps
Notes is no longer an app you enable — it's native and always-on in every project (like Tasks), with its own sidebar and full text + meaning search. There's nothing to enable.
| App | What it does |
|---|---|
| Contacts | A lightweight CRM shared across your whole org — people, orgs, tags. Enable it in any project to give that project's agent access to the org-wide contact book. |
| GitHub | Repos, issues, pull requests, files in a repo. |
| HubSpot | Full CRM access via your HubSpot account. |
| Freshdesk | Ticket management. |
| MongoDB | Read and write operations on your MongoDB clusters. |
| Spreadsheet | Read and write Google Sheets. |
Apps
On top of the built-ins, you can build your own — they're called apps, and the CLI makes it straightforward. The Google suite (Gmail, Calendar, Contacts, Drive) is actually an app in the Avi repo, not a built-in — you can install it the same way you'd install any other app.
Enabling an app
In a project's settings, toggle the apps you want on. Enabling an app:
- Makes its tools available to the agent.
- May open a sidebar panel in the project (e.g. an app can add its own panel).
- May require you to connect an account (e.g. linking GitHub or HubSpot via OAuth).
Tool-level control
Even when an app is enabled, you can disable individual tools inside it — useful if you want the agent to read from a service but not write or delete. Look for the tool permissions panel inside the project's settings.
What apps the agent can actually use
For a tool to be callable, two things must be true:
- The app it belongs to is enabled in this project.
- The specific tool is permitted in this project.
Both gates matter. Turning off a single tool is a quick way to keep the rest of an app's capabilities while blocking one risky one.