100% Local AI for Odoo,
with your own trained
models. No cloud. No subscriptions.
OdooClaw 1.0 ships with its own trained models — OdooClaw Light 1.2B (95% accuracy, 600/600 creations) and OdooClaw Vision (794/800 fields). 134 tools across 5 MCP servers, a 4-layer OCR pipeline, dual-layer memory, and dynamic billing rules. Runs on any hardware: VPS 1 vCPU (20 tok/s) → M1 Ultra (643 tok/s).
If OdooClaw helps your Odoo work, a GitHub star helps more people find it.
$ ./odooclaw serve --port 8080
INFO: Starting Odooclaw lightweight engine (Go runtime)...
INFO: Successfully connected to Odoo instance
→ Establishing async webhook listener on /api/discuss
→ Loading MCP tools and permission guards
READY: Listening for Odoo Discuss events.
Pick a capability. See why it matters.
OdooClaw 1.0 ships with its own trained models — but remains fully model-agnostic. 134 tools across 5 MCP servers, a 4-layer OCR pipeline, dual-layer memory, dynamic billing rules, and ToolGuard protection. Runs on any hardware: VPS 1 vCPU (20 tok/s) → M1 Ultra (643 tok/s).
Star OdooClaw on GitHubTrained models
OdooClaw Light 1.2B (95% accuracy, 600/600 creations) and Vision (794/800 fields). Published on HuggingFace as GGUF + MLX + Ollama. Or bring your own model.
134 tools · 5 MCP servers
Only the 3–5 relevant tools injected per query: 245 tokens instead of 14,000. Deterministic counting, hallucination rejection, and ToolGuard protection.
ToolGuard + permissions
Schema validation + destructive-operation gating, deny-by-default. Every operation inherits Odoo ACLs and record rules.
4-layer OCR · Dynamic billing
Vision → fiscal → header → validation. Zero hardcoded taxes. account_dynamic_rules with tax_ids + fiscal_position_id decided by Odoo from the OCR JSON.
Built for Odoo, not bolted on top of it.
Most AI tools treat ERP systems like generic databases. OdooClaw does not. It is designed around how Odoo actually works: Discuss conversations, user permissions, business objects, and real operational workflows.
It helps teams move faster without bypassing the rules that keep ERP systems safe.
With Browser Copilot, teams can also guide web actions from controlled workflows while keeping Odoo as the operational source of truth.
Works inside Odoo workflows
Respects access rights and record rules
Handles asynchronous operations cleanly
Connects to tools and external services when needed
v1.0.0 Next Generation: your own AI, on your own hardware
OdooClaw 1.0 is the first stable release of the Next Generation: a complete, 100% local AI system for Odoo with its own trained models — no subscriptions, no cloud, no API keys. It ships with OdooClaw Light 1.2B (95% accuracy, 600/600 creations) and OdooClaw Vision (794/800 fields), plus 134 tools, 5 MCP servers, a 4-layer OCR pipeline, dual-layer memory, and dynamic billing rules.
Own trained models
OdooClaw Light 1.2B (95% real-conversation accuracy, 600/600 record creations) and OdooClaw Vision (794/800 fields). Published on HuggingFace as GGUF + MLX + Ollama. Or bring your own model — any OpenAI-compatible endpoint.
134 tools · 5 MCP servers
Only the 3–5 relevant tools injected per query: 245 tokens instead of 14,000. Deterministic counting (odoo_count), hallucination rejection, and ToolGuard protection.
4-layer OCR pipeline
Vision → deterministic fiscal → LLM header → arithmetic validation. Cross-checks against Odoo reality. Never invents data; failures go to declared review.
Dynamic billing rules
account_dynamic_rules amplified with tax_ids + fiscal_position_id (PR #9 merged). Tax and fiscal position decided by Odoo from OCR JSON — zero hardcoded taxes.
Memory system
HOT + COLD dual-layer memory, structured session memory (NRA-511), knowledge base + tool retrieval (NRA-515), always-on recipe store.
Performance
VPS 1 vCPU (20 tok/s) → M1 Ultra (643 tok/s). Less than 1GB of models. n-gram speculative decoding: +49% tok/s (NRA-541). One-shot local installer.
Core capabilities
OdooClaw focuses on practical, high-value operations that matter in day-to-day Odoo usage.
Own trained models
OdooClaw Light 1.2B (95% accuracy, 600/600 creations) and Vision (794/800 fields). Published on HuggingFace as GGUF + MLX + Ollama. Or bring your own model.
134 tools · 5 MCP servers
Only the 3–5 relevant tools injected per query: 245 tokens instead of 14,000. Deterministic counting, hallucination rejection, and ToolGuard protection.
4-layer OCR pipeline
Vision → deterministic fiscal → LLM header → arithmetic validation. Never invents data; failures go to declared review. Validated on real invoices.
Dynamic billing rules
account_dynamic_rules with tax_ids + fiscal_position_id (PR #9 merged). Tax and fiscal position decided by Odoo from OCR JSON — zero hardcoded taxes.
Dual-layer memory engine
HOT + COLD dual-layer memory, structured session memory (NRA-511), knowledge base + tool retrieval (NRA-515), always-on recipe store.
ToolGuard anti-hallucination
Schema validation + destructive-operation gating, deny-by-default, escape hatch via ir.config_parameter. Reply-token validation on every webhook.
n-gram speculative decoding
Benchmarked +49% tok/s on Linux (NRA-541). Runs on any hardware: VPS 1 vCPU (20 tok/s) → M1 Ultra (643 tok/s). Less than 1GB of models.
Native Discuss integration
Interact with OdooClaw from Odoo Discuss so users can work where they already communicate. Voice notes and private 1:1 reply routing supported.
How it works
A user sends a request from Odoo
The interaction starts inside Odoo, typically through Discuss or an integrated business flow.
Odoo triggers OdooClaw asynchronously
A webhook sends the event to OdooClaw so the main Odoo workers are not blocked by long-running AI or document-processing tasks.
OdooClaw gathers context and checks permissions
The system evaluates the user context, relevant business data, and security boundaries before taking action.
Tools execute the requested work
OdooClaw can call Odoo operations, OCR pipelines, voice services, or external tools depending on the workflow.
The result goes back into Odoo
Responses, extracted data, or completed actions are returned to Odoo so users stay inside the same operational loop.
Guided browser automation, connected to Odoo.
Copilot extends OdooClaw with controlled web interaction for scenarios where data lives in portals or external back offices. Teams keep Odoo as the decision center while Copilot executes browser steps with security guardrails.
Trigger from Odoo
A user launches a guided Copilot task from Discuss or an operational flow in Odoo.
Policy and context check
OdooClaw applies permissions, allowlists, and task policy before any browser interaction.
Execute with guardrails
The extension performs read-first actions, asking explicit confirmation before write operations.
Return audited result
Results and action traces return to Odoo for traceability and follow-up workflows.
Security first, because this is ERP.
ERP automation is useful only when it remains trustworthy. OdooClaw is designed to operate within Odoo’s existing security boundaries instead of trying to bypass them.
- shield Inherits user permissions
- rule Respects Odoo access rights and record rules
- fact_check Supports confirmation flows for critical actions
- policy Browser Copilot supports read-only mode and domain allowlists by default
- touch_app Action execution requires explicit user confirmation before write operations
- account_tree Keeps operational context separated and auditable
- dns Fits self-hosted environments where data control matters
- encrypted Supports reverse-proxy TLS and optional native gateway TLS
Practical use cases
Accounting assistance
Use OCR and contextual actions to speed up invoice intake, validation, and operational review.
Sales and CRM support
Retrieve customer context, create records, and assist commercial teams directly from Odoo workflows.
Operations and internal support
Answer internal questions, trigger routine actions, and reduce repetitive ERP work.
Voice-driven usage
Enable faster interaction on mobile or in operational environments where typing is inconvenient.
Browser Copilot workflows
Run controlled browser tasks with secure defaults (read-only mode, domain allowlists, explicit confirmation) and connect results back to Odoo operations.
Designed for real deployments
OdooClaw is intended to run close to Odoo, connect to language models and tools, and return results safely back into the ERP workflow. Browser Copilot can be added as an optional extension layer for guided web execution.
Deploy the way your stack requires
OdooClaw is suitable for self-hosted environments and flexible enough to work with different deployment strategies.
- check On the same server as Odoo
- check On a separate gateway host
- check With local models
- check With remote providers
- check With custom tool integrations and Browser Copilot
- check With reverse-proxy TLS or native TLS for standalone gateways
Start building with OdooClaw
Read the installation guides, configure providers, tools, and Browser Copilot, and deploy OdooClaw into your Odoo environment step by step.
Read the DocsLatest Updates
Follow the evolution of OdooClaw. Real updates directly from our repository.
v1.0.0 Next Generation: trained models, 134 tools, 4-layer OCR
OdooClaw 1.0 ships with its own trained models (Light 1.2B, Vision), 134 tools across 5 MCP servers, a 4-layer OCR pipeline, dual-layer memory, and dynamic billing rules. 46/46 Go packages green, 23/23 Odoo tests, 8/8 E2E.
Commit Highlights
- v1.0.0: Own trained models (HF: GGUF + MLX + Ollama), 134 tools, 5 MCP servers, 4-layer OCR pipeline, dynamic billing rules, ToolGuard.
- PR #64: Unify lms + main lines into one stable branch with full CI gate. n-gram +49% tok/s (NRA-541).
v0.3.0: secure purchases, inventory, and warehouse operations
OdooClaw v0.3.0 expands safe day-to-day business operations and hardens delegated Odoo permissions, with real validation against Doodba 18.
Commit Highlights
- v0.3.0: Add validated purchase, vendor-bill, inventory, and warehouse workflows.
- security: Enforce delegated ACLs, record rules, company context, and controlled writes.
Browser Copilot + Odoo Modules for v16/v17/v18
The Browser Copilot backend and extension workflow were added, alongside native Odoo modules adapted for versions 16, 17, and 18.
Commit Highlights
- 31d1d38: Add browser extension and Odoo modules for v16/v17/v18.
- 9422811: Add Browser Copilot backend and markdown sanitizer.
Help OdooClaw reach more Odoo teams.
A star is small, but it gives maintainers signal, helps other implementers discover the project, and makes the roadmap easier to justify.
Bring AI into Odoo without turning your ERP into a science project.
OdooClaw helps teams add practical AI, OCR, voice, and dual-layer memory to Odoo while keeping architecture lean, recall traceable, and security grounded.