Skip to content

This page takes you from the installed fbk and fbkd binaries to a coding agent running in a sandbox. Install them first; see Installation.

Run fbk start in your project directory:

Terminal window
cd ~/projects/my-project
fbk start

The first start pulls the base image, so it takes a while. When the sandbox runs, fbk start prints how to connect to it:

Connect with: ssh my-project.fbk
Open in VS Code: code --folder-uri vscode-remote://ssh-remote+my-project.fbk/workspaces/my-project
Open in Zed: zed ssh://my-project.fbk/workspaces/my-project

The project directory is mounted in the sandbox at /workspaces/my-project. Without a .firebrick.yml, the sandbox uses the defaults; see Configuration to change them.

Store the key as a secret, reading it from stdin so it stays out of your shell history:

Terminal window
fbk secret set ANTHROPIC_API_KEY --from-stdin < ~/anthropic-key.txt

The sandbox never sees the real key: its ANTHROPIC_API_KEY holds a placeholder, which the host replaces with the key only in requests to api.anthropic.com. A running sandbox gets a new secret after a restart:

Terminal window
fbk stop
fbk start

See Secrets for other tokens and hosts.

Open a shell in the sandbox:

Terminal window
fbk run bash

The base image comes with mise, so you can install an agent CLI in the sandbox, for example Claude Code with Node:

Terminal window
mise use -g node@lts npm:@anthropic-ai/claude-code
claude

The agent works on the files in /workspaces/my-project, which are your project files on the host. The sandbox keeps running after you exit the shell.

You can also connect with SSH, or point your editor at the same host name:

Terminal window
ssh my-project.fbk

See Editor support for VS Code, Zed and JetBrains.

Stop the sandbox when you’re done. It keeps its disk, so the installed tools are still there the next time you run fbk start:

Terminal window
fbk stop

Remove the sandbox to delete its disk. Your project files stay on the host:

Terminal window
fbk rm