Install the runtime daemon on every machine that should execute Odoo agent work.
- Create a runtime record in Odoo.
- Generate and copy its API key.
- Clone this repository on the execution machine.
- Run the installer.
- Choose manual mode first.
- Confirm heartbeat in Odoo.
- Switch to service/daemon mode only after the manual run works.
git clone https://github.com/nicolasramos/odoo-agent-runtime.git
cd odoo-agent-runtime
bash install.shManual run:
python3 daemon.pySystemd mode is available from the installer when selected.
git clone https://github.com/nicolasramos/odoo-agent-runtime.git
cd odoo-agent-runtime
bash install.shLaunchd mode is available from the installer when selected.
git clone https://github.com/nicolasramos/odoo-agent-runtime.git
cd odoo-agent-runtime
.\install.ps1Scheduled Task mode is available from the installer when selected.
| Value | Example |
|---|---|
| Odoo URL | https://odoo.example.com |
| Runtime API key | odoo_rt_xxx |
| Runtime name | agent-worker-01 |
| Poll interval | 10 |
ODOO_DATABASE is optional for a single-database Odoo deployment. Provide it when the Odoo URL serves multiple databases, or when your runtime must always target one specific database. On Linux and macOS, enter it at the install.sh prompt; on Windows, enter it at the install.ps1 prompt. Each installer writes an empty value when it is not needed.
Keep the runtime API key separate from the Odoo URL. Enter it only at the Runtime API key prompt; never append it to a URL, query string, bookmark, or command history.
The installer does not silently overwrite .env. If .env exists, it asks before replacing it. If you decline, it writes .env.new and does not install/start a background service with stale settings.
After starting the daemon:
- Open Odoo.
- Go to AI Agents → Runtimes.
- Confirm
Last Seenupdates. - Send a simple task to an agent assigned to that runtime.
- Confirm logs and final status.