Skip to content

Foreman kit · component 5 of 8

OffSite

src/components/kit/OffSite.astro: the New workspace dialog, the container yard with the vault and the property line, the four ship steps and the session panel. Every instance emits fm:kit events and listens for fm:kit:cmd.

Defaults, on cream

Try it · Illustrative

Send it off-site

Pick a workspace and a container, ship it, then close the laptop and see who keeps working.

New workspace · atlas

Workspace

Runs on

Sandbox
E2B
Size
vCPU
Starts from
A fresh clone, set up when it’s made
Sleeps after
20 min idle
Agent sign-in
Claude setup token

Your Claude subscription sign-in stays on this computer. In a sandbox Claude uses a setup token from claude setup-token, or an API key.

On E2B a session ends after 60 minutes. Foreman continues the turn when you’re around; with Foreman closed, the agent stops at the limit and the workspace sleeps.

Remote workspaces run on E2B. Experimental.

This computer

Foreman · atlasZzz

Vault

  • Provider keystays here
  • GitHub tokenstays here
  • Agent sign-instays here
Property line · provider keys stop here
  1. Clone from GitHub The repository comes from its GitHub remote. GitHub’s token goes in as that one command’s environment.
  2. Install the agent host Foreman puts its small agent host in the sandbox, so the agent can run there without your computer.
  3. Set up The install script and the repository’s setup steps run, as they would in a local worktree.
  4. Run The agent takes the turn in the sandbox. Your computer only coordinates.

Session · not started

Turn · waiting to ship

  1. Pick a workspace and a container, then Create. Closing the laptop quits Foreman: remote turns go on in their sandboxes until they finish or reach the session limit, and their chats catch up when you open Foreman again.

This month · no sandbox time yet

Dark night theme, Codex on Daytona

Night shift · Illustrative

Ship the night shift

Pick a workspace and a container, ship it, then close the laptop and see who keeps working.

New workspace · atlas

Workspace

Runs on

Sandbox
Daytona
Size
vCPU
Starts from
Base · built 2h ago
Sleeps after
20 min idle
Agent sign-in
Codex API key

Codex needs an API key in a sandbox. ChatGPT sign-in is off there for now.

Remote workspaces run on Daytona. Experimental.

This computer

Foreman · atlasZzz

Vault

  • Provider keystays here
  • GitHub tokenstays here
  • Agent sign-instays here
Property line · provider keys stop here
  1. Clone from GitHub The repository comes from its GitHub remote. GitHub’s token goes in as that one command’s environment.
  2. Install the agent host Foreman puts its small agent host in the sandbox, so the agent can run there without your computer.
  3. Set up The install script and the repository’s setup steps run, as they would in a local worktree.
  4. Run The agent takes the turn in the sandbox. Your computer only coordinates.

Session · not started

Turn · waiting to ship

  1. Pick a workspace and a container, then Create. Closing the laptop quits Foreman: remote turns go on in their sandboxes until they finish or reach the session limit, and their chats catch up when you open Foreman again.

This month · no sandbox time yet

Compact, Docker, OpenCode

Try it · Illustrative

Send it off-site

Pick a workspace and a container, ship it, then close the laptop and see who keeps working.

New workspace · atlas

Workspace

Runs on

Sandbox
Docker · ssh://buildbox
Size
vCPU
Starts from
Base · built 2h ago
Sleeps after
20 min idle
Agent sign-in
OpenCode’s own keys

Remote workspaces run on Docker. Experimental.

This computer

Foreman · atlasZzz

Vault

  • Provider keystays here
  • GitHub tokenstays here
  • Agent sign-instays here
Property line · provider keys stop here
  1. Clone from GitHub The repository comes from its GitHub remote. GitHub’s token goes in as that one command’s environment.
  2. Install the agent host Foreman puts its small agent host in the sandbox, so the agent can run there without your computer.
  3. Set up The install script and the repository’s setup steps run, as they would in a local worktree.
  4. Run The agent takes the turn in the sandbox. Your computer only coordinates.

Session · not started

Turn · waiting to ship

  1. Pick a workspace and a container, then Create. Closing the laptop quits Foreman: remote turns go on in their sandboxes until they finish or reach the session limit, and their chats catch up when you open Foreman again.

This month · no sandbox time yet

No header, in a 420px column, This computer

New workspace · atlas

Workspace

Runs on

Runs here, in a git worktree on this computer. Close the laptop and the agent stops with it.

This computer · a git worktree on its own branch.

This computer

Foreman · atlasZzz

Vault

  • Provider keystays here
  • GitHub tokenstays here
  • Agent sign-instays here
Property line · provider keys stop here
  1. Clone from GitHub The repository comes from its GitHub remote. GitHub’s token goes in as that one command’s environment.
  2. Install the agent host Foreman puts its small agent host in the sandbox, so the agent can run there without your computer.
  3. Set up The install script and the repository’s setup steps run, as they would in a local worktree.
  4. Run The agent takes the turn in the sandbox. Your computer only coordinates.

Session · not started

Turn · waiting to ship

  1. Pick a workspace and a container, then Create. Closing the laptop quits Foreman: remote turns go on in their sandboxes until they finish or reach the session limit, and their chats catch up when you open Foreman again.

This month · no sandbox time yet

Commands and events

Events appear here.