Versioning and Lifecycle
Version control for agents
You'll be able to
- Save, name, and roll back versions of an agent as it changes
- Use a draft-to-published lifecycle to keep risky edits out of production
Read first
Day 6 Lab
**Status: Generally available — Glean’s Agent Builder and its core features (scheduled triggers, versioning, native actions) are GA. Only the *content triggers* trigger type remains Beta; confirm availability in your tenant.**
- Take your working agent and save it as a named version — note what changed and why.
- Make an edit in a draft, leaving the published version running untouched.
- Publish the draft, then compare the two versions to confirm the diff is what you meant.
- Practice a rollback: restore the prior version and verify the schedule still points at it.
- Write a one-line changelog note so the next person knows what each version did.
Working Example: An Agent's Version Lifecycle
Per Glean's Fall '25 launch announcement, agents carry a version lifecycle — save, publish, and roll back as the agent evolves. Verified against fall25_launch.
Agent: "Morning #incidents digest"
v1 published baseline: read -> summarize -> DM (running on schedule)
v2 draft added a "no new posts -> send nothing" guard
v3 published promoted v2 after review (now running)
...v3 starts over-trimming the digest...
rollback restore v1 as published; investigate v3 in a draft
Changelog:
v1 baseline | v2 add empty-run guard | v3 promote v2 | rollback -> v1 (regression)Versioning makes change *accountable*: every edit is a named, comparable, reversible step rather than an in-place mutation no one can audit. Rollback to a known-good version is a GOVERN control because it bounds blast radius — a bad change is recoverable by policy, not by luck. This lifecycle is an announced feature; confirm versioning and rollback are GA in your tenant before you treat them as a safety net.
Check for understanding
Why does rollback to a known-good version count as a governance control, not just a convenience?
Check yourself
1. In Glean's vibe-code agent builder, how do you start building an agent?
2. The vibe-code builder, 100+ native actions, scheduled triggers, looping, and versioning are best described as...
3. Before adding a native WRITE action (e.g., update a Salesforce case) to an agent step, what should you check?
4. An agent runs unattended on a daily schedule. Which guard most directly keeps a bad run from compounding?
5. Why does rolling an agent back to a known-good version count as a governance control?
In 10 seconds
“Glean's Fall '25 launch announced agent versioning: save named versions, publish a draft, roll back a bad change. That lifecycle is how an agent stays accountable as it evolves.”
Power-User Capstone 2: Ship a Scheduled Agent