Sandbox
Give Claude a workspace that acts on your accounts.
Connect your Google Workspace, then ask Claude to triage your inbox, draft a deck, build a spreadsheet, or schedule a meeting. The Sandbox runs the command-line tools that do the work — inside an isolated container, on your instruction, never on a schedule.
Why this exists
You have Claude. Now what?
Chat models can't reach your inbox, your calendar, or your Drive. The Sandbox bridges them — without you copying and pasting screenshots back and forth.
You don't trust browser plug-ins with everything.
The Sandbox isn't a plug-in. It's a remote container, scoped to one task at a time, with OAuth tokens stored encrypted server-side and revoked on disconnect.
You don't want a Frankenstein of half-finished automations.
One AI you talk to in plain language. One sandbox it works inside. One bill at the end of the month. No Zaps, no Make, no glue.
How it works
Three steps from set-up to "hey, can you…"
- 01
Connect an account
OAuth into Google (more providers coming). You see the exact permissions Google asks for, before you authorise anything. Tokens are stored encrypted at rest.
- 02
Open Claude (or any MCP client)
Add the Zero BS AI Sandbox as an MCP server. One URL, one consent screen. Claude now sees the CLIs the Sandbox provides.
- 03
Ask, in plain English
"Draft a follow-up to everyone who replied to the launch email." "Find the spreadsheet from last Tuesday and update column C." "Move my 3pm to tomorrow morning." The Sandbox runs the CLI commands. You stay in the conversation.
Integrations
What you can wire up today
Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, Chat, Classroom, Tasks, Forms, Meet, Apps Script. Read and act.
Coming next
- Microsoft 365
- Slack
- Notion
- Linear
- GitHub
Want one we haven't built yet? Tell us and we'll prioritise.
Security & privacy
The boring stuff, on the record
Isolated containers
Each session runs in a single-tenant container. Nothing persists between tasks; the container is destroyed when you're done.
Encrypted at rest
OAuth tokens are encrypted before they touch our database. We can't read them; nor can anyone with stolen disk access.
You control consent
Google shows you the full permission list before you authorise. Revoke anytime from your Google account or our app — tokens are deleted server-side.
No training, no resale
Your data is fetched on demand to carry out the action you asked for. It isn't used for advertising, profiling, or sold to anyone. Ever.
Full detail in our Privacy Policy and Terms of Service.
Pricing
One subscription. The whole suite.
Sandbox usage is metered at 2 credits per minute of active container time.
200 credits/month
1,500 credits/month
6,000 credits/month
Stop pasting screenshots into Claude.
Connect your accounts once. Then talk to your work like it's a person who already has the context.
Open the Sandbox →