Deploying and Versioning Agents: Ship It Like Software

Agents are software, so ship them like software: pick a deployment topology on purpose, treat prompt + toolset + model + parameters + framework as one atomic version, evaluate a model upgrade like a database migration, and make rollback possible before you need it.

Content current as of 2026-09.

Lessons

1. Three shapes of a deployed agent
2. What a version even is for an agent
3. Model versioning: pinning, upgrades, and silent drift
4. Rollback: the state that will not go backwards
5. Checkpointing and replay: debugging runs you cannot reproduce