Sprites Backend
The Sprites backend runs AI agent sessions on sprites.dev, a managed container platform for development environments.
Requirements
- sprites.dev account
- API key configured
- Internet connectivity
Getting Started
1. Create Account
Sign up at sprites.dev and generate an API key.
2. Configure API Key
Store your API key:
echo "your-sprites-api-key" > ~/.clauderon/secrets/sprites_api_keychmod 600 ~/.clauderon/secrets/sprites_api_keyOr use environment variable:
export SPRITES_API_KEY="your-sprites-api-key"Or use 1Password:
[onepassword.credentials]sprites_api_key = "op://Work/Sprites/api-key"3. Create a Session
clauderon create --backend sprites \ --repo ~/project \ --prompt "Work on the feature"Configuration
Configure Sprites settings in ~/.clauderon/config.toml:
[sprites]# API key (or use secret file/env var)api_key = ""How It Works
When you create a Sprites session, clauderon:
- Creates a git worktree locally
- Syncs the worktree to a Sprites container
- Configures proxy settings for credential injection
- Starts the agent with your prompt
Features
Zero-Ops Containers
- Managed infrastructure
- Automatic scaling
- No Docker or Kubernetes required locally
Sync and Attach
Changes sync bidirectionally:
- Local changes sync to container
- Container changes sync back
Pre-configured Images
Sprites provides optimized images for common development scenarios.
Use Cases
Remote Development
Work on code without local resources:
clauderon create --backend sprites \ --repo ~/large-project \ --prompt "Analyze dependencies"Team Collaboration
Share sessions with team members via sprites.dev dashboard.
CI/CD Integration
Run sessions as part of your pipeline:
# Example GitHub Action- name: Run AI Analysis run: | clauderon create --backend sprites \ --repo . \ --prompt "Review PR changes" \ --printResource Limits
Configure container resources:
clauderon create --backend sprites \ --cpu-limit 4 \ --memory-limit 8g \ --repo ~/project \ --prompt "Heavy task"Monitoring
Session Status
clauderon listContainer Logs
View logs via the sprites.dev dashboard or:
clauderon attach <session-name>Networking
Sprites containers:
- Have internet access
- Route through clauderon proxy for credential injection
- Support custom network configurations via sprites.dev
Pricing
Sprites usage is billed based on:
- Container runtime
- Storage used
- Network transfer
Check sprites.dev for current pricing.
Advanced Features
Hibernation & Wake
Sprites containers support hibernation to reduce costs during idle periods. Hibernated containers:
- Preserve all state - Filesystem, environment, and configuration
- Reduce costs - Storage-only pricing (no compute charges)
- Resume quickly - Wake time typically 5-10 seconds
- Automatic wake - On attach or API access
Hibernating manually:
Sprites containers may hibernate automatically after an idle timeout. To manually wake a hibernated session:
# Wake via CLIclauderon wake <session-name>
# Or via APIcurl -X POST http://localhost:3030/api/sessions/{id}/wakeHibernation configuration:
Configure hibernation timeout in session creation:
clauderon create --backend sprites \ --hibernation-timeout 30m \ --repo ~/project \ --prompt "Long-running task"Timeout options:
5m,15m,30m- Short hibernation (for cost savings)1h,2h,6h- Medium hibernationnever- Disable automatic hibernation
Checking hibernation status:
# View session statusclauderon status <session-name># Shows "Hibernated" if container is suspendedIn Web UI or TUI, hibernated sessions display with a special status indicator.
Remote Clone Strategy
Unlike other backends, Sprites uses remote clones rather than local git worktrees:
How it works:
- Repository is cloned directly on sprites.dev servers
- No local disk usage for the clone
- Changes committed in container are pushed to remote
- Local worktree syncing is optional
Advantages:
- No local disk space consumed
- Faster session creation for large repositories
- Better for environments with limited local storage
Trade-offs:
- Network latency for git operations
- Initial clone time proportional to repository size
- May use more network bandwidth
Best for:
- Large monorepos (>1GB)
- Machines with limited disk space
- Remote-first development workflows
Not ideal for:
- Latency-sensitive git operations
- Offline development
- Frequent git operations (rebasing, cherry-picking)
Build Caching
Sprites supports build caching to speed up iterations:
Supported cache types:
- Cargo registry/git - For Rust projects
- npm/yarn/bun cache - For Node.js projects
- pip cache - For Python projects
- Docker layer caching - For Dockerfile builds
- Custom cache directories - Via configuration
Enabling build caching:
clauderon create --backend sprites \ --build-cache cargo,npm \ --repo ~/project \ --prompt "Build and test"Cache persistence:
- Caches persist across session recreates
- Shared across sessions in same project (configurable)
- Automatically cleaned after 30 days of inactivity
Cache configuration in Web UI:
When creating a session via Web UI:
- Expand “Advanced Options”
- Check “Enable build caching”
- Select cache types: Cargo, NPM, Pip, Docker
- Optionally set cache sharing scope (project-wide or session-specific)
Performance impact:
| Cache Type | First Build | Cached Build | Savings |
|---|---|---|---|
| Cargo | 5-10min | 30-60s | 80-90% |
| NPM | 2-5min | 10-30s | 70-85% |
| Docker layers | 3-8min | 30-90s | 60-80% |
Checkpoint Support
Status: ⚠️ Not yet implemented (sprites.dev API TODO)
When the checkpoint API becomes available, Sprites will support:
Session snapshots:
- Instant session state capture
- Point-in-time restoration
- Branch-point creation for experimentation
Planned usage:
# Create checkpointclauderon checkpoint create <session-name> "Before refactor"
# List checkpointsclauderon checkpoint list <session-name>
# Restore from checkpointclauderon checkpoint restore <session-name> <checkpoint-id>Future capabilities:
- Automatic checkpoints before risky operations
- Checkpoint-based branching (create session from checkpoint)
- Checkpoint sharing across team members
Current workaround:
Until checkpoints are implemented, use git commits for snapshots:
# In session, commit work before risky changesgit add .git commit -m "Checkpoint before refactor"
# If things go wrong, reset to commitgit reset --hard HEAD~1Model Override and Plan Mode
Model selection:
Sprites backend supports all available models. Specify during session creation:
clauderon create --backend sprites \ --model claude-opus-4-5 \ --repo ~/project \ --prompt "Complex refactor"See Model Selection Guide for choosing the right model.
Plan mode:
Plan mode works seamlessly with Sprites:
clauderon create --backend sprites \ --plan-mode \ --repo ~/project \ --prompt "Implement authentication system"The agent creates an implementation plan before executing. Network latency has minimal impact since planning is primarily AI computation.
Custom Container Images
Sprites supports custom container images via sprites.dev dashboard:
- Build and push image to sprites.dev registry
- Configure session to use custom image
- Session starts with your custom environment
Example use cases:
- Specific language versions (Python 3.11, Node 20)
- Pre-installed tools (databases, build tools)
- Custom development environments
- Company-specific base images
Limitations
- Requires internet connectivity
- Network latency vs local backends
- Usage costs apply
- Dependent on sprites.dev availability
Troubleshooting
Connection Failed
Check API key is valid:
clauderon config credentialsVerify internet connectivity.
Slow Performance
Consider:
- Using a closer region
- Reducing sync frequency
- Using Docker for latency-sensitive work
Session Not Starting
Check sprites.dev status page for service issues.
Verify your account has available capacity.
See Also
- Backends Comparison - Compare all backends
- Docker Backend - For local container sessions
- Troubleshooting - Common issues and solutions