Give Codex a browser signed in to your sites
Codex can change your code, but checking the result often means signing in somewhere: your app’s staging site, a vendor console, an internal tool. Clutchbox gives it a cloud computer whose Chrome is already signed in to the sites you choose.
Before you start
- Sign in to Clutchbox with Google. Personal use is free for 600 minutes of computer time a month.
- Add the Chrome extension and add the sites Codex needs. It syncs their sign-ins to your cloud computer in the background.
Connect Codex
The MCP server’s address is https://www.clutchbox.dev/api/mcp.
- In a terminal, run:
- Follow the browser prompt to sign in and allow the connection. If sign-in did not complete, run:
Try it
Ask Codex for something that needs one of your synced sites, for example:
Use Clutchbox to open staging, click through checkout, and report anything broken.
Use Clutchbox to read the failing build in our CI dashboard and fix the cause here.
With Clutchbox, open our vendor console and copy the webhook settings into config/webhooks.json.
Codex opens your cloud computer, already signed in. You can watch it work and take over from your account at any time.
What Codex can do there
- See the screen and use the mouse and keyboard on a full Linux desktop.
- Drive Chrome directly over the Chrome DevTools Protocol, as Playwright does.
- Run commands, and download the files it makes.
It acts on your real accounts, so sync only the sites a task needs. One agent uses the computer at a time, and you can disconnect any agent from your account immediately. How we keep your sign-ins safe.