{"version":"2.1.224","anchor":"agent-versions-are-sequential-integers-not-timestamps","canonical_anchor":"agent-versions-are-sequential-integers-not-timestamps","heading":"Agent versions are sequential integers, not timestamps","tier":"internal","area":"Agent SDK Docs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/agent-versions-are-sequential-integers-not-timestamps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Agent versions are sequential integers, not timestamps\n\nAgent versions are documented as counting up from 1, not timestamps.\n\n**What**\n\nThe docs previously said each agent update produced a version numbered with a timestamp, and gave a timestamp example. They now say versions start at 1 and increment by one on each update.\n\n**Details**\n\n- Also tightened: `effort` is the only field exempt from full replacement when you supply a `model` object, and supplying `model` without `inference_geo` clears any pinned geography.\n\n**Evidence**\n\n`a sequential integer, starting at 1 and incrementing on each update`\n\n- Area: Agent SDK Docs\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}