01
Bug fix
Reproduce against production-shaped data.
Give the agent the issue, an isolated clone, and direct access to logs, shell, SQL, and tests.
Example: fix a compute method that only fails on a 30+ GB customer database.
Free live webinar · AI-agent Odoo development
From Odoo issue to tested change. Live.
Watch an AI coding agent take a real task through an isolated production-shaped environment, module upgrade, logs, tests, and a human review boundary.
Next live session
September 23 · 15:00 UTC
17:00 CEST in Europe, 11:00 EDT / 8:00 PDT in the Americas
Your time:
Starts in
--
days
--
hrs
--
min
--
sec
Live build · no prepared result
task
Fix CRM scoring and cover the regression.
$ oduflow env create crm-scoring --from prod-template
✓ database cloned · filestore mounted · Odoo ready
environment: crm-scoring · 54 MCP tools connected
01
Agent edits
models/lead.py + tests
02
Oduflow applies
module upgraded
03
Runtime answers
traceback → fix
04
Reviewer decides
diff + green tests
18 tests passedready for review
Format
Live online
Length
45 min + 15 min Q&A
Level
Technical, practical
Price
Free
Free registration
Save your seat.
September 23 at 15:00 UTC. We will send the live access link and calendar invitation to your work email.
Your details are used only to manage the webinar and relevant follow-up. See our privacy policy.
60-minute session
Know exactly what you will see.
A compact explanation, a long live build, and enough time to challenge the workflow with your own Odoo reality.
0110 min
Why coding agents stall on real Odoo work
The missing runtime, production-shaped data, module state, logs, and feedback loop.
0225 min
From issue to working module — live
An agent provisions an isolated environment, changes code, upgrades the module, and reads the result.
0310 min
Tests, failures, and the review boundary
See where autonomy helps, where approvals belong, and what the developer reviews before merge.
0415 min
Your Odoo workflow + Q&A
Bring the task that costs your team time. We will map it to a practical agent loop.
The problem
AI can write code. Odoo still has to run it.
The code edit is only the beginning. The useful result is a working module, against the right data, with a visible runtime result.
The agent has code, but no Odoo runtime
It can edit Python and XML without knowing whether the module installs or the registry even loads.
A clean demo database hides real failures
Production configuration, data volume, dependencies, and custom modules are where the difficult bugs live.
Every feedback cycle needs a person
Restore, restart, upgrade, inspect logs, relay the error, repeat. The human becomes the agent's shell script.
More autonomy can mean more risk
Without isolation and a review boundary, a fast agent can simply produce mistakes faster.
What the webinar covers
One task. One closed Odoo feedback loop.
No copy-pasted traceback. No shared staging server. The agent gets controlled tools and the runtime answers directly.
Developer intent
Issue ODOO-184
“Fix the CRM scoring regression and prove it with a test.”
The human defines the goal and the acceptance boundary.
Agent loop
01
Provisionisolated DB + filestore
02
ChangePython, XML, access, tests
03
Applyinstall · upgrade · restart
04
Observelogs · shell · SQL · UI
05
VerifyOdoo tests + assertions
Reviewable result
Focused code diff
4 files changed
Module upgrade
completed
Regression suite
18 passed
Pull request
ready for human review
The agent gets fast feedback. The developer keeps the final decision.
01
Shorten feedback
Runtime errors return to the agent immediately.
02
Use real context
Test against the database shape that matters.
03
Isolate every task
Branches stop competing for one staging server.
04
Review evidence
Merge a result, not a confident explanation.
Start with one costly loop
Bug fixes, features, and every branch between.
You do not need to automate the whole SDLC. Start where environment setup and manual feedback consume the most engineering time.
02
Feature work
Build and upgrade in the same loop.
The agent edits the branch, applies the right Odoo action, validates behavior, and leaves a reviewable diff.
Example: add approval rules, access rights, views, and tests to an existing module.
03
CI and review
Give every branch its own Odoo.
Provision disposable environments for pull requests and make the runtime result part of code review.
Example: install changed modules, run tests, collect logs, then remove the environment.
Working Odoo infrastructure
The agent does more than edit files.
Oduflow gives the agent a constrained operational surface around the real Odoo lifecycle — while your infrastructure and review rules stay in control.
Clone the real baseline
PostgreSQL templates create isolated databases in seconds.
Share the filestore safely
Copy-on-write overlays avoid duplicating production-sized files.
Connect the coding agent
54 MCP tools expose environments, modules, tests, logs, shell, and SQL.
Apply the right Odoo action
pull_and_apply decides whether to upgrade, restart, or leave the process alone.
Run and read tests
The agent executes Odoo tests and consumes the result without human relaying.
Keep data on your infrastructure
Oduflow is self-hosted; databases, filestores, and code stay with you.
The control model
Fast agent loop. Explicit human boundary.
The webinar is not about removing developers. It is about removing the slow mechanical relay between an agent and an Odoo runtime.
The agent can provision, apply, inspect, and test inside an isolated environment.
Destructive operations remain visible and environment protection can block deletion.
A developer reviews the diff, runtime evidence, and business behavior before merge.
54
MCP tools
13–19
Odoo versions
C + E
Community + Enterprise
Local
data and code stay yours
Questions
Before you register.
Is the webinar free?
Yes. Registration is free, and we will email the access link and calendar invitation before the session.
Who is it for?
Odoo developers, technical leads, integrators, and agency teams already experimenting with Cursor, Codex, Claude Code, Cline, or other coding agents.
Will this be a real live demo?
Yes. The core of the session is a real branch, a real Odoo environment, actual module changes, runtime output, and tests — not a sequence of product slides.
Do I need to use a specific AI coding tool?
No. The workflow is MCP-native and the same Oduflow operations are also available from the CLI, so the concepts apply across agent clients and CI systems.
Can this work with our Odoo version and custom modules?
Oduflow targets Odoo Community and Enterprise versions 13–19 and is designed for repositories with real custom modules, dependencies, databases, and filestores.
Free live webinar · Sep 23, 15:00 UTC
See one real Odoo task become a tested, reviewable change.
Live build, practical boundaries, and your questions — in one focused hour.