Prior search
What's the problem
Summary
It would be useful to have container/VM/sandbox management a native part of Paseo, so someone can easily spin up a reproducible environment with Paseo and any agents installed automatically. Also, some services might have heavy resource requirements where it's best to have separate containers/resources.
Motivation
Today, getting Paseo running in a fresh environment requires manual creation of the instance/container, Paseo installation and daemon setup. This adds friction.
What would solve it
Ideal world
- Cloud sandbox API — a
paseo sandbox create command that provisions a remote environment with Paseo + agents already wired up on Kubernetes, various clouds or sandbox providers
- Simple UI button that creates a sandbox with Paseo all setup
- Docker image — publish an official
ghcr.io/getpaseo/paseo image with the daemon and CLI pre-installed
- Devcontainer / Codespaces feature — a
devcontainer-feature.json that installs Paseo into any devcontainer
- Configurable image (if the user wants to build an image with other tools installed)
Having sandboxes native to the CLI and API so agents can also create more sandboxes natively. We could also have an option when creating a new agent whether to put it in an existing or new sandbox.
Alternatives you considered
I've already built a Docker image with Claude, Codex and Paseo and have used Kubernetes to spin these up. I also built a lightweight CLI manage this. Would be great if could be a native Paseo feature, so I could do it on mobile/web as well.
Prior search
What's the problem
Summary
It would be useful to have container/VM/sandbox management a native part of Paseo, so someone can easily spin up a reproducible environment with Paseo and any agents installed automatically. Also, some services might have heavy resource requirements where it's best to have separate containers/resources.
Motivation
Today, getting Paseo running in a fresh environment requires manual creation of the instance/container, Paseo installation and daemon setup. This adds friction.
What would solve it
Ideal world
paseo sandbox createcommand that provisions a remote environment with Paseo + agents already wired up on Kubernetes, various clouds or sandbox providersghcr.io/getpaseo/paseoimage with the daemon and CLI pre-installeddevcontainer-feature.jsonthat installs Paseo into any devcontainerHaving sandboxes native to the CLI and API so agents can also create more sandboxes natively. We could also have an option when creating a new agent whether to put it in an existing or new sandbox.
Alternatives you considered
I've already built a Docker image with Claude, Codex and Paseo and have used Kubernetes to spin these up. I also built a lightweight CLI manage this. Would be great if could be a native Paseo feature, so I could do it on mobile/web as well.