`sbxm files`
sbxm files add <path> [--dest <destination>]sbxm files lssbxm files rm <destination>sbxm files pull <destination> [<project-id>]files edits the files list in ~/.sbxm/config.yaml. It changes declarations only; files are placed in sandboxes by the first build and by sbxm apply --files.
Declares one host file. A relative path is resolved from the current directory. The destination defaults to the file’s path relative to your home directory, so ~/.claude/CLAUDE.md is placed at .claude/CLAUDE.md in the sandbox home. Use --dest for a file outside your home directory or to place it elsewhere.
The file is checked before the declaration is saved: it must be a regular file (not a directory or a symbolic link) within the size limit, and the destination must stay inside the sandbox home. A name that often holds credentials, such as .env, credentials, id_rsa, or a name containing token, is saved with a warning; keep credentials in Docker Sandboxes secrets instead.
A destination that is already declared with another source is refused. Declaring the same file again changes nothing.
After a new declaration is saved, an interactive terminal asks whether to place the declared files in every registered project now, which runs the same steps as sbxm apply --files --all. Otherwise the command shows that command to run later.
The existing configuration keeps its comments and formatting. The new entry follows the style of the existing entries. If sbxm cannot confirm that the rest of the file stays as written, it refuses and shows the entry to add by hand.
Lists the declared files with their destinations.
Removes the declaration whose destination is <destination>. Copies already placed in sandboxes are left as they are.
Brings an edit made inside a sandbox back to the host file. In an interactive terminal the project ID may be omitted and selected. The sandbox must be running; a stopped sandbox is not started.
sbxm copies the sandbox file into the project’s .sbxm/incoming area, never over an existing file, refusing a destination reached through a symbolic link and a copy larger than the declared-file size limit. It then shows how the copy differs from the host file, using the host’s git diff --no-index with external diff tools, textconv, and attributes turned off. Control characters and characters that change text direction are shown as \u{...} instead of reaching the terminal.
Nothing is merged automatically. An interactive terminal asks whether to adopt the copy; a non-interactive run only shows the differences. Adopting replaces the host file with the copy, keeping its permissions, only if the host file has not changed since the differences were shown, and records that the host and this sandbox now hold the same content. The received copy is removed either way.