odoo-manage

Odoo dev environment management

This skill drives the local Odoo development environment through a small CLI, odoo-cli (__ODOO_CLI__). The CLI shares its implementation with the odoo MCP server (same core.ts), including the smart log filtering — so you get the same concise, error-focused output without the MCP server needing to be connected.

This is the Claude Code counterpart to the odoo MCP server (which is kept for Claude Desktop). Prefer this skill in Claude Code; the odoo MCP can be left disabled here to keep the context lean.

Layout you are working with

• Base (fixed): ~/odoo — holds the active odoo.conf and one odoo-<project>.conf per project. (The engine manage_odoo.sh is installed globally, not in the base.)
• Sources live inside the base, _-prefixed (so they stand out from the unprefixed project addon symlinks): _odoo18/ (CE 18), _enterprise18/ (EE 18), _odoo19/ (CE 19), _enterprise19/ (EE 19), plus _venv18/, _venv19/, and _data/.
• 18 vs 19 is per-project, not a separate tree. The active odoo.conf selects it via the ; odoo_src = … / ; python_venv = … markers and its addons_path. Switching project (below) is what changes the running version. Today only verita runs on 19; the rest run on 18.

So "switch project" = swap which odoo-<project>.conf is active. There is no version flag to set — picking the project picks the version.

How to run it

Call the CLI with Bash. It prints a concise result to stdout; diagnostic [Executing]/[Success] lines go to stderr.

node __ODOO_CLI__ <command> [args] [options]

If __ODOO_CLI__ is missing (fresh checkout), build it first: cd __REPO_DIR__ && npm install && npm run build.

Commands

Command	What it does
status	Is Odoo running?
start / stop / restart	Server control
list	List available project configs + the active one
switch <project>	Activate odoo-<project>.conf and restart (changes 18/19 too)
new <name>	Scaffold a new project: odoo-<name>.conf + ./<name> addons symlink + DB (named <name>) + install modules, then switch. --version 18|19, --enterprise, --modules a,b,c, --repo <path>, --no-start
import <file>	Import a backup into the active DB (.zip/.sql/.sql.gz/.dump), then restart. Destructive (drops the DB). --db-only, --neutralize, --no-start
fresh	Drop the active DB+filestore, create a fresh DB initialized with base (+ --init <modules>), then restart. Destructive. --no-start
update <modules>	Update module(s) (comma-separated) and restart — filtered output
install <modules>	Install module(s) — filtered output
frontend <modules>	Update frontend module(s) and restart — filtered output
test [modules]	Run tests (all, or for given modules); --tags <tags> to filter
logs	Tail of odoo.log; --lines <n> (default 50) for the unfiltered log
shell	Prints the command to open an interactive Odoo shell (interactive — not run here)
config-path	Active odoo.conf path
project-config <project>	Path to a project's odoo-<project>.conf
project-dir <project>	A project's custom addons directory
addons-dir	Active Odoo core addons dir (resolves to _odoo18/ or _odoo19/)
enterprise-dir	Active Enterprise addons dir (_enterprise18/ or _enterprise19/)