Where AI agents meet human control
AI agents and MCP servers now create invoices, edit contacts and move stock inside Odoo. MCP AI Supervisor (Mission Control) is their flight recorder and their guardrails: every AI action captured in plain English, risky changes held for approval, and one-click rollback when the AI gets it wrong.
Turn AI activity into stories worth trusting
Works with any agent that talks to Odoo — MCP servers, RPC scripts, Odoo’s native AI — with no changes to the agent. Install, flag the AI’s identity, done.
A live feed of every AI action — in plain English
No JSON archaeology. Each action becomes a human sentence — «codex» updated Phone on 1 Vendor — with a risk score, field-level before/after diffs, and the raw payload one click away.
The feed separates API key actions (unambiguously the AI) from User account actions (an AI-flagged login — agent or human at the keyboard), so you always know how sure the attribution is.
Sessions tell the whole story
Related actions group into one session: «codex» — 8 actions across Contacts, max risk 21, 14 minutes. Open the timeline to replay exactly what the agent did, step by step.
A weekly digest email summarises AI activity per company — risk highlights included — for the managers who never open the backend.
Allow Ask Deny — you set the rules
Sequence-ordered policies match on model, operation, fields, record count, money amount, time window and identity. First match wins. Every rule reads back as a sentence, so you always know what it does.
Not sure a rule is right? Backtest it against your real history before it goes live — see exactly which past actions it would have blocked, held or allowed. Read-only, zero side effects.
A sensible starter pack ships enabled: bank-account changes, bulk edits, user/permission changes and posted-invoice deletion are covered on day one.
Risky changes wait for a human
When an Ask policy matches, the AI’s change is held — nothing touches your data. The agent is told an approval number; you see the masked field diff and one question: approve or reject?
Approve replays the change exactly as the AI intended, fully captured and linked. Reject leaves your data untouched. Unanswered requests expire on their own after 7 days.
One-click rollback, honestly labelled
Every captured action carries an honest reversibility flag. Safe writes and unreferenced creates roll back with one click — restore the before-state, log a mirror action, drop a note in the record’s chatter.
Payments, posted invoices, sent emails? Mission Control tells you upfront these can’t be un-done — protect those with an Ask policy instead. No false promises.
Setup Health: green means watching
The app opens on a single health screen: are identities active, are actions flowing, are policies / approvals / rollback switched on, has an identity expired? Every warning comes with a “Do this” instruction.
Up and running in three steps
Capture, a default policy pack and the weekly digest are live immediately. Nothing to configure to start seeing AI activity.
Create an AI Identity: link the Odoo user your agent logs in with, or pick the API key it authenticates with — the strongest attribution.
Read the Feed, tighten policies with the backtest button, approve what needs you. Setup Health stays green while it watches.
record rules built in
hardened access rights
for consoles & agent UIs
batched, safe cleanup
Let AI do the work. Stay in control.
Install MCP AI Supervisor today — your AI agents get to work, and you get the flight recorder, the guardrails and the undo button.
📖 Full guide: https://rubylabz.com/apps/mission-control/guide
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 6673 |
| Technical Name |
ai_mission_control |
| License | OPL-1 |
| Website | https://rubylabz.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module