Core build is deterministic and does not require AI-related settings.
AI-related keys (ai.*, skills.*) are internal/dev-only and are not part of released core behavior.
Recommended operational model:
- Use core build for normal development pipelines.
- Let external agents write/refine code in your workspace.
- Use CLI as the enforcement layer (
init/addtemplates,validate,build,package,deploy). - Treat embedded AI behavior as internal experimentation, not product contract.
Configuration is loaded in this precedence order (highest first):
--configargumentIDEMPIERE_CLI_CONFIGenvironment variable.idempiere-cli.yamlin current directory or parents~/.idempiere-cli.yaml
defaults:
vendor: "My Company Inc."
idempiereVersion: 13Only configure this section when explicitly evaluating internal AI/skills paths.
Recommended:
idempiere-cli config initManual:
idempiere-cli config set ai.provider anthropic
idempiere-cli config set ai.model claude-sonnet-4-20250514API key resolution order:
- environment variable (
ai.apiKeyEnv) - config file (
ai.apiKey)
skills.sources can be managed directly in YAML or through skills source commands.
Note:
config setworks for scalar keys (for exampleai.provider,defaults.vendor)- nested array entries like
skills.sources[0].nameare easier viaskills source add/remove
skills:
sources:
- name: official
url: https://github.com/hengsin/idempiere-skills.git
priority: 1
- name: local-overrides
path: /opt/mycompany/idempiere-skills
priority: 0Supported source layouts:
- multi-skill repository (multiple directories containing
SKILL.md) - single-skill repository (root
SKILL.md)
Use:
idempiere-cli skills list
idempiere-cli skills sync
idempiere-cli skills source list
idempiere-cli skills source add --name=official --url=https://github.com/hengsin/idempiere-skills.git --priority=1Use one config per workspace root:
workspace/
├── idempiere12/.idempiere-cli.yaml
└── idempiere13/.idempiere-cli.yaml
This keeps defaults version-specific without passing flags every time.