Your name is on the cron job - Snowflake's unattended agent runs, your default role, and a two-month record

Snowflake put CoCo automations into public preview on 21 August 2026: recurring, unattended coding-agent runs on a fixed schedule inside a managed sandbox. The governance detail is not the scheduler but the identity. A run does not use the role that was active when it was created - it starts on the user's default role with the default secondary roles activated, the agent task is owned by the user rather than a role, the EXECUTE AGENT TASK privilege sits on PUBLIC by default, and interactive tool approval is disabled for the duration of a run. Least-privilege discipline that lives in switching to a narrow role per session does not survive the transition to a schedule. The European consequence is a retention asymmetry: automation threads and run history are kept two months, while ACCOUNT_USAGE.ACCESS_HISTORY is kept one year, so the record of which SQL touched which column outlives the record of why an agent decided to run it by ten months. GDPR Article 5(2) requires the controller to be able to demonstrate compliance and Article 32(4) requires that anyone acting under the controller's authority process personal data only on instruction; after day sixty the instruction is gone and the surviving log names a human. The AI Act's own answer lands later - Article 26(6) sets an at-least-six-months floor on deployer logs for high-risk systems, and Regulation (EU) 2026/1744 moved Annex III to 2 December 2027. The automation is fine; the retention is the bug.

Post

Snowflake shipped scheduled, unattended coding-agent runs on 21 August. The interesting line is not the scheduler. It is whose privileges the run inherits.

CoCo automations turn a prompt into a recurring job: it executes in a Snowflake-managed sandbox, at most once an hour, and writes a thread of every message and tool call it made.

Three things in the documentation that matter more than the feature itself:

  1. It does not run as the role you had active when you created it. Each run starts on your user's default role, with your default secondary roles activated, and the agent task is owned by the user rather than by a role. If your least-privilege discipline lives in "switch to the narrow role for this session", the automation routes around it.

  2. EXECUTE AGENT TASK is granted to PUBLIC by default. Every user in the account can create one until an administrator changes that grant. Revoking it on the account from role PUBLIC is a one-line change, and it is Monday's change.

  3. Interactive tool permission prompts are disabled during a run. The docs say it plainly: do not schedule destructive or irreversible actions unless the prompt, the role privileges, the connected tools and the target objects are intentionally configured for that.

Now the European part. Automation threads and run history are retained for two months. ACCOUNT_USAGE.ACCESS_HISTORY is retained for one year. The record of which SQL touched which column outlives the record of why an agent decided to run it, by ten months.

GDPR Article 5(2) requires you to be able to demonstrate compliance. Article 32(4) requires that anyone acting under your authority processes personal data only on your instructions. After day sixty the instruction is gone and the surviving log names a human.

The AI Act's answer arrives later: Article 26(6) sets a six-month floor on deployer logs for high-risk systems, and the Digital Omnibus moved Annex III to 2 December 2027. Two months sits under a floor that is not load-bearing yet.

Export the threads. The record is the deliverable.

Which of your agents remembers less than your database does?

#AIAct #DSGVO #AgenticAI #DataGovernance #Snowflake

First comment

Sources.

Snowflake's own documentation for CoCo automations - identity, default role, PUBLIC grant, disabled approval prompts, two-month retention: https://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-automations

The release note that dates the public preview to 21 August 2026: https://docs.snowflake.com/en/release-notes/2026/other/2026-08-21-cortex-code-automations-preview

ACCOUNT_USAGE retention, where ACCESS_HISTORY is one year (Enterprise Edition or higher): https://docs.snowflake.com/en/sql-reference/account-usage

AI Act Article 26(6), the at-least-six-months floor on deployer logs: https://artificialintelligenceact.eu/article/26/

GDPR Article 32(4), processing only on the controller's instructions: https://www.privacy-regulation.eu/en/32.htm

One point cut for length: the two-month window is not only a compliance number, it is an incident-response number. GDPR Article 33 gives you 72 hours from awareness - but awareness of an agent's misstep often arrives from a downstream anomaly weeks later, and by then the thread that would explain the decision may already be outside retention. Whatever else you automate, automate the export.

Claims

Sources

Corrections

None. All ten claims verified against primary or named secondary sources on 2026-08-25.

AI disclosure

The video for this edition contains AI-generated media: the narration is a synthetic voice, the cover art is generated, and the brand ident is a generated video interpolated between two frames of this same render. The script, the claims and the source verification are human-authored and human-checked. Assets carry IPTC DigitalSourceType and C2PA Content Credentials.