AI Engine

Where to configure

AI Engine app (not Settings → General Settings, not Technical). Providers, agents, URL whitelist and MCP users live in that app.

Paste the provider API key on the provider form. Set failover order on the agent (the Chatboo agent, or the one your MCP user uses). Secrets never travel in the addon.

What it is

The product AI layer. It owns providers, agents, contexts, skills, Safe Plan writes and the MCP endpoint that Cursor (and other clients) call. Chatboo is a separate module: it owns the conversation UI and talks to this engine. This module does not depend on Chatboo.

Knowledge that is generic to the suite lives here (geo fabric, partners, accounting, ACL…). Pilot-only skills, Sesame/CDMON connectors and the Occidente failover chain belong in occ_custom_ai, not in this repo.

What it ships

MCP server — tools and prompts for Cursor and other MCP clients. The instance is the source of truth; clients do not keep a second copy of skills.
Inference — LLM drivers (OpenAI-compatible, Anthropic, Ollama, …) and provider failover on the agent. A key is pasted per instance; it never travels in the module.
Safe Plan — proposed writes wait for a human Confirm in Odoo. The engine does not apply ORM writes behind the operator’s back.

Knowledge — product contexts and skills (pns_*). Domain cheat-sheets regenerate; they are not versioned as customer dumps.
External APIs — OpenAPI / MCP servers plus a typed URL whitelist. A whitelist row is a hostname, not a secret.
PAAP — the open agent protocol this engine implements. Chatboo, OCR and future UIs are consumers, not a second engine.

What it does not do

No chat UI — that is pns_ai_chatboo. Install Chatboo if people will talk from the Odoo systray.
No customer pack — Occidente skills, Sesame/CDMON tokens and the pilot failover chain are occ_custom_ai.
No map HTTP — geocoding and routes go through pns_geo / geo.service. The engine must not call Google or OSM itself.
No secrets in the addon — provider keys, API tokens and env credentials stay in the database (or the instance env). The module only leaves the slot.

How to configure

Before Apps: in the Odoo Python, install the extras stock Odoo does not ship (httpx, pydantic; on Odoo 14 also openpyxl>=3.1.2). Then install pns_base and this module. Install pns_geo if maps or geocoding will be used.
Open the AI Engine app. Create or open a provider, paste the API key, pick a model and save.
On the Chatboo agent (or the agent your MCP user uses), set the provider and the failover chain. Order is on the agent, not in Chatboo.
If Cursor will call this instance: create an MCP user / API key and point the client at this database. Whitelist any extra hostnames the tools need.
Pilot databases: install occ_custom_ai after the engine so Occidente skills and connectors seed on top. Paste Sesame/CDMON tokens there, not here.

Family

Module	Where	Role
`pns_ai_mcp`	O14 and O19	This engine: providers, knowledge, MCP, Safe Plan
`pns_ai_chatboo`	O14 and O19	In-Odoo chat UI; depends on the engine
`occ_custom_ai`	O14 and O19	Occidente pack: pilot skills and connectors. Product never depends on it.

UI source in English. Layout: common/ plus OWL1 (O13–14) and OWL2 (O15–19+) stacks.

PATANEGRA Soft — Apache License 2.0 (OSI approved). See LICENSE.