Claudoo

Chat with your Odoo — safely.

An in-Odoo AI assistant powered by the Claude Code CLI. It answers questions, queries your data, and builds reports — running as the logged-in user, never as superuser, with a full audit trail.

Quick start · Security model · Configuration · Commercial support · Roadmap

Most "AI for Odoo" add-ons either ship your data to a third-party prompt or hand the model a superuser connection and hope for the best. Claudoo is built the other way around — security first:

If you sell or run Odoo for clients, the security posture is the feature: you can give business users a natural-language window into their ERP without widening anyone's access by a single record.

OWL chat UI ──/claudoo/send (auth=user)──► Odoo worker ──► daemon thread
   ▲ bus stream (deltas, tool chips)                          │ spawns
   │                          claude -p --output-format stream-json (OAuth)
   │                          tool surface = mcp__odoo__* ONLY
   │                                       │ stdio MCP
   │                                       ▼
   │               bridge/mcp_server.py  (no DB creds, loopback only)
   │                                       │ Bearer(session token)
   └──── bus.bus ◄── controllers/tools.py (auth='ai_bridge', runs AS the user) ──► Postgres

• Only Odoo touches the database. The CLI subprocess and the MCP forwarder hold no credentials — only a short-lived, session-scoped HMAC bearer token.
• The bridge is reachable on loopback only; the auth method rejects any non-local caller and rebinds the request to the session's user (su=False).
• Built-in tools are denied through a generated settings.json deny-list plus a PreToolUse hook, so the model is confined to mcp__odoo__*.

• Odoo 18.0
• The Claude Code CLI installed on the Odoo server (Claudoo auto-detects the binary; the path is configurable).
• Python requests (declared as an external dependency).
• A Claude subscription per user (OAuth login) — no API key required.

# Put the module on your addons_path (the repo is the module folder),
# then install it:
odoo-bin -c odoo.conf -d <your-db> -i claudoo --stop-after-init
# Restart your live server afterwards (Odoo does not re-import changed Python).

1. Open the Claudoo app from the top menu.
2. Click Login with Claude and authorize with your subscription.
3. Ask away: "How many sale orders are still in draft this month?"

Grant the AI SQL Analyst group to users who should be able to run read-only SQL reports, and AI Assistant Manager to those who configure it and read the audit log.

Claudoo treats LLM output as untrusted and defends accordingly:

• Never superuser. Tool endpoints abort if request.env.su is true.
• ACLs + record rules apply to every read and write, because the call runs as the user.
• Writes are opt-in. Read tools are the default; each write tool (orm_create/write/unlink, orm_action, run_wizard, run_server_action) must be granted per user, and zero-trust mode strips them entirely.
• SQL can only read. See the guard above.
• Capability tokens expire, are session-scoped, single-jti, and HMAC-signed with the database secret.

See SECURITY.md for the full threat model and how to report a vulnerability.

Settings → Claudoo (or System Parameters claudoo.*):

• AI Assistant User — can use the chat (ORM reads).
• AI SQL Analyst — additionally may run sql_select.
• AI Assistant Manager — configuration + audit log; sees all sessions.

odoo-bin -c odoo.conf -d <db> -i claudoo --test-enable --test-tags claudoo --stop-after-init

Covers the SQL guard, bridge-token mint/verify, the tool-access policy, the ai_bridge auth method, and the audit log. CI runs them on every push and PR.

Claudoo is free and open source (LGPL-3.0) and always will be. It is built and maintained by CICDoo, who also offer:

• 🚀 Managed deployment & hosting — Claudoo running securely on your Odoo, you manage your business and we manage your infrastructure
• 🛟 Priority support & SLAs for production rollouts.
• 🧩 Custom tools & integrations — extend the safe tool surface to your models and workflows.
• 📜 Commercial license for organizations that cannot adopt LGPL terms — modify Claudoo and keep your changes private, embed it in a closed product, or get warranty/indemnification. See COMMERCIAL_LICENSE.md.
• 🎓 Training & security review for teams enabling AI access to their ERP.

👉 Get in touch: sam@cicdoo.com · cicdoo.com

If Claudoo saves your team time, consider sponsoring its development.

• Approval-gated orm_create/orm_write/orm_unlink with before→after diff cards
• An admin allow/deny policy model for tools and models
• A dedicated ai_sql_ro Postgres role + view scoping
• OS-level sandboxing of the CLI subprocess
• Per-session rate and tool budgets

Have an idea? Open a feature request or a PR — see CONTRIBUTING.md.

Claudoo wraps Anthropic's Claude Code CLI. "Claude" and "Anthropic" are trademarks of Anthropic. Claudoo is an independent, community project and is not affiliated with or endorsed by Anthropic.

Claudoo is dual-licensed — choose whichever fits you:

• 🆓 Open source: GNU LGPL-3.0-or-later. Free for any use, including on both Odoo Community and Enterprise; modifications to Claudoo's own files stay under the LGPL.
• 💼 Commercial: a proprietary-friendly license from CICDoo that lifts the LGPL obligations (keep modifications private, embed in closed products, warranty/SLA). See COMMERCIAL_LICENSE.md · license@cicdoo.com.

SPDX-License-Identifier: LGPL-3.0-or-later OR LicenseRef-Claudoo-Commercial

© 2026 CICDoo