Your work. Your connection.
The v0.3.0 source release connects directly to Odoo from your own execution environment. No Odoo addon or hosted backend is required.
Before you start
You need Node.js 24 or newer, an execution-capable host such as local Codex, and an Odoo 19 instance with external JSON-2 API access. API availability depends on your Odoo plan and deployment. Your personal API key keeps your normal Odoo permissions.
Ordinary chat cannot run a local helper or read your computer’s configuration. ChatGPT or Cloud hosts need their own supported execution and secret-file access; those integrations have not been validated. The existing ChatGPT listing is separate: its installed version and availability are not verified by this source release.
Try the sample dashboard
Download and extract the standard source package, then run these commands in its folder. This read-only sample uses fictional data and no Odoo credentials.
npm ci --omit=dev
echo '{"operation":"dashboard"}' | node scripts/odoo.js --demoThe helper returns the path to a local HTML report. Open that file in your browser; no local web server is started. Your shell must send the JSON object as standard input.
Use a private configuration
Copy config.example.json to a private config file outside the repository. Add your HTTPS Odoo URL, database and personal API key there. Set filesystem permissions for your account only. The file is plaintext: protect it like a password. Never paste keys in chat, upload them here or commit them to Git.
echo '{"operation":"context"}' | node scripts/odoo.js --config "C:/private/odoo/config.json"Install the bundled skill in a host that can execute the helper and access that private file. Start with context discovery on staging. Then list your work and verify one small, explicitly confirmed change before production use. See docs/direct-access.md in the package.
Fit your company’s workflow
Discovery checks models and fields visible to your account. Your private configuration can map company-specific fields, ownership, required defaults, completion and reviewed workflow actions. Metadata describes structure; it cannot infer your company’s business rules.
Unknown completion stays unknown. Submission or approval requires an explicit supported action and saved-state checks. Wizard-based flows need Odoo or a reviewed adapter. Todos and notes are private local records unless explicitly mapped to Odoo; the dashboard identifies their source.
Review every change
The helper prepares an exact preview for the acting user, company and record. After your confirmation it rechecks the record and mapping, executes once, and reads back saved values. Durable local receipts prevent repeating the same operation.
If a connection fails after a write, the result may be uncertain. Do not create a fresh operation to retry it: check the receipt and reconcile in Odoo first. Custom automation may have external effects that cannot be undone.
Validation and local data
Automated tests use native-API fixtures, including stale records, uncertain writes and duplicate prevention. Local desktop and mobile reports are checked separately. Live Odoo, an installed ChatGPT listing and Cloud execution still need environment-specific validation.
Configuration remains on your execution host. Requests go directly to Odoo. Local SQLite receipts, todos, notes and generated reports contain work data; protect backups and remove old files when no longer needed. Revoke your API key in Odoo when disconnecting.
Want organisation-managed mappings? The optional free organisation module is a separate download.