Variables
Key-value environment variables injected into workspaces at boot.- Scoped globally, per repository, or per repository set
- Values are encrypted at rest
- Paste
.env-formatted blocks to batch add
Files
Configuration files placed inside workspaces.- Place files at
~/...(home directory) or~/workspaces/...(alongside cloned repos) - Scoped globally, per repository, or per repository set
- Max file size: 64 KB
- Contents are encrypted at rest
Skills
Install skills from the skills.sh directory into your workspaces.- Skills are installed globally during workspace pre-warming
- Search by name or slug to find available skills
- Enable or disable per organization
Warm Hooks
Warm hooks are available on Team and Enterprise plans.
How it works
- Configure — set up warm hooks at the organization or repository level.
- Pre-warm — Replicas runs the hook commands inside a fresh workspace and snapshots the result.
- Pool — a set of pre-warmed workspaces is maintained per repository or repository set.
- Provision — when a user creates a workspace, Replicas assigns one from the warm pool.
- Boot — the workspace’s start hook (if any) still runs for session-specific initialization.
Organization-level warm hooks
Configure from Settings → Warm Hooks:- Add shell commands to run during pre-warming (e.g., dependency installs, asset builds).
- Set a timeout per command (default 5 minutes, max 15 minutes).
- Choose which repositories or repository sets the hook applies to.
Repository-level warm hooks
Add awarmHook field to your replicas.json file:
Execution order
| Phase | Hook | When it runs |
|---|---|---|
| Pre-warm | Organization warm hook | During pool creation |
| Pre-warm | Repository warm hook (warmHook) | During pool creation, after org hook |
| Boot | Start hook (startHook) | When the workspace is assigned to a user |
Warm pools
Warm pools keep pre-warmed workspaces ready per repository or repository set.- Default pool size is 5. Contact founders@replicas.dev to increase.
- Replicas periodically reconciles pool levels.
- Pools are automatically invalidated when environment variables or files change.