[chore] Rename agent config to agent template#4901
Conversation
Rename the agent authoring type from agent_config / AgentConfig to agent template, naming-layer only, mirroring the skill-template rename and the prompt-template precedent. No behavior change. - AgentConfig -> AgentTemplate, AgentConfigSchema -> AgentTemplateSchema - harness-config family: Pi/Harness/Claude/Agenta/Resolved AgentConfig -> ...AgentTemplate - catalog __ag_type__ / x-ag-type-ref "agent_config" -> "agent-template" - web AgentConfigControl -> AgentTemplateControl (+ layout, props, atoms) - services AGENT_CONFIG_SCHEMA / _DEFAULT_AGENT_CONFIG -> AGENT_TEMPLATE_* - env var AGENTA_AGENT_CONFIG_DIR -> AGENTA_AGENT_TEMPLATE_DIR (static on-file template dir) Kept: AgentaClientConfig, AgentaConfig (env), AgentRunnerConfigurationError. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
# Conflicts: # sdks/python/agenta/sdk/agents/dtos.py # sdks/python/oss/tests/pytest/unit/agents/skills/test_skills_e2e.py # sdks/python/oss/tests/pytest/unit/test_skill_template_catalog.py
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Context
The agent authoring type was named
agent_config/AgentConfigeverywhere, out of step with theprompt-template/PromptTemplatenaming and with the just-landedskill-templaterename. This renames the agent authoring vocabulary to "template", the same way #4900 did for skills. Naming layer only. No behavior change.Changes
Rename
agent configtoagent template(mirrorsprompt-templateandskill-template):AgentConfigtoAgentTemplate,AgentConfigSchematoAgentTemplateSchema.PiAgentConfig,HarnessAgentConfig,ClaudeAgentConfig,AgentaAgentConfig,ResolvedAgentConfigto...AgentTemplate.__ag_type__/x-ag-type-refgoes from"agent_config"to"agent-template"(dash, likeprompt-template).AgentConfigControltoAgentTemplateControl(file renamed), plusagentConfigLayouttoagentTemplateLayout,AGENT_CONFIG_LAYOUTStoAGENT_TEMPLATE_LAYOUTS, props and atoms.AGENT_CONFIG_SCHEMAtoAGENT_TEMPLATE_SCHEMA,_DEFAULT_AGENT_CONFIGto_DEFAULT_AGENT_TEMPLATE.AGENTA_AGENT_CONFIG_DIRtoAGENTA_AGENT_TEMPLATE_DIR(the directory holding the static on-file agent template). No back-compat.Deliberately kept (these are not the agent template):
AgentaClientConfig(the web Agenta API client config),AgentaConfig(the API env config), andAgentRunnerConfigurationError(the runner error).No back-compat: every renamed type is new on
big-agents, so this is a clean break with no aliases.This branch also merges
big-agents(which now carries the skill-template rename #4900). The merge combined both renames where they overlapped, so a skill referenced inside an agent template readsSkillTemplateinsideAgentTemplate, and the agent template'sskillsfield references theskill-templatecatalog type.Tests / notes
@agenta/entity-uiand@agenta/playgroundtsc clean; the skill control test passes post-merge (12/12).agent_config/AgentConfigresidual in live code (the only retained occurrence is intentional, the kept identifiers above), and zeroskill_configresidual from the merged branch.agent_configtoagent_templaterename does not touch the Fern-generated client; it still needs an OpenAPI regen alongside the skill-template one.