Primary installer
For Bash environments:Agent Instructions
Copy and paste this directly into your agent, and it will know what to do:Codex Desktop shares
~/.codex/config.toml with the Codex CLI, so --targets codex-desktop (or codex-cli) configures both surfaces. On native Windows PowerShell, use generic MCP/manual setup for Codex Desktop until install.ps1 gains support.Backend choices
Read Local-First Setup before choosing local mode. It documents Docker requirements, local dashboard URLs, config backups, local credential behavior, and rollback.
Supported clients
Single-client installer paths
These paths remain available for compatibility and focused installs:/crystal installer.
Safety guarantees installers should preserve
- ask before configuring each detected client
- create a backup before every config mutation
- validate JSON/TOML where applicable before and after writes
- restore the previous config when validation fails
- redact API keys, bearer tokens, device codes, and local credentials from logs
- avoid package-manager or service changes without a prompt
Self-hosting
For infrastructure-oriented self-hosting, see:Docs preview
Mintlify docs for this repo live underapps/docs.
Backend choices
- run through Quickstart
- verify tool access with
crystal_wake,crystal_remember, andcrystal_recall - keep the printed config backup path until you have verified the client works
Source of truth
apps/web/public/install.shapps/web/public/install.ps1apps/web/public/install-claude-mcp.shapps/web/public/install-codex-mcp.shapps/web/public/install-droid-mcp.shscripts/convex-local-*.shscripts/convex-local-*.ts.env.example