Most teams adding agents to a product already have row-level security in Postgres. Until now an agent s writes went around it: the gateway wrote back as its own role.
0.2.10 fixes that. Start a run with act_as, and its changes are written back as your end user s role, with their JWT claims:
Postgres then judges the agent s insert, update or delete exactly as it would the user s own. A row the policy hides or refuses stops the whole merge, and nothing is written. Superuser and BYPASSRLS roles are refused.
AI agents have already wiped production databases. Chronos Gateway is how you let yours write to real customer data anyway.
Every agent gets a run token, never your Postgres password, and a private copy of one customer's rows. Safe changes merge back in one transaction, every row checked against live data. Deletes and big changes stop and wait for a human, who approves in plain English. Your row-level security still decides what it can write.
Self-hosted. Free. Postgres 12-18, Supabase, Neon.
