Goose

Goose publishes native Linux binaries for both aarch64 and x86_64. Its installer detects the guest architecture, which makes it a relatively small agent setup compared with a large Python environment.

Run Goose

Start Goose

msb run -t --name goose-demo --replace \
  --cpus 2 --memory 2G --root-disk 3G \
  --mount-dir ./my-project:/workspace:rw \
  --workdir /workspace \
  debian:bookworm-slim -- sh -lc '
    apt-get update &&
    apt-get install -y --no-install-recommends ca-certificates curl bzip2 git &&
    curl -fsSL https://github.com/aaif-goose/goose/releases/download/v1.44.0/download_cli.sh |
      GOOSE_BIN_DIR=/usr/local/bin GOOSE_VERSION=v1.44.0 CONFIGURE=false bash &&
    exec goose session
  '

msb run -t --name goose-demo --replace `
  --cpus 2 --memory 2G --root-disk 3G `
  --mount-dir ./my-project:/workspace:rw `
  --workdir /workspace `
  debian:bookworm-slim -- sh -lc '
    apt-get update &&
    apt-get install -y --no-install-recommends ca-certificates curl bzip2 git &&
    curl -fsSL https://github.com/aaif-goose/goose/releases/download/v1.44.0/download_cli.sh |
      GOOSE_BIN_DIR=/usr/local/bin GOOSE_VERSION=v1.44.0 CONFIGURE=false bash &&
    exec goose session
  '

On first launch Goose asks whether to share anonymous usage data, then walks through provider configuration. GOOSE_BIN_DIR installs the executable on the sandbox’s normal PATH, including later msb exec sessions. Goose keeps its configuration, data, and session state on the sandbox’s 3 GiB root disk.

For an isolated workspace, or when using microsandbox cloud, replace --mount-dir ./my-project:/workspace:rw with --copy-dir ./my-project:/workspace. To test Goose without a project, use --mkdir /workspace instead.

Start another session

After leaving Goose, return to the same sandbox and workspace with:

msb exec -t goose-demo -- goose session

Verify the installation

Exit the session and run:

msb exec goose-demo -- goose --version

The pinned installer reports 1.44.0.

Review or export changes

With the default writable mount, changes are already in the host checkout. Review them inside the sandbox:

msb exec goose-demo -- sh -lc 'cd /workspace && git status --short && git diff --stat && git diff'

If you chose the isolated --copy-dir alternative, create a patch inside the sandbox:

msb exec goose-demo -- sh -lc 'cd /workspace && git add -N . && git diff --binary > /tmp/goose.patch'

Copy the patch to the host:

msb cp goose-demo:/tmp/goose.patch ./goose.patch

Check that it applies cleanly before applying it:

git apply --check ./goose.patch

Clean up

Remove the sandbox:

msb rm -f goose-demo

Removing the sandbox also removes its Goose configuration and session data. Changes made through the default workspace mount remain in the host checkout.

Agents

CI/CD

Docker

Sandbox Workflows

Automation & Tooling

Data & Observability

Run Goose

Reference

​Run Goose

​Reference

Run Goose

Reference