> ## Documentation Index
> Fetch the complete documentation index at: https://docs.doploy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What agents can do

> Every tool an AI agent gets when it connects to doploy, and the loop they add up to

# What agents can do

After connecting, an agent sees two groups of tools. Which ones it may *call* depends on the
permissions you granted and on your role in each project.

## Watch and read

| Tool                        | What it returns                                                                 |
| --------------------------- | ------------------------------------------------------------------------------- |
| `platform_list_projects`    | Your projects and their Odoo versions                                           |
| `platform_get_project`      | A project with its live deployments and their health                            |
| `platform_list_branches`    | Branches of a project                                                           |
| `platform_list_builds`      | Recent builds, filterable by branch or type                                     |
| `platform_get_build`        | One build: status, commit, versions, error summary                              |
| `platform_get_test_results` | Test failures and errors with tracebacks                                        |
| `platform_get_build_logs`   | Tail of the build log, the test run output, or the running Odoo container's log |
| `platform_get_operation`    | Progress of a queued module update                                              |
| `platform_get_backup`       | Status of a backup                                                              |
| `doploy_list_connections`   | Odoo connections you can query                                                  |

## Deploy

Available with **Read + deploy**, on projects where an admin enabled agent write access.

| Tool                         | What it does                                                                                     |
| ---------------------------- | ------------------------------------------------------------------------------------------------ |
| `platform_create_dev_branch` | Forks a branch on GitHub and queues its dev build                                                |
| `platform_rebuild_build`     | Queues a rebuild of a deployment                                                                 |
| `platform_restart_odoo`      | Restarts the Odoo service                                                                        |
| `platform_update_modules`    | Runs `odoo-bin -u` on the modules doploy detected as changed, optionally rebuilding theme assets |
| `platform_create_backup`     | Takes a database and filestore backup                                                            |

Any of these aimed at a production deployment returns `confirm_required` first. The agent has to call
again with `confirm: true`, which in practice means it asks you.

Nothing destructive is exposed. Agents cannot delete projects or deployments, restore backups, or
change domains.

## Odoo data

The same `odoo_*`, `doploy_sql_*` and `doploy_schema_*` tools available in
doploy AI chat are available to connected agents. Each call names a `connection_id`
from `doploy_list_connections`. What the agent may do on that connection follows your own Odoo
identity and tier there: read, write or execute, and whether direct SQL is allowed.

## The loop

The tools are designed around one workflow:

1. Agent pushes code to a branch, or creates one with `platform_create_dev_branch`.
2. doploy builds it and runs the tests.
3. Agent reads `platform_get_test_results` and `platform_get_build_logs`, fixes the code, pushes again.
4. Build goes green. The agent opens the pull request.
5. After merge, the agent runs `platform_update_modules` on staging and checks the Odoo log.

Every write is recorded in the project's audit log with the app that made it.