Changelog
What changed in VariantGate, newest first: new features, changes to how approvals and rules work, and fixes.
Follow it in a feed reader: Atom feed
Signed webhooks to your own systems
Pro and up can send signed webhooks to their own systems: a serverless agent, n8n, a workflow engine or an internal tool hears when a request waits, is approved, denied, expires or is withdrawn, without polling. Add up to five under Settings, choose the events, and check each message with its signing secret, the Standard Webhooks way; both SDKs now have a helper for it. Deliveries that fail are tried again for about ten hours, and Settings shows the latest ones. Only public https addresses are accepted.
See WebhooksChange roles, and delete a workspace or your account
Owners can make anyone an owner or a member under People, and a workspace always keeps at least one owner. Under Settings, Deleting, an owner can delete a workspace with everything in it, and anyone can delete their own account, by typing its name or email address. A paid plan ends first, with a final invoice for what was used and not billed yet. Workspaces you share keep what you did there in their sealed records.
See TeamsA weekly summary by email
Every Monday morning, a short email per workspace about the week before: how many requests your agents made and how they ended, next to the week before, the median time to a decision, the busiest agents, what is waiting now and, for owners, rules worth writing. Owners get it unless they turn it off and members choose to, under Settings; one click in the email turns it off. It is on every plan, Free included.
See NotificationsTry your rules before an agent does
Under Rules, pick a key, type an action and an amount, and see at once what that request would get right now: allowed, denied, refused or waiting for a person, which rule decides and why, who it would go to, and how much of a budget is left. It goes through the same checks as a real request, from the key and this month's requests to the rules, budgets and pauses, but nothing is stored, nobody is told, and it counts toward nothing. Available on every plan.
See RulesEach agent sees only its own requests
An agent key now reads only the requests it made. Before, another key in the same workspace could read a request, details included, if it knew the request's id; now it gets the same not-found answer as for a request that does not exist. The SDKs also say when only the asking agent is paused, rather than every agent.
See SecurityDetails you can read: messages, code, diffs and tables
Details now show the way an agent sent them. A message keeps its line breaks, SQL and commands are set in a fixed-width font, a code change shows its added and removed lines in green and red, order lines become a small table, and nested facts are indented. Web addresses become links that read as the full address. Long text starts collapsed with a button to show all of it, in the inbox, on the page a Slack or email link opens, and on the record.
See RequestsSearch the docs
Search the docs, guides, articles, glossary and API from any public page. Choose Search in the header or the docs menu, or press ⌘K, Ctrl K or /, and type: each word finds the pages, headings, terms and endpoints it starts a word in. Arrow keys move through the results and Enter opens one.
See QuickstartEvery plan, side by side
The pricing page now compares every plan side by side, row by row: requests, agents and people, how you decide, rules, the record and company needs. It also answers the billing questions people ask before they buy: who counts as a person, when paying per request is the better choice, and what happens when you move to a smaller plan or cancel.
See PricingTry a request the moment you make a key
Right after you create an agent key, one click sends a test request with it, the way an agent would. It waits in the inbox like any other request, so you can approve or deny your first one before connecting Claude Code, Codex or your own code.
See Agent keys
Plans that include what they list
Each plan now includes exactly what the pricing page lists: rules, amount limits, budgets and editing a request before approving it from Pro; inviting people and two-person approval from Team; routing, reports per agent and audit exports from Business. Moving to a smaller plan never takes away what you set up: existing rules, people and routes keep working, and only adding new ones needs the plan again. Paying per request on Team and Business now starts at €15 and €39 a month, and a month without requests costs nothing.
See Limits and errors
Pay per request on Team and Business, and an Enterprise page
Team and Business can now be paid per request, €0.05 and €0.12, instead of per person: you pay for what your agents ask, whatever the size of the team. A monthly cap, 10,000 requests to start and yours to change in Settings, keeps a runaway agent from running up a bill, and Settings shows what this month costs so far. Enterprise has its own page, with what it adds and a short form to tell us what your company needs.
See Limits and errorsA suggested workspace name, and renaming
Creating a workspace now suggests a name from your work email's domain, such as Northwind for maya@northwind.example, and leaves the field empty for personal addresses like Gmail. Owners can rename a workspace under Settings at any time; the rename is kept in Record under Workspace changes.
See Teams
A faster inbox, and push notifications
Work the inbox from the keyboard: j and k to move, a to approve, d to deny, and ? for the rest. Filter by agent, action or amount, and bookmark the view. Turn on push in Settings to get a notification on your phone or desktop even with the tab closed; on an iPhone, add the site to the home screen first.
See NotificationsGuides for risky actions, and new articles
Six guides for risky kinds of action (refunds, production deploys, payments, bulk email and CRM changes, GDPR erasure, database migrations), each with a rule set and the agent's code. Five new articles, among them the EU AI Act's Article 14 and OWASP's Excessive Agency, and this changelog.
See GuidesAgent key limits, end dates, and a log of workspace changes
An owner can limit an agent key to some actions, such as deploy.*, and give it an end date. A request outside the key's actions is refused before anyone is told. Record now has a second view, Workspace changes: who created, paused or revoked keys, changed rules, paused the workspace, invited or removed people, or changed notifications or the plan, sealed like decisions.
See Agent keysInsights and rule suggestions
A new Insights section shows the last 7, 30 or 90 days against the period before: how long people take to decide, how much rules answer, what nobody answered in time, and the numbers per action and per person. When one agent keeps asking for the same thing and it is always approved, owners see the rule that would answer it.
See InsightsMicrosoft Teams and Discord
A workspace can announce waiting requests in Microsoft Teams or Discord instead of Slack, with the same Approve and Deny buttons. Only the services' own webhook addresses are accepted.
See NotificationsA clearer front page and a new logo
The front page lists every feature in five groups (connect, decide, rules, control, record) and shows screenshots retaken from the current app. A new logo, too: a solid block with a doorway cut out.
Self-hosted backups read the email settings again
The backup script stopped with a syntax error when the email sender in the settings file had a display name. The example settings now quote it, and a check catches an example that would break the backup again.
See Self-hostingBuy a plan from Settings
Owners pick Pro, Team or Business under Settings and pay through Stripe Checkout. Manage billing opens Stripe's portal for invoices, the card and plan changes. Team and Business count one seat per person in the workspace.
Single sign-on
People can sign in through their company's identity provider over SAML, such as Okta, Microsoft Entra ID or Google Workspace, with Sign in with SSO on the sign-in page.
See Single sign-onA self-hosting guide
Requirements, setup, settings, email, single sign-on, upgrades, backups and health checks for running VariantGate on your own server.
See Self-hostingA report per agent
Under Agents, a report per agent key over 30 days, 90 days or 12 months: how its requests ended, the share a rule decided, the median time a person took to decide, the outcomes it reported and the money approved. It downloads as CSV.
A record you can check for tampering
Every change to a request adds an entry to a hash chain kept per workspace. Verify recomputes the chain and names the first broken entry, and the chain downloads so anyone can check it without trusting the server.
See The recordSend what a rule catches to the right people
An always-ask rule can name who decides what it catches, such as refunds to the two people who handle them, and how long they have before anyone in the workspace may decide instead.
See RulesA Python SDK
The variantgate Python package has a client, a require_approval decorator and with block, and the same command line as the TypeScript package. Both packages install from this site until they are on npm and PyPI.
See SDK and command lineDocs for every integration
Setup pages for Claude Code, Codex, Cursor, VS Code, the Claude app, GitHub Actions, LangChain, the OpenAI Agents SDK, n8n and Zapier, plus an API reference built from the OpenAPI file, a security page and a glossary.
See IntegrationsApprove or deny from an email or Slack
Every member is emailed when a request waits for a person, with Approve and Deny links that each work once. The Slack message has the same two buttons, which ask the person to sign in first.
See NotificationsEdit a request before approving it
Reword a request or lower its amount before approving. The agent may then do only the approved version: the SDKs, the command line and the hooks refuse to run what was first asked.
See RequestsGreenlight is now VariantGate
The product is now VariantGate, at variantgate.com. The command is variantgate and it reads VARIANTGATE_KEY and VARIANTGATE_API_URL. Agent keys keep their gl_ prefix.
Budgets per day, week or month
An always-allow rule can approve up to a total per day, week (from Monday) or month, in UTC. Past it, a person decides until the period starts again.
See RulesSearch, browser notifications and the inbox on a phone
Search the record by summary, agent or action. Turn on notifications in a browser to hear about requests while the inbox is in the background. Add the inbox to a phone's home screen and it opens like an app.
See NotificationsTwo-person approval
An always-ask rule can need two or three different people to approve, such as payments above €1,000. One denial stops the request.
See Two-person approval for AI agent actionsPause one agent
Pause one agent key while the others keep working. Nothing it asks for is allowed until an owner resumes it, and its requests still arrive so you can see what it tried.
See Emergency stopRemember an answer from the inbox
Next to Approve and Deny, owners choose how long the answer stands: just this once, for an hour, for a day, or always. That writes a rule for exactly that action from exactly that agent key.
See RulesConnect your agent in minutes
A Connect an agent panel gives copy-ready steps for Claude Code, Codex, Cursor, VS Code and the Claude app. A TypeScript client, the variantgate command for scripts and CI, and hooks that put Claude Code and Codex tool calls through approval.
See IntegrationsWait for the answer, take a request back, report the outcome
Agents can hold a call open for up to 30 seconds until a person decides, withdraw a request when their plan changes, and report whether the approved action succeeded.
See Requests
Rules by amount
A request can state an amount and a currency, and a rule can carry a limit: allow up to it, or ask or deny above it. A request with no amount never gets past a limit.
See RulesSee which key a request came from
Every request shows the name of the key it was made with, next to the name the agent gave itself, in the inbox, the record, the export and Slack.
See RequestsDocs and articles
Docs with a page per concept, the first articles, and a product tour on the front page.
See QuickstartA reworked inbox
The workspace is split into Inbox, Record, Rules, Agents, People and Settings, with a countdown on each request, notes for the record and first steps for a new workspace.
Plans and usage
Each workspace is on a plan and Settings shows this month's usage. Free allows 100 requests a month and 2 active agent keys.
See Limits and errorsExport the record
Download what was decided or expired as a CSV file for an auditor or a spreadsheet.
See The recordSlack announcements
Give a workspace a Slack incoming webhook, and every request that needs a person is announced in that channel.
See NotificationsA rate limit per agent key
One agent key may make 600 calls a minute, so a runaway agent cannot flood the service.
See Limits and errorsThe emergency stop
Any member can pause every agent in the workspace with one switch. Nothing is allowed until an owner resumes.
See Emergency stopStanding rules
Owners answer in advance: always allow, never allow or always ask, for one action or a family such as email.*. The most cautious rule wins.
See RulesAn MCP server
Agents that speak MCP ask with a request_approval tool and read the answer with check_approval. A skill teaches them when to ask.
See MCP server
Workspaces, sign-in and agent keys
People sign in with an emailed link and create a workspace. Agents ask with keys made for that workspace, and a key can never approve its own request.
See Quickstart