Lifecycle
Workspaces move through three states:| State | Description |
|---|---|
| Booting | VM starting, cloning repo, installing dependencies |
| Active | Ready for messages, agent working |
| Sleeping | Paused, no charges accrue |
What Runs Inside
Each workspace runs the Replicas Engine on port 3737, which:- Manages Claude Code and Codex agent sessions
- Queues messages when agents are busy
- Handles git operations (branch creation, commits)
- Refreshes authentication tokens automatically
- Supports Docker for running containerized development services inside the workspace
Collaboration and Review
- Create multiple chats per workspace to split workstreams and keep context organized.
- Use the built-in Diff Viewer to inspect pending code changes without leaving the dashboard.
- Use the Files view to browse workspace files directly in the dashboard.
- Share workspaces with teammates so they appear in the “Shared” sidebar view. Sharing controls sidebar visibility. All organization members already have full access to all workspaces.
- Team Workspaces view shows dashboard workspaces created by other organization members, with a “team” badge and creator tooltip. This lets you discover teammates’ workspaces without requiring an explicit share.
Repository Targeting
Workspaces can run against one repository or multiple repositories.- Select individual repositories during workspace creation.
- Use Repository Sets to save common multi-repository combinations and reuse them quickly.
Environment Configuration
Configure workspace environment variables and files in dashboard settings:- Global (all workspaces)
- Per repository
- Per repository set
Warm Pools
Pre-warm workspaces by running setup scripts ahead of time, so new workspaces provision instantly from a ready pool. Configure warm hooks at the organization level or per repository viareplicas.json or replicas.yaml. See Environments for details.