Getting Started¶
This guide walks you through installing Cloister and running your first sandboxed AI agent session.
Prerequisites¶
- Docker (or OrbStack on macOS) — Cloister runs containers on an isolated network
- A git repository — Cloister is designed for project-based workflows
Installation¶
Recommended: Install Script¶
This downloads the latest release and installs it to ~/.local/bin. If this directory isn't already in your PATH, the script will offer to add it to your shell configuration (bash, zsh, or fish).
To install a specific version:
Alternative: Build from Source¶
Requires Go 1.25+.
Or clone and build manually:
First-Time Setup¶
Before using Cloister, configure your AI agent credentials.
For Claude Code:
The setup wizard prompts for authentication method (OAuth token or API key).
For Codex CLI:
The setup wizard prompts for your OpenAI API key.
See Credentials for details on each method.
Your First Cloister¶
Navigate to any git repository and start a cloister:
What happens:
- The guardian proxy starts automatically (if not running)
- A container is created on an isolated Docker network
- Your project directory is mounted at
/work - You're dropped into a shell inside the container
Started cloister: my-app
Project: my-app (branch: main)
Token: cloister_abc123...
Attaching interactive shell...
cloister@container:/work$
Running Your Agent Inside the Cloister¶
Inside the cloister, your configured agent runs with permissions auto-approved — the sandbox provides the safety net.
Claude Code (default):
Codex CLI:
To use a different agent than your default, start with --agent:
Your agent can:
- Read and write files in /work (your project)
- Access allowlisted domains (AI APIs, package registries, docs)
- Request host commands via the approval UI
Monitoring Activity¶
Open http://localhost:9999 in your browser to: - See pending hostexec requests - Approve or deny commands
Exiting and Stopping¶
# Exit the shell (container keeps running)
cloister@container:/work$ exit
# Re-enter the running cloister
cloister start
# Stop and remove the cloister
cloister stop
When you exit the shell:
Next Steps¶
- Configuration — Customize allowlists and settings
- Working with Cloisters — Managing cloister lifecycle
- Host Commands — Using hostexec for git push, docker, etc.