AI assistant for Odoo,
built to run where
your ERP lives.
Odooclaw brings AI assistance, OCR, voice interactions, and dual-layer memory directly into Odoo. Lightweight, asynchronous, and designed for real production environments with scoped and explainable recall.
$ ./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.
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
Core capabilities
OdooClaw focuses on practical, high-value operations that matter in day-to-day Odoo usage.
Native Discuss integration
Interact with OdooClaw from Odoo Discuss so users can work where they already communicate, without jumping between tools.
Permission-aware actions
OdooClaw inherits the user context and operates within Odoo’s security model, helping avoid dangerous shortcuts and invisible privilege escalation.
OCR for business documents
Extract structured information from invoices, receipts, and other operational documents to reduce manual entry and speed up accounting workflows.
Voice interactions
Add speech-to-text and text-to-speech flows for hands-free operation, mobile usage, and faster interaction in real business environments.
Async architecture
Built around asynchronous webhooks so Odoo workers stay responsive while OdooClaw handles heavier processing outside the critical request path.
Browser Copilot integration
Connect a lightweight browser extension to execute guided web flows with token auth, read-only defaults, allowlisted domains, and explicit confirmation before actions.
Dual-layer memory engine
Combines HOT operational memory with COLD historical memory for durable recall, scoped isolation, temporal facts, and explainable retrieval.
Context-aware execution
Designed to work with business context, model data, and operational intent instead of behaving like a disconnected chatbot.
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
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
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.
Scoped Historical Memory (HOT + COLD) is now live
OdooClaw now ships with dual-layer memory, scoped historical recall, temporal facts, timeline queries, explainability tooling, and optional historical import with dry-run + dedupe.
Commit Highlights
- 37ab8f1: Add scoped historical memory layer and tools.
- c3404e5: Document historical memory and Odoo chat QA.
Browser Copilot + Odoo Modules for v16/v17/v18
Recent releases add the Browser Copilot backend and extension workflow, plus native Odoo modules adapted for versions 16, 17, and 18.
Commit Highlights
- 31d1d38: Add browser extension and Odoo modules v16-18.
- 9422811: Add Browser Copilot backend and markdown sanitizer.
Markdown Rendering & Documentation Improvements
Earlier updates improved markdown rendering quality and refreshed key docs so setup and usage flows are clearer across Odoo and Browser Copilot scenarios.
Commit Highlights
- 68cccc9: Improve Odoo markdown renderer.
- 4932526: Update README.md with latest integration details.
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.