box.slicervm.com - Your own private Slicer box

Examples

How people use their box

Configure your environment:

$ export SLICER_URL=https://box.slicervm.com
$ export SLICER_TOKEN_FILE=~/.slicer/gh-access-token

Check status:

$ slicer vm list
$ slicer vm top

Open a shell:

$ slicer vm shell

You are now inside your private Firecracker VM. The disk persists between sessions.

Drive your box programmatically using the Slicer SDK.

client := slicer.NewClientFromEnv()

out, err := client.Exec(ctx, slicer.ExecRequest{
    VM:      "alexellis-1",
    Command: []string{"uname", "-a"},
})
if err != nil {
    log.Fatal(err)
}

fmt.Println(out.Stdout)

This is how agents, scripts, and automation interact with your box.

Copy credentials and source code to your box:

# Ensure SLICER_URL and SLICER_TOKEN_FILE are set
$ slicer vm cp ~/.config/opencode vm:/home/ubuntu/.config/opencode
$ slicer vm cp --tar ./repo vm:/home/ubuntu/repo
$ slicer vm shell

Inside the VM, run a task:

$ arkade get opencode
$ cd ~/repo
$ opencode -m "Analyze this repo for common bugs and write results to REPORT.md"

Copy the report back to your machine:

$ slicer vm cp vm:/home/ubuntu/repo/REPORT.md ./REPORT.md

The agent runs remotely with a warm filesystem and long context.

Copy your AMP secrets file to the VM:

# Ensure SLICER_URL and SLICER_TOKEN_FILE are set
$ slicer vm exec <hostname> -- mkdir -p ~/.local/share/amp
$ slicer vm cp ~/.local/share/amp/secrets.json <hostname>:~/.local/share/amp/secrets.json

The secrets file must be in ~/.local/share/amp/secrets.json for AMP to find it.

Install K3s using k3sup:

# Ensure SLICER_URL and SLICER_TOKEN_FILE are set
$ slicer vm shell
$ arkade get k3sup kubectl
$ k3sup install --local

Set up KUBECONFIG (written to current directory):

$ export KUBECONFIG=$(pwd)/kubeconfig
$ kubectl get nodes

Reset the VM anytime to return to a clean state.

Forward Docker's socket to your local machine:

# Ensure SLICER_URL and SLICER_TOKEN_FILE are set
$ slicer vm port-forward \
    -L /tmp/docker.sock:127.0.0.1:/var/run/docker.sock

Use Docker locally with the remote engine:

$ export DOCKER_HOST=unix:///tmp/docker.sock
$ docker ps
$ docker run --rm -t alpine cat /etc/os-release

Run containers remotely without SSH tunnels or exposing ports.

Install PostgreSQL using apt:

# Ensure SLICER_URL and SLICER_TOKEN_FILE are set
$ slicer vm shell
$ sudo apt update && sudo apt install -y postgresql
$ sudo systemctl enable postgresql
$ sudo systemctl start postgresql

Verify and forward the port:

$ sudo -u postgres psql -c "select version();"
$ slicer vm port-forward \
    -L 127.0.0.1:5432:127.0.0.1:5432

Connect from your local machine:

$ psql -h 127.0.0.1 -U postgres

This is not managed Postgres. It's your database inside your box.

A box you can always reach

Your box is a personal Firecracker microVM with a persistent disk, accessible via CLI. It's included with Slicer Home Edition as a companion to your self-hosted setup.

Sub-second boot

Firecracker microVMs boot in <1s with strong isolation and a full Linux kernel.

CLI-driven access

Use slicer vm shell, exec, cp, and port-forward.

Agent-ready

Perfect sandbox for Claude Code, Amp, OpenCode, and other coding agents.

Persistent disk

Your data persists between sessions. Install packages and they stay installed.

Always available

Run cron jobs, background tasks, and services without keeping your laptop on.

Included with Home Edition

Your box comes at no extra cost with your Slicer Home Edition license.

Your own private Slicer box