AI Docs Bundle
Join Our Community Slack Contact

Chainguard Workspaces

Set up Chainguard Checks and Chainguard Workspaces
How Chainguard Checks and Chainguard Workspaces work together, and how to sign up for both with chainctl develop init and give teammates access.
Chainguard Workspaces overview
Learn how Chainguard Workspaces runs your repository and your coding agents in a remote microVM session without putting your credentials in the session.
How Chainguard Checks and Chainguard Workspaces isolate your code
The security model of Chainguard Checks and Chainguard Workspaces in one place: microVM isolation, credentials kept outside the VM, network allowlists, trust rings, and the run and session lifecycles.
Get started with Chainguard Workspaces
Sign up for Chainguard Workspaces, open your first development session, and learn how to detach from it and return.
Manage Chainguard Workspaces sessions
Open, detach from, return to, list, rename, and delete Chainguard Workspaces sessions, run several terminals in one, and keep a session running while you're away.
Configure a Chainguard Workspaces session's environment
Choose the packages, tools, and network access a Chainguard Workspaces session gets, from your repository's .chainguard/develop.yaml or .chainguard/ci.yaml file, a file of your own, or the default environment.
Manage Chainguard Workspaces session credentials
Learn how a Chainguard Workspaces session reaches GitHub, Claude, and Chainguard without holding credentials, and how to approve, review, and revoke what it can reach.