# AI assistant

> The assistant in the cabinet answers questions, explains failed builds and proposes actions as buttons you press. Only a deploy you ask for starts at once.

Source: https://livops.dev/en/docs/assistant

The assistant works in two places:

1. **Next to a failed build** — a single button. It reads the log and tells you what happened and how to fix it. The answer is saved: clicking again is free and returns the same answer.
2. **A chat in the bottom corner of every screen** — questions about how to deploy, connect a domain, or what your bill is made of.

## Actions — on a button, with one exception

The assistant can't call anything on its own: the model is given no tools. It proposes a **card** — a button on screen. When you click it, a regular cabinet action runs: your session and permissions are checked again, exactly as if you had found and clicked that button yourself.

**Deploy is the exception.** When you ask it to deploy a repository you named or a folder you attached to the chat, the card doesn't wait for a click: as soon as the answer arrives, the cabinet creates the project with your session and starts its first build. Auto mode makes no difference to this. A static site is free. A bot or an app that runs a server is paid: when its build finishes and it starts, a month's price is taken from your credits if they cover it; an account that has never paid may get its one-time [demonstration](https://livops.dev/en/docs/pricing) instead; otherwise the app waits for a payment. The button on this card only appears, to try again, after a failure.

The actions the assistant can propose:

- deploy a repository or an attached folder as a new project (starts on its own, see above), retry or cancel a build;
- restart, stop, or roll back to a previous version;
- fix the build and start commands, the project folder or the build output folder;
- connect a domain or recheck DNS;
- connect a GitHub repository;
- add a database or move it to a larger size — the card shows the new monthly price (team owner only);
- create again a database that failed to be created or got stuck creating (team owner only);
- add a storage bucket or change a service's memory;
- set one variable or several — only to values you wrote in that same message;
- add a service or environment, set a cron schedule, create from a template or fill in a template field (a price, a phone number), import a repository into a project;
- run a public Docker image (docker.io, ghcr.io, quay.io) as a new service, either web or worker; the image and port are taken exactly as you wrote them in that message;
- promote staging to production;
- merge stacks, connect services to each other, or write a stack's addresses again;
- rename a project or a stack, change a project's Livops address, send a static site's paths to another service;
- invite someone to a project — only the email you wrote in that message; create an API token — shown once, on the card only;
- turn waiting for CI and pull request previews on or off.

## What it doesn't do

- It **never deletes anything** and never restores from a backup.
- It **doesn't see variable values** — only their names.
- It doesn't write a database address or password into a static site.

## Auto mode

You can turn on auto mode under the team's **Settings → Assistant** (`/<team>/settings/assistant`); it is off by default. With it on, the cabinet clicks the button for you only on small, reversible actions: retrying or cancelling a build, restarting, adding a domain, rechecking DNS, and fixing the project folder or build output folder. Everything else — rollback, stop, changing commands, adding a database or storage bucket, growing a database, running a Docker image, variables, promote and more — **still waits for your click**. Deploy is not affected by this setting: it starts on its own either way (see above).

## Privacy

When the assistant is enabled and you ask it something, your question, your project names and the failed build's log are sent to the AI provider (Anthropic). If you don't want that, turn it off under **Settings → Assistant** — after that the server sends nothing.

## Limits

- Chat: **20** questions a month on Free, **100** on Hobby, **300** on Pro, **1,000** on Team. Questions are counted per team per month; an account that has paid without a plan gets Hobby's. Past that, 5 questions cost 1 credit; out of credits, the assistant asks you to top up.
- Failed build explanations: up to 20 per day per account.
