Shell sessions in worker pools
Reserve a worker in a named profile. Run commands in one persistent shell, attach a terminal, and release the worker when finished.
Read the documentation โOne session, one shell
Stateful commands retain directory, exports, and shell variables. Parallel commands inherit the shell's latest directory and exported environment and run at the same time. A terminal can detach without ending the session.
Profiles shape the sandbox
Deploy worker profiles with different mounts and resources. Give selected workers a shared application folder, and keep other workers without that mount. In the two-pod topology, each profile has a separate worker Deployment and pod-level network boundary.
Output stays with the server
Workers stream stdout and stderr to the server over the authenticated dispatch socket. The server keeps local output files for HTTP range reads. Worker pods need no shared capture volume.
Start with the API
POST /api/v1/sessions
{"profile":"default","env":{"PATH":"/usr/bin:/bin"}}
POST /api/v1/sessions/{id}/commands
{"command":"echo hello","mode":"stateful"}
GET /api/v1/sessions/{id}/commands/{handle} (poll until completed)
GET /api/v1/sessions/{id}/commands/{handle}/stdout
DELETE /api/v1/sessions/{id}See the full API and deployment layouts.