MitDesk
| Chat with your Odoo data. The AI acts as you, asks before it changes anything, and writes down what it did. |
Technical name minddesk.
Edition: Basic and above. See Editions and how the modules fit together.
This is the application. Every other MitDesk module needs it. It gives you chat, the Decisions board, autonomy rules, agents, tools, skills, an audit log, jobs, the Cockpit and the settings for AI models.
What it adds
- Chat that reads your records. Ask in plain words. Answers can list the Odoo records they came from.
- Tools with a gate. Before a tool runs, MitDesk decides: run it, ask a person first, or refuse it.
- Totals, not just pages. The
model_overviewtool returns exact totals and top groups for a whole model in one call. - Your choice of AI provider. Anthropic, OpenAI, Gemini, Mistral, Ollama, any OpenAI-compatible server, and named endpoints you add yourself.
- A spending ceiling. Set a monthly budget in USD. When it is reached, paid providers stop and local models keep answering.
- AI fields. An administrator names a text, choice or yes/no field that the AI may fill. Each fill goes through the same gate as any other AI write.
- Labelled AI notes. Chatter written by the AI carries an origin tag, in every installation.
Limits that always apply
- When the target is unknown, it never runs alone. If MitDesk cannot tell which record or model a call will touch, it asks or refuses. An autonomy rule can make this stricter, never looser.
- Money always asks. Any change to
account.move,account.move.lineoraccount.paymentneeds a person. No setting removes this. - Four state changes always ask. Confirming or cancelling a sales order, validating a transfer, and confirming a purchase order.
- The rules about the AI are off limits. The AI cannot write autonomy rules, agents, skills, tools, approvals, the audit log, jobs or flows. It also cannot write Odoo groups, access rights, record rules or server actions.
- A task may only ask so often. By default one request can stop and ask three times. After that the run ends. It never turns a question into a yes.
- Never as an administrator. An agent or flow cannot run as the superuser, OdooBot, a portal user, an administrator, an archived account or a user without MitDesk rights.
- Keys only go to known hosts. A provider key is sent only to a built-in vendor host, a loopback address or a host on your allowlist.
Where you find it
- Cockpit, Chat and Decisions
- Oversight ▸ Approvals, Audit and How Approvals Work
- Governance ▸ Do not ask me again and Reported answers
- Configuration ▸ Settings, and under Engine: AI Models, AI endpoints, AI Tools
- Configuration ▸ Who does the work: Agents, Skills
- Configuration ▸ Rules: Autonomy Rules, Test a decision, AI Fields
- Configuration ▸ What has run: Jobs, Conversations
What to know
- The provider libraries are loaded only when needed. The module installs without them, but a provider whose library is missing shows an error that names the package to install.
Requirements
Needs base, base_automation, html_editor, mail, web.
Related
- What MitDesk is
- How consent works
- The modules: every module and what it needs.
- Installing MitDesk: how to add it.