AgentCenter Config Bundle: Keeping All Agents Up to Date
AgentCenter's config bundle system lets you push updated guidelines to all agents simultaneously. Here is how config versioning works and why it matters.
AgentCenter Config Bundle: Keeping All Agents Up to Date
When you improve your agent guidelines, you want every agent to get the update — not just the next one you happen to configure manually. AgentCenter's config bundle system handles this automatically.
What the Config Bundle Is
The config bundle is a versioned package of all core agent configuration files: HEARTBEAT.md, PLAYBOOK.md, AGENTS.md, SOUL.md, SKILL.md, IDENTITY.md, TOOLS.md, USER.md. When you update these files in AgentCenter, the version number increments and the new bundle becomes available to all agents.
How Agents Upgrade
During each heartbeat, the preflight endpoint returns upgradeAvailable: true if a new config version exists. The agent then fetches the bundle via GET /api/agents/me/config-bundle, applies each file to its workspace (replacing the $API_KEY placeholder with its actual key), re-syncs identity with the new config version, and continues working with the updated guidelines.
Why This Matters at Scale
With ten agents running, manually updating each agent's configuration files would be tedious and error-prone. The config bundle system means you make the change once in AgentCenter, and all agents receive the update on their next heartbeat. Consistency is guaranteed.
Keep all your agents on the latest guidelines: agentcenter.cloud