odoo-agent-cli 0.4.0__tar.gz → 0.6.0__tar.gz

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: odoo-agent-cli
-Version: 0.4.0
+Version: 0.6.0
 Summary: Odoo JSON-RPC CLI and Python client built for AI agents and scripts.
 Project-URL: Homepage, https://github.com/Organize-IT/odoo-cli
 Project-URL: Issues, https://github.com/Organize-IT/odoo-cli/issues
@@ -43,8 +43,10 @@ uv tool install odoo-agent-cli   # or: pipx install odoo-agent-cli
 odoo --version
 ```
 
-Requires Python 3.11+. Works with Odoo 17, 18 and 19 (integration-tested in CI), and should
-work with any version exposing `/jsonrpc` with API keys (14+).
+Requires Python 3.11+. Works with Odoo 15 through 20 (integration-tested in CI on 15.0,
+16.0, 17.0, 18.0, 19.0 and 20.0, Community), and should work with any version exposing
+`/jsonrpc` with API keys (14+). Odoo 20 still serves `/jsonrpc` but logs it as deprecated;
+Odoo plans to remove it in 22.
 
 ## 60 seconds
 
@@ -67,7 +69,8 @@ odoo group invoices -w unpaid --by partner_id --sum amount_residual
 anything is sent, and the technical names keep working. Full documentation:
 [Organize-IT.github.io/odoo-cli](https://github.com/Organize-IT/odoo-cli/tree/main/docs).
 
-Prefer named connections? They live in a `0600` TOML file:
+Prefer named connections? They live in a TOML file written owner-only where the platform
+can enforce that — `odoo profile path --check` says whether it can:
 
 ```bash
 odoo profile add acme --url https://acme.odoo.com --db acme --login bot@acme.com \
@@ -84,7 +87,10 @@ First match wins, and the CLI never prompts:
 3. a profile named `default`
 
 Nothing found: exit code 3 with a message listing those three ways. A profile stores the key
-(`--api-key`) or points to an env var (`--api-key-env`). `odoo profile path` shows the file.
+(`--api-key`) or points to an env var (`--api-key-env`). `odoo profile path` shows the file,
+`--check` reports what its permissions are actually worth: mode 600 means owner-only on
+POSIX and nothing at all on Windows, where `chmod` only toggles a read-only attribute. On
+such a platform, prefer `--api-key-env` and keep the key in your secret manager.
 
 ## Output contract
 
@@ -96,6 +102,7 @@ Nothing found: exit code 3 with a message listing those three ways. A profile st
 | bad arguments | | `{"error": ...}` | 2 |
 | connection, auth, no profile | | `{"error": ...}` | 3 |
 | refused by a guard | | `{"error": ...}` | 4 |
+| query repaired to run | rows | `{"error": ...}` | 5 |
 | write executed | result | `{"write": {"model", "method", "ids", "fields"}}` | 0 |
 
 Data is never humanised: many2one fields stay `[id, "name"]`, empty values stay `false`.
@@ -134,6 +141,31 @@ A bare word is looked up as a preset for the model: `-w overdue`, `-w unpaid`, `
 `-w confirmed`, `-w archived`. `odoo alias MODEL --presets` lists the ones that apply. A bare
 word that is not a preset exits 2 listing the ones that are.
 
+## Your own names
+
+The shipped table covers what most tenants call things. A profile file adds the rest, and a
+user entry replaces a built-in of the same name — your tenant knows its vocabulary better than
+this tool does:
+
+```toml
+[aliases.subscriptions]
+model = "sale.subscription"
+domain = [["stage_category", "=", "progress"]]
+help = "Running subscriptions"
+
+[aliases.invoices]                     # replaces the built-in
+model = "account.move"
+domain = [["move_type", "=", "out_invoice"], ["company_id", "=", 3]]
+
+[presets.mine]
+domain = [["user_id", "=", 7]]
+models = ["crm.lead", "sale.order"]
+```
+
+`odoo alias` marks each entry `builtin` or `config`. A malformed table fails the command with
+exit 2 instead of being skipped: a filter you believe is applied and is not is exactly what
+this mechanism exists to avoid. Dynamic dates work too — `@today`, `@month-start`, `@year-start`.
+
 ## Names and typos
 
 Read commands accept an alias in place of a technical model name (`invoices`, `customers`,
@@ -166,7 +198,10 @@ odoo group invoices -w overdue --by partner_id --sum amount_residual \
 odoo group invoices --by invoice_date:month --sum amount_total
 ```
 
-`read_group` under the hood: counts and totals per group without pulling the records.
+`read_group` under the hood: counts and totals per group without pulling the records. On
+Odoo 20, whose `read_group` no longer answers JSON-RPC callers, it is `formatted_read_group`,
+and its answer is passed through as is: totals are keyed `amount_residual:sum` rather than
+`amount_residual`, and each group's filter is `__extra_domain`.
 
 ## Writes
 
@@ -192,8 +227,9 @@ are refused unless `--include-sensitive`.
   many2one shapes) and recipes.
 - The same text ships as an [Agent Skill](https://github.com/Organize-IT/odoo-cli/blob/main/SKILL.md):
   `npx skills add Organize-IT/odoo-cli`.
-- `odoo search ... --lenient-fields` removes fields Odoo rejects and retries, with a warning on
-  stderr. Exploration only.
+- `odoo search ... --lenient-fields` removes fields Odoo rejects and retries. It prints the
+  rows, then exits **5**: they answer a wider question than the one you asked. Exploration
+  stays comfortable; a script that checks its exit codes cannot be fooled by it.
 
 ## Library
 
@@ -223,14 +259,17 @@ async with AsyncOdooClient(url, db, login, key) as odoo:
 ```
 
 Exceptions: `OdooError` (base, `.code`, `.message`, `.data`), `OdooConnectionError`,
-`OdooAuthError`, `OdooAccessError`, `OdooValidationError`, `OdooMissingError`.
+`OdooAuthError`, `OdooAccessError`, `OdooValidationError`, `OdooMissingError`,
+`OdooFieldMissingError`.
 
 Both clients accept `context={...}` (merged into every call; a per-call `context=` keyword
 wins), `verify_ssl=False` and `max_retries`. HTTP 429 is always retried with backoff and
 `Retry-After`; network errors, timeouts and HTTP 5xx are retried only for calls that cannot
 change data, so a `create` that timed out is never replayed. Logs go to the `odoocli.rpc`
-logger. Domain helpers live in `odoocli.domain`, guards in `odoocli.security`, the opt-in
-repair loop in `odoocli.lenient`.
+logger. Domain helpers live in `odoocli.domain`, guards in `odoocli.security`, the repair
+loop in `odoocli.lenient`: `lenient_search_read` drops rejected fields from `fields` and
+`order` on its own, but a rejected field in the domain raises `OdooFieldMissingError` unless
+you pass `strip_domain=True`, because removing a filter widens the query.
 
 ## Development
 
@@ -243,18 +282,21 @@ uv run pytest --cov --cov-report=term-missing   # gated at 93% in CI
 uv run --group docs mkdocs serve     # the documentation site
 
 ODOO_VERSION=17.0 scripts/start-odoo.sh                     # throwaway Odoo in Docker
+                                   # 15.0 to 20.0; 20.0 is built from docker/odoo20/SHA;
+                                   # ODOO_PORT=8169 if 8069 is taken
 ODOO_URL=http://localhost:8069 ODOO_DB=test ODOO_LOGIN=admin ODOO_API_KEY=admin \
 ODOO_ALLOW_WRITES=1 uv run pytest -m integration -o addopts=""
 docker compose -f docker/odoo-compose.yml down -v
 ```
 
 CI runs the unit suite on Python 3.11-3.13 and builds the docs on every PR; the integration
-matrix (Odoo 17.0, 18.0, 19.0) runs on `main`, tags and manual dispatch. Releases are
+matrix (Odoo 15.0 to 20.0) runs on `main`, tags and manual dispatch. Releases are
 published to PyPI on `v*` tags through trusted publishing, with every action pinned to a
 commit digest.
 
 `AGENTS.md` is the specification: layering, the contracts that may not change silently, and
-the definition of done. Read it before changing anything.
+the definition of done. [docs/decisions/](docs/decisions/) records the decisions with a real
+trade-off behind them. Read both before changing anything.
 
 ## License
 

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/README.md

@@ -16,8 +16,10 @@ uv tool install odoo-agent-cli   # or: pipx install odoo-agent-cli
 odoo --version
 ```
 
-Requires Python 3.11+. Works with Odoo 17, 18 and 19 (integration-tested in CI), and should
-work with any version exposing `/jsonrpc` with API keys (14+).
+Requires Python 3.11+. Works with Odoo 15 through 20 (integration-tested in CI on 15.0,
+16.0, 17.0, 18.0, 19.0 and 20.0, Community), and should work with any version exposing
+`/jsonrpc` with API keys (14+). Odoo 20 still serves `/jsonrpc` but logs it as deprecated;
+Odoo plans to remove it in 22.
 
 ## 60 seconds
 
@@ -40,7 +42,8 @@ odoo group invoices -w unpaid --by partner_id --sum amount_residual
 anything is sent, and the technical names keep working. Full documentation:
 [Organize-IT.github.io/odoo-cli](https://github.com/Organize-IT/odoo-cli/tree/main/docs).
 
-Prefer named connections? They live in a `0600` TOML file:
+Prefer named connections? They live in a TOML file written owner-only where the platform
+can enforce that — `odoo profile path --check` says whether it can:
 
 ```bash
 odoo profile add acme --url https://acme.odoo.com --db acme --login bot@acme.com \
@@ -57,7 +60,10 @@ First match wins, and the CLI never prompts:
 3. a profile named `default`
 
 Nothing found: exit code 3 with a message listing those three ways. A profile stores the key
-(`--api-key`) or points to an env var (`--api-key-env`). `odoo profile path` shows the file.
+(`--api-key`) or points to an env var (`--api-key-env`). `odoo profile path` shows the file,
+`--check` reports what its permissions are actually worth: mode 600 means owner-only on
+POSIX and nothing at all on Windows, where `chmod` only toggles a read-only attribute. On
+such a platform, prefer `--api-key-env` and keep the key in your secret manager.
 
 ## Output contract
 
@@ -69,6 +75,7 @@ Nothing found: exit code 3 with a message listing those three ways. A profile st
 | bad arguments | | `{"error": ...}` | 2 |
 | connection, auth, no profile | | `{"error": ...}` | 3 |
 | refused by a guard | | `{"error": ...}` | 4 |
+| query repaired to run | rows | `{"error": ...}` | 5 |
 | write executed | result | `{"write": {"model", "method", "ids", "fields"}}` | 0 |
 
 Data is never humanised: many2one fields stay `[id, "name"]`, empty values stay `false`.
@@ -107,6 +114,31 @@ A bare word is looked up as a preset for the model: `-w overdue`, `-w unpaid`, `
 `-w confirmed`, `-w archived`. `odoo alias MODEL --presets` lists the ones that apply. A bare
 word that is not a preset exits 2 listing the ones that are.
 
+## Your own names
+
+The shipped table covers what most tenants call things. A profile file adds the rest, and a
+user entry replaces a built-in of the same name — your tenant knows its vocabulary better than
+this tool does:
+
+```toml
+[aliases.subscriptions]
+model = "sale.subscription"
+domain = [["stage_category", "=", "progress"]]
+help = "Running subscriptions"
+
+[aliases.invoices]                     # replaces the built-in
+model = "account.move"
+domain = [["move_type", "=", "out_invoice"], ["company_id", "=", 3]]
+
+[presets.mine]
+domain = [["user_id", "=", 7]]
+models = ["crm.lead", "sale.order"]
+```
+
+`odoo alias` marks each entry `builtin` or `config`. A malformed table fails the command with
+exit 2 instead of being skipped: a filter you believe is applied and is not is exactly what
+this mechanism exists to avoid. Dynamic dates work too — `@today`, `@month-start`, `@year-start`.
+
 ## Names and typos
 
 Read commands accept an alias in place of a technical model name (`invoices`, `customers`,
@@ -139,7 +171,10 @@ odoo group invoices -w overdue --by partner_id --sum amount_residual \
 odoo group invoices --by invoice_date:month --sum amount_total
 ```
 
-`read_group` under the hood: counts and totals per group without pulling the records.
+`read_group` under the hood: counts and totals per group without pulling the records. On
+Odoo 20, whose `read_group` no longer answers JSON-RPC callers, it is `formatted_read_group`,
+and its answer is passed through as is: totals are keyed `amount_residual:sum` rather than
+`amount_residual`, and each group's filter is `__extra_domain`.
 
 ## Writes
 
@@ -165,8 +200,9 @@ are refused unless `--include-sensitive`.
   many2one shapes) and recipes.
 - The same text ships as an [Agent Skill](https://github.com/Organize-IT/odoo-cli/blob/main/SKILL.md):
   `npx skills add Organize-IT/odoo-cli`.
-- `odoo search ... --lenient-fields` removes fields Odoo rejects and retries, with a warning on
-  stderr. Exploration only.
+- `odoo search ... --lenient-fields` removes fields Odoo rejects and retries. It prints the
+  rows, then exits **5**: they answer a wider question than the one you asked. Exploration
+  stays comfortable; a script that checks its exit codes cannot be fooled by it.
 
 ## Library
 
@@ -196,14 +232,17 @@ async with AsyncOdooClient(url, db, login, key) as odoo:
 ```
 
 Exceptions: `OdooError` (base, `.code`, `.message`, `.data`), `OdooConnectionError`,
-`OdooAuthError`, `OdooAccessError`, `OdooValidationError`, `OdooMissingError`.
+`OdooAuthError`, `OdooAccessError`, `OdooValidationError`, `OdooMissingError`,
+`OdooFieldMissingError`.
 
 Both clients accept `context={...}` (merged into every call; a per-call `context=` keyword
 wins), `verify_ssl=False` and `max_retries`. HTTP 429 is always retried with backoff and
 `Retry-After`; network errors, timeouts and HTTP 5xx are retried only for calls that cannot
 change data, so a `create` that timed out is never replayed. Logs go to the `odoocli.rpc`
-logger. Domain helpers live in `odoocli.domain`, guards in `odoocli.security`, the opt-in
-repair loop in `odoocli.lenient`.
+logger. Domain helpers live in `odoocli.domain`, guards in `odoocli.security`, the repair
+loop in `odoocli.lenient`: `lenient_search_read` drops rejected fields from `fields` and
+`order` on its own, but a rejected field in the domain raises `OdooFieldMissingError` unless
+you pass `strip_domain=True`, because removing a filter widens the query.
 
 ## Development
 
@@ -216,18 +255,21 @@ uv run pytest --cov --cov-report=term-missing   # gated at 93% in CI
 uv run --group docs mkdocs serve     # the documentation site
 
 ODOO_VERSION=17.0 scripts/start-odoo.sh                     # throwaway Odoo in Docker
+                                   # 15.0 to 20.0; 20.0 is built from docker/odoo20/SHA;
+                                   # ODOO_PORT=8169 if 8069 is taken
 ODOO_URL=http://localhost:8069 ODOO_DB=test ODOO_LOGIN=admin ODOO_API_KEY=admin \
 ODOO_ALLOW_WRITES=1 uv run pytest -m integration -o addopts=""
 docker compose -f docker/odoo-compose.yml down -v
 ```
 
 CI runs the unit suite on Python 3.11-3.13 and builds the docs on every PR; the integration
-matrix (Odoo 17.0, 18.0, 19.0) runs on `main`, tags and manual dispatch. Releases are
+matrix (Odoo 15.0 to 20.0) runs on `main`, tags and manual dispatch. Releases are
 published to PyPI on `v*` tags through trusted publishing, with every action pinned to a
 commit digest.
 
 `AGENTS.md` is the specification: layering, the contracts that may not change silently, and
-the definition of done. Read it before changing anything.
+the definition of done. [docs/decisions/](docs/decisions/) records the decisions with a real
+trade-off behind them. Read both before changing anything.
 
 ## License
 

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/SKILL.md

@@ -18,6 +18,8 @@ Resolution order, first match wins:
 3. A profile named `default`
 
 Nothing resolved: exit code 3 and a message listing these three ways. The CLI never prompts.
+`odoo profile path --check` says whether the stored key is really owner-only on this
+platform; on Windows it is not, so prefer `--api-key-env` there.
 `ODOO_API_KEY` accepts an Odoo API key (preferred) or the user's password.
 Check a connection with `odoo info`. Self-signed on-prem server: `--insecure`
 (or `odoo profile add ... --no-verify-ssl`).
@@ -91,7 +93,8 @@ Refresh it after a module install or an Odoo upgrade with `odoo cache clear`.
 - Errors: one JSON object on stderr, `{"error": {"code": ..., "message": ..., "odoo": {...}}}`.
 - Warnings and write logs: one JSON object per line on stderr.
 - Exit codes: `0` ok, `1` Odoo raised, `2` bad usage, `3` connection or authentication,
-  `4` refused by a guard (writes disabled, missing `--yes`, sensitive model).
+  `4` refused by a guard (writes disabled, missing `--yes`, sensitive model), `5` the query
+  was repaired to make it run, so the rows answer a wider question than the one you asked.
 - Values of fields named like `password`, `api_key`, `secret` are replaced by `[redacted]`
   unless `--no-redact`.
 
@@ -113,7 +116,9 @@ odoo cache path|list|clear                  the schema cache
 `MODEL` accepts an alias on every read command. `odoo group` runs `read_group`, so you
 get counts and totals per group without pulling the records:
 `odoo group invoices -w overdue --by partner_id --sum amount_residual`.
-Grouping keys accept a date granularity: `--by invoice_date:month`.
+Grouping keys accept a date granularity: `--by invoice_date:month`. On Odoo 20 it runs
+`formatted_read_group` and passes its answer through: totals are keyed `amount_residual:sum`
+instead of `amount_residual`, and each group's filter is `__extra_domain`.
 
 Conditions (`-w`, repeatable, AND-ed together, combined with `--domain`):
 
@@ -171,10 +176,11 @@ One2many and many2many fields take Odoo commands, written as JSON in `-v` or `--
 5. Many2one values come back as `[id, name]`. Filter on them with the id
    (`-w partner_id=42`) or through a related field (`-w partner_id.name~acme`).
 6. Dates are strings, `YYYY-MM-DD` or `YYYY-MM-DD HH:MM:SS` in UTC.
-7. Field names drift between Odoo 17, 18 and 19 (for example `account.account.company_id`
+7. Field names drift between Odoo 15 and 20 (for example `account.account.company_id`
    became `company_ids`). If a field is rejected, `odoo fields` is the truth.
-   `--lenient-fields` on `search` removes rejected fields and retries, with a warning on
-   stderr; only use it for exploration, never in a script that relies on the result.
+   `--lenient-fields` on `search` removes rejected fields and retries. It prints the rows and
+   then exits 5, because they answer a wider question than the one you asked. Use it to
+   explore; if you keep it in a script, check the exit code.
 8. Never guess a model name: `odoo alias`, then `odoo models --like invoice`. A dotless
    name close to a known alias is reported as a typo instead of being sent.
 9. Sensitive models (`ir.config_parameter`, `ir.mail_server`, `res.users.apikeys`, `ir.cron`,

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "odoo-agent-cli"
-version = "0.4.0"
+version = "0.6.0"
 description = "Odoo JSON-RPC CLI and Python client built for AI agents and scripts."
 readme = "README.md"
 license = "MIT"
@@ -45,6 +45,7 @@ dev = [
   "ruff>=0.6",
   "mypy>=1.11",
   "pytest-cov>=5",
+  "hypothesis>=6.168.0",
 ]
 docs = [
   "mkdocs>=1.6",

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/src/odoocli/AGENT_GUIDE.md

@@ -13,6 +13,8 @@ Resolution order, first match wins:
 3. A profile named `default`
 
 Nothing resolved: exit code 3 and a message listing these three ways. The CLI never prompts.
+`odoo profile path --check` says whether the stored key is really owner-only on this
+platform; on Windows it is not, so prefer `--api-key-env` there.
 `ODOO_API_KEY` accepts an Odoo API key (preferred) or the user's password.
 Check a connection with `odoo info`. Self-signed on-prem server: `--insecure`
 (or `odoo profile add ... --no-verify-ssl`).
@@ -86,7 +88,8 @@ Refresh it after a module install or an Odoo upgrade with `odoo cache clear`.
 - Errors: one JSON object on stderr, `{"error": {"code": ..., "message": ..., "odoo": {...}}}`.
 - Warnings and write logs: one JSON object per line on stderr.
 - Exit codes: `0` ok, `1` Odoo raised, `2` bad usage, `3` connection or authentication,
-  `4` refused by a guard (writes disabled, missing `--yes`, sensitive model).
+  `4` refused by a guard (writes disabled, missing `--yes`, sensitive model), `5` the query
+  was repaired to make it run, so the rows answer a wider question than the one you asked.
 - Values of fields named like `password`, `api_key`, `secret` are replaced by `[redacted]`
   unless `--no-redact`.
 
@@ -108,7 +111,9 @@ odoo cache path|list|clear                  the schema cache
 `MODEL` accepts an alias on every read command. `odoo group` runs `read_group`, so you
 get counts and totals per group without pulling the records:
 `odoo group invoices -w overdue --by partner_id --sum amount_residual`.
-Grouping keys accept a date granularity: `--by invoice_date:month`.
+Grouping keys accept a date granularity: `--by invoice_date:month`. On Odoo 20 it runs
+`formatted_read_group` and passes its answer through: totals are keyed `amount_residual:sum`
+instead of `amount_residual`, and each group's filter is `__extra_domain`.
 
 Conditions (`-w`, repeatable, AND-ed together, combined with `--domain`):
 
@@ -166,10 +171,11 @@ One2many and many2many fields take Odoo commands, written as JSON in `-v` or `--
 5. Many2one values come back as `[id, name]`. Filter on them with the id
    (`-w partner_id=42`) or through a related field (`-w partner_id.name~acme`).
 6. Dates are strings, `YYYY-MM-DD` or `YYYY-MM-DD HH:MM:SS` in UTC.
-7. Field names drift between Odoo 17, 18 and 19 (for example `account.account.company_id`
+7. Field names drift between Odoo 15 and 20 (for example `account.account.company_id`
    became `company_ids`). If a field is rejected, `odoo fields` is the truth.
-   `--lenient-fields` on `search` removes rejected fields and retries, with a warning on
-   stderr; only use it for exploration, never in a script that relies on the result.
+   `--lenient-fields` on `search` removes rejected fields and retries. It prints the rows and
+   then exits 5, because they answer a wider question than the one you asked. Use it to
+   explore; if you keep it in a script, check the exit code.
 8. Never guess a model name: `odoo alias`, then `odoo models --like invoice`. A dotless
    name close to a known alias is reported as a typo instead of being sent.
 9. Sensitive models (`ir.config_parameter`, `ir.mail_server`, `res.users.apikeys`, `ir.cron`,

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/src/odoocli/__init__.py

@@ -7,8 +7,10 @@ from odoocli.errors import (
     OdooAuthError,
     OdooConnectionError,
     OdooError,
+    OdooFieldMissingError,
     OdooMissingError,
     OdooRefusedError,
+    OdooRepairedError,
     OdooUsageError,
     OdooValidationError,
 )
@@ -21,8 +23,10 @@ __all__ = [
     "OdooClient",
     "OdooConnectionError",
     "OdooError",
+    "OdooFieldMissingError",
     "OdooMissingError",
     "OdooRefusedError",
+    "OdooRepairedError",
     "OdooUsageError",
     "OdooValidationError",
     "__version__",

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/src/odoocli/_version.py

@@ -1,3 +1,3 @@
 """Single source of the package version (kept import-free to avoid cycles)."""
 
-__version__ = "0.4.0"
+__version__ = "0.6.0"

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/src/odoocli/aliases.py

@@ -10,14 +10,20 @@ Both are pure sugar: they expand to an ordinary domain before anything is sent,
 they never change the shape of the result, and the technical model name always
 keeps working. Aliases apply to read commands only — writing through a name
 that hides a filter would be a good way to create the wrong record.
+
+The tables below ship with the tool. A profile file may add its own under
+``[aliases]`` and ``[presets]``; a user entry with a built-in name replaces it,
+because the tenant knows its own vocabulary better than this file does.
 """
 
 from __future__ import annotations
 
 import difflib
+import tomllib
 from collections.abc import Mapping
 from dataclasses import dataclass, field
 from datetime import date
+from pathlib import Path
 from typing import Any
 
 # Dynamic operands, substituted when a preset is expanded.
@@ -141,7 +147,112 @@ PRESETS: Mapping[str, Preset] = {
 }
 
 
-# ----- lookup -----
+# ----- registry -----
+
+
+@dataclass(frozen=True, slots=True)
+class Registry:
+    """The alias and preset tables in force for one invocation."""
+
+    aliases: Mapping[str, Alias]
+    presets: Mapping[str, Preset]
+
+    def resolve(self, name: str) -> Alias | None:
+        return self.aliases.get(name.strip().lower())
+
+    def resolve_model(self, name: str) -> str:
+        alias = self.resolve(name)
+        return alias.model if alias else name
+
+    def suggest(self, name: str) -> list[str]:
+        return difflib.get_close_matches(
+            name.strip().lower(), sorted(self.aliases), n=3, cutoff=0.6
+        )
+
+    def preset(self, model: str, name: str) -> Preset | None:
+        found = self.presets.get(name.strip().lower())
+        if found is None or (found.models and model not in found.models):
+            return None
+        return found
+
+    def presets_for(self, model: str | None) -> dict[str, Preset]:
+        if model is None:
+            return dict(self.presets)
+        return {n: p for n, p in self.presets.items() if not p.models or model in p.models}
+
+    def expand(self, model: str, token: str, today: date | None = None) -> list[list[Any]] | None:
+        found = self.preset(model, token)
+        return None if found is None else found.clauses(today or date.today())
+
+    def rows(self) -> list[dict[str, Any]]:
+        """Table-friendly listing, marking which entries came from the config file."""
+        return [
+            {
+                "alias": name,
+                "model": alias.model,
+                "filter": ", ".join(f"{f} {o} {v}" for f, o, v in alias.domain),
+                "presets": ", ".join(sorted(self.presets_for(alias.model))),
+                "source": "config" if name not in ALIASES or ALIASES[name] != alias else "builtin",
+                "help": alias.help,
+            }
+            for name, alias in sorted(self.aliases.items())
+        ]
+
+
+BUILTIN = Registry(ALIASES, PRESETS)
+
+
+def _leaves(raw: Any, where: str) -> tuple[tuple[str, str, Any], ...]:
+    if raw is None:
+        return ()
+    if not isinstance(raw, list):
+        raise ValueError(f"{where}: 'domain' must be a list of [field, operator, value]")
+    out: list[tuple[str, str, Any]] = []
+    for leaf in raw:
+        if not isinstance(leaf, list | tuple) or len(leaf) != 3 or not isinstance(leaf[0], str):
+            raise ValueError(
+                f"{where}: every clause must be [field, operator, value], got {leaf!r}"
+            )
+        out.append((str(leaf[0]), str(leaf[1]), leaf[2]))
+    return tuple(out)
+
+
+def from_config(path: Path) -> Registry:
+    """Merge ``[aliases]`` and ``[presets]`` from a profile file over the built-in tables.
+
+    A malformed entry raises rather than being skipped: a filter the caller believes is
+    applied and is not is exactly the failure this whole mechanism exists to avoid.
+    """
+    try:
+        raw = tomllib.loads(path.read_text(encoding="utf-8"))
+    except (OSError, ValueError):
+        return BUILTIN
+    user_aliases = dict(ALIASES)
+    for name, table in (raw.get("aliases") or {}).items():
+        if not isinstance(table, dict):
+            continue
+        model = table.get("model")
+        if not isinstance(model, str) or "." not in model:
+            raise ValueError(f"alias '{name}': 'model' must be a technical Odoo model name")
+        user_aliases[name.strip().lower()] = Alias(
+            model=model,
+            domain=_leaves(table.get("domain"), f"alias '{name}'"),
+            help=str(table.get("help", "")),
+        )
+    user_presets = dict(PRESETS)
+    for name, table in (raw.get("presets") or {}).items():
+        if not isinstance(table, dict):
+            continue
+        models = table.get("models") or []
+        user_presets[name.strip().lower()] = Preset(
+            domain=_leaves(table.get("domain"), f"preset '{name}'"),
+            help=str(table.get("help", "")),
+            models=tuple(str(m) for m in models) if isinstance(models, list) else (),
+        )
+    return Registry(user_aliases, user_presets)
+
+
+# ----- lookup (the built-in tables) -----
 
 
 def resolve(name: str) -> Alias | None:

{odoo_agent_cli-0.4.0 → odoo_agent_cli-0.6.0}/src/odoocli/cli/alias_cmd.py

@@ -6,8 +6,7 @@ from typing import Any
 
 import typer
 
-from odoocli import aliases
-from odoocli.cli.app import app, emit
+from odoocli.cli.app import app, emit, session
 
 
 @app.command("alias")
@@ -21,8 +20,9 @@ def alias_cmd(
     ),
 ) -> None:
     """Model aliases ('invoices' -> account.move) and presets ('-w overdue'). Offline."""
+    registry = session(ctx).registry()
     if presets:
-        model = aliases.resolve_model(name) if name else None
+        model = registry.resolve_model(name) if name else None
         rows: list[dict[str, Any]] = [
             {
                 "preset": preset_name,
@@ -30,11 +30,11 @@ def alias_cmd(
                 "domain": " and ".join(f"{f} {o} {v}" for f, o, v in preset.domain),
                 "help": preset.help,
             }
-            for preset_name, preset in sorted(aliases.presets_for(model).items())
+            for preset_name, preset in sorted(registry.presets_for(model).items())
         ]
         emit(ctx, rows)
         return
-    listing = aliases.alias_rows()
+    listing = registry.rows()
     if name:
         needle = name.lower()
         listing = [r for r in listing if needle in r["alias"] or needle in r["model"]]