Use `model: inherit` to Keep APC Agents Portable

Description and use

Using model: inherit in APC decouples agent roles from specific models, enhancing portability and simplifying configuration for diverse contributors.

Problem

Agent definitions often hard‑code a specific model, making the role non‑portable and tying contributors to a particular runtime or provider.

Outcome

Using model: inherit decouples agent roles from specific models, improving portability, reducing maintenance, and allowing contributors to use their own runtimes.

Workflow

• 1. Write agent frontmatter with model: inherit and required skills.
• 2. Commit the agent file to the repository.
• 3. Each contributor configures their APX runtime with their preferred provider and model.
• 4. When the agent runs, APX resolves the model by checking per‑call overrides, then the agent file (none), then the runtime’s active model routing.
• 5. If a forced model is needed, document the justification in the agent file and handle missing‑model scenarios in the runtime configuration.

Evidence

model: inherit is the better default for an APC agent unless a particular model is genuinely part of the project's contract.

Source

APX’s agent model resolution code treats inherit and an empty model field as no forced model.

Source