Reuse a container or isolate a task

Every new coding session gets its own working directory and Git branch. Reuse a compatible container to reduce overhead, or create another for separate processes and resources. Different users always get separate containers.

How it works

  1. Choose the container

    Reuse a compatible container for your own sessions or start another. Different users always run in separate containers.

  2. Work on an independent branch

    Each new coding session gets separate working files and a Git index. It starts from the selected source commit and available uncommitted inputs; existing sessions keep their original directories.

  3. Keep and combine the results

    Resume and Thaw keep the same working directory. Merge or cherry-pick completed changes explicitly; sharing a container does not merge branches.

  4. Start from your devcontainer.json

    devctrl reads a supported subset of devcontainer.json: environment, user, init, sanitized run arguments and lifecycle commands. The Host creates the container itself through the ⁠Docker API, without the Dev Container CLI. Compose configurations and other unsupported options have no effect.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

ProjectsREAL UI

Loading the recorded terminal…

Walkthrough paused
YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.