KEY=secret:<name> in any service or environment. Values are write-only: agents and the API can only see the name, never the value.secret:<name> as a value to reference a team secret (Credentials tab).__ODUFLOW_DIAGNOSTICS__
Loading...
Pull the latest image for and re-create its container. Volumes are kept.
secret:<name> as a value to reference a team secret (Credentials tab).One KEY=VALUE per line. Clear the field to remove all variables; leave it untouched to keep them.
Creates a persistent PostgreSQL database with a dedicated non-superuser role. It is not deleted with a service container.
These values grant access to the database. Store and pass them as secrets.
secret:<name> as a value to reference a team secret (Credentials tab).secret:<name> values are resolved from the team secrets at restore time.Reuse this environment for another branch instead of creating a new one. The database, filestore, hostname and URL are kept — only the code changes. The branch must already exist on origin; Oduflow then installs, upgrades or restarts as the difference between the two branches requires.
Currently on .
Recreate the container for . The database and filestore are kept.
secret:<name> as a value to reference a team secret (Credentials tab).One KEY=VALUE per line, injected into the Odoo container on top of the database connection variables. Clear the field to remove all custom variables; leave it untouched to keep them.
Runs odoo -i against this environment's database and restarts the container when it succeeds. Modules already installed are left as they are — use Upgrade modules for those.
Runs odoo -u for the modules you pick and restarts the container when it succeeds. Only installed modules are listed; filtering never clears a selection.
The dashboard link is scoped to this environment: its card, logs, consoles, module install/upgrade, Connect As and Agent Chat. Other team environments and team-wide pages are unavailable, as is Agent CLI. Important: Agent Chat runs in the team's shared coder container, so the agent may read other team checkouts and Git credentials available there. Share only with someone trusted for that access. The link carries its own key, so treat it as a credential.
This environment is not shared yet.
Scoped MCP endpoint for this environment only. Use the Secret Key as a Bearer token — this endpoint is Bearer-only and does not use the OAuth flow. It exposes the in-environment tools (sync, install/upgrade, tests, shell, SQL, logs); it cannot create, delete or stop environments.
This environment was created before per-environment tokens existed. Recreate it to issue a Secret Key.
KEY=secret:<name>.