When you approve a deployment, what you actually want to know is simple: does this still match the current state of infrastructure? In a team that ships continuously, main doesn't hold still — a plan that was accurate the moment a PR merged can be stale by lunch if someone else's change landed in between. Up to now, approving meant trusting a plan you couldn't see, or re-running one by hand somewhere else first.

The Approvals dashboard now gives you that plan directly on the row, and the ability to refresh it before you commit. If a plan already ran for the exact commit under review, you get View Plan with its age. If it hasn't run yet — or you just want a current read against main — Run Plan dispatches one on demand, pinned to that precise commit so the plan you review and the commit that gets applied are guaranteed to match. A running plan reflects that in real time with a link to live logs, and refreshing stays disabled until the new run actually lands rather than re-enabling the instant the dispatch request is sent.

If there's no plan actually available to view, View Plan shows disabled with an explanation instead of opening a run with nothing to show — and Refresh Plan is right there to dispatch a new one.

Driving approvals through the Atmos Pro MCP server gets the same information: get_approval and list_approvals return a plan field on every apply-phase approval — the workflow run, its age, and whether it's stale — without a second lookup. An agent can answer "what does this approval change, and is that still current?" directly from the approval record, then call the new dispatch_approval_plan tool to trigger a fresh plan against the same commit before recommending approval, rather than trusting a stale one.