How to Use Claude Code for Odoo Development: Complete Guide

What Is Claude Code?

Claude Code is Anthropic's command-line AI coding tool. Unlike code completion tools like Copilot that suggest the next line, Claude Code is agentic — it reads your project files, understands the codebase structure, runs commands, executes tests, and makes multi-file changes. For Odoo development, this means it can generate complete custom modules with models, views, security rules, data files, and tests, all coordinated across the right file structure.

Claude Code is particularly effective for Odoo because Odoo modules follow predictable patterns: Python models in models/, XML views in views/, security in security/, data in data/. Once Claude Code understands your Odoo version and conventions, it produces production-quality code that follows these patterns consistently.

Setting Up Claude Code for Odoo

Step 1: Install Claude Code

npm install -g @anthropic-ai/claude-code
claude

Step 2: Create a CLAUDE.md File

The most important step for Odoo development is creating a CLAUDE.md file in your project root. This file tells Claude Code about your specific Odoo setup:

# CLAUDE.md — Odoo 19 Custom Module Project

## Environment
- Odoo version: 19.0
- Python: 3.12
- Database: PostgreSQL 16
- Edition: Community

## Module Structure
- Custom modules in: /custom/addons/
- Each module follows standard Odoo structure:
  __manifest__.py, models/, views/, security/, data/, static/

## Coding Conventions
- Use _name and _description on all models
- Always add _sql_constraints or Constraint() for unique fields
- Use Odoo 19 patterns: Domain class, Constraint/Index classes
- Views use <list> (not <tree>) — this is Odoo 18+
- No attrs= in XML views — use invisible/readonly/required directly (Odoo 17+)
- Use fields.Date.today (not datetime.now)

## Testing
- Run tests: python odoo-bin -d testdb --test-tags /module_name
- Use TransactionCase for model tests
- Use HttpCase for controller tests

This context file is what separates mediocre AI output from production-quality Odoo code. Without it, Claude Code might generate v16-style views with attrs for a v19 project.

Step 3: Feed the Knowledge Base

For the best results, provide Claude Code with version-specific Odoo documentation. If you have knowledge base files (like the ones covering ORM, views, security, etc. for each version), reference them in your CLAUDE.md or feed them as context when starting a session.

What Claude Code Can Do for Odoo

Generate Complete Modules

Prompt: "Create an Odoo 19 module called project_milestone with a model for project milestones. Each milestone has a name, deadline (date), project_id (many2one to project.project), status (selection: draft/in_progress/done/cancelled), completion_percentage (integer 0-100), and notes (text). Add form, list, and search views. Add it as a tab on the project form."

Claude Code will generate:

• __manifest__.py with correct depends, data files, version
• models/project_milestone.py with all fields, constraints, and a compute method for status
• views/project_milestone_views.xml with form, list, search views
• views/project_views.xml with inherited view adding the milestone tab
• security/ir.model.access.csv with user and manager access rules

All following Odoo 19 conventions: <list> instead of <tree>, no attrs, proper Constraint() syntax.

Write XML Views

Claude Code excels at Odoo view generation because views follow strict XML patterns. It handles:

• Form views with proper <sheet>, <group>, <notebook> structure
• List views with widget attributes, optional columns, color decorations
• Kanban views with QWeb templates and progress bars
• Search views with filters, group-by options, and default filters
• View inheritance with correct xpath expressions

Create Security Rules

Security is where many developers make mistakes. Claude Code generates:

• ir.model.access.csv with appropriate read/write/create/unlink permissions
• Record rules with domain-based access control
• Security groups with proper hierarchy (user → manager → admin)
• Multi-company rules when needed

Build QWeb Reports

Prompt: "Create a PDF report for project_milestone that shows all milestones for a project, grouped by status, with a progress bar showing overall completion."

Claude Code generates the QWeb template, report action, and paper format — including proper t-foreach, t-if, and styling for print.

Write Tests

Prompt: "Write tests for the project_milestone model. Test CRUD operations, the status constraint (completion must be 100 for done status), and the access rules."

Claude Code generates TransactionCase tests with proper setup methods, test data, and assertion patterns that follow Odoo testing conventions.

Debug ORM Errors

Paste a traceback and ask: "Why is this failing?" Claude Code reads the error, identifies the root cause (missing field, wrong domain syntax, permission issue), and suggests the fix with exact code changes.

Generate Migration Scripts

Prompt: "I need to migrate this module from Odoo 17 to 18. What changes are needed?"

Claude Code identifies version-specific breaking changes: <tree> → <list>, deprecated APIs, changed method signatures, and generates the migration script and updated files.

Version-Specific Tips

Odoo 17 — attrs Removal

The biggest breaking change in recent Odoo history. In v17, attrs={'invisible': [('state', '!=', 'draft')]} became invisible="state != 'draft'". Always specify your Odoo version in CLAUDE.md to ensure Claude Code generates the correct syntax.

Odoo 18 — tree to list

All <tree> tags became <list>. Claude Code handles this correctly when it knows the target version, but will default to <tree> if the version is ambiguous.

Odoo 19 — ORM Package Split

The ORM was refactored into odoo/orm/ with submodules. Imports still work via re-exports (from odoo import fields, models is unchanged), but internal ORM patterns changed. Claude Code with the v19 knowledge base handles this correctly.

Claude Code vs Other AI Tools for Odoo

Claude Code's advantage for Odoo is its agentic nature. When you ask it to create a module, it generates all the files, checks for consistency, runs tests if available, and fixes issues — without you switching between files manually.

Best Practices

• Always specify the Odoo version in CLAUDE.md — this is the single most important thing you can do
• Feed the knowledge base — version-specific KB files eliminate hallucination on API details
• Review generated security rules — AI can miss edge cases in record rules; always verify access control manually
• Test in a staging database — never deploy AI-generated code directly to production without testing
• Use Claude Code for the first draft, then refine — it gets 80-90% right on the first try; the remaining 10-20% needs human judgment

Deploy Your AI-Built Modules with DeployMonkey

Once Claude Code generates your Odoo module, you need somewhere to deploy it. DeployMonkey lets you push custom modules to your Odoo instance via Git integration — commit your code, and DeployMonkey's CI/CD pipeline installs it automatically. Combined with the built-in AI agent for monitoring, you get an end-to-end AI-powered Odoo development and operations workflow. Try it free at deploymonkey.com.