Claude is now told to suggest running /copy when clipboard commands fail inside the sandbox
When Claude Code runs commands in a sandbox (a restricted environment that limits what a command can access), clipboard tools like pbcopy, xclip, or wl-copy don't work because they can't reach the system clipboard from inside it. Claude's instructions now tell it that when this happens, it should put the text in a fenced code block and tell the user to run /copy themselves, rather than writing the text to a file for the user to copy manually.
The /copy command copies the last assistant response to the clipboard from outside the sandbox; when code blocks are present it shows an interactive picker so the user can select just the block they want, or press w to write the selection to a file instead, which is useful over SSH.
This avoids Claude falling back to writing scratch files just to work around a clipboard command that can't run inside the sandbox, pointing the user instead to the built-in /copy workflow that already handles this case.
* Improved sandbox guidance so Claude suggests `/copy` when clipboard commands such as `pbcopy` fail inside the sandboxsee the edit
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
When Claude Code runs on a remote machine over SSH, it can't run a clipboard tool on your local machine. Outside tmux, when you select text in [fullscreen rendering](/docs/en/fullscreen) or run `/copy`, Claude Code sends the text to your t…troubleshooting see the edit
/copy on Claude Code changelog
Improved sandbox guidance so Claude suggests /copy when clipboard commands such as pbcopy fail inside the sandbox