Documentation Index
Fetch the complete documentation index at: https://docs.joggr.ai/llms.txt
Use this file to discover all available pages before exploring further.
Container sandboxes are not yet available. Follow the roadmap
→
Why Containers
Local worktrees share your host environment. That’s fast and convenient, but it means an agent has access to everything on your machine — your SSH keys, your other projects, your system tools. For most tasks that’s fine. For some it’s not:- Untrusted or experimental agents that might modify files outside the repo
- Reproducible builds that need a clean, consistent environment
- Dependency isolation when testing against different Node/Python/system versions
- Security-sensitive work where agents shouldn’t access host credentials
What You Get
Full Isolation
Each sandbox runs in its own container with scoped filesystem and network access. Agents can’t
reach your host environment.
OCI Compatible
Works with Docker and Podman. Uses the OCI container standard — bring your own runtime.
Custom Images & Dockerfiles
Use a public base image for quick setup or point to a Dockerfile for custom build steps. Same
Dockerfile works for local containers and remote sandboxes.
Resource Limits
Set CPU, memory, and disk limits per sandbox to prevent runaway processes.
How It Works
Build
Joggr builds a container from your configured
image or dockerfile. Your project is mounted
into the container automatically.Configure
Ports, volumes, environment variables, and resource limits are applied from your
sandbox.container config.Execute
The agent runs inside the container with scoped filesystem and network access. Changes to your
project are synced back. Detach anytime — the container keeps running in the background.