Changelog · shipping in public
Shipping in public. Follow along on the blog.
Approve or deny a pending action straight from Slack. Each org can now wire its own destinations in Settings → Notifications: a Slack incoming webhook, or a signed webhook (HMAC-SHA256, timestamped) that delivers approval.requested events to your own systems.
Wrap your Vercel AI SDK tools once and every tool call goes through Arc for an allow / ask / block decision before execute runs. Ask and block come back as typed outcomes in the agent loop; the adapter never auto-approves and fails closed.
Invocations, decisions, approvals, and blocks, streaming into the console as they happen — the audit trail live, not after the fact.
A checklist in the console walks a new org from zero to first guarded action: register an app, sync actions, mint an agent token, fire a test invocation.
The CLI now speaks machine: --json output on commands and a new arc setup-prompt that emits a paste-into-your-agent setup brief, paired with an AI setup page in the docs. Point an agent at it and it can wire itself into Arc.
examples/supabase-guard receives Arc's signed approval webhooks into a Supabase table — pending approvals next to your own data — and shows an agent mutation guarded by Arc before it touches the database.
The Arc SDK + CLI (npm install @geostack/arc, bin: arc) and the MCP transport adapter (@geostack/arc-mcp-adapter, bin: arc-mcp-adapter) are published. Install, point the CLI at a local Arc server, and guard your first action in five minutes.
Set a budget per agent and Arc blocks before a runaway loop blows past it — counting cost across every action, not just one. The primitive behind the whole product.
Every attempt, approval, and block is recorded in a tamper-evident log you can read and export.
Expose Arc-guarded actions to any MCP-speaking agent (Claude Desktop, Cursor) with no code change.
Want the longer story behind each release? Read the blog.
