{"version":"2.1.267","anchor":"sandbox-system-prompt-now-tells-claude-to-use-copy-when-a-c","canonical_anchor":"sandbox-system-prompt-now-tells-claude-to-use-copy-when-a-c","heading":"Sandbox system prompt now tells Claude to use \/copy when a clipboard tool fails inside the sandbox","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/sandbox-system-prompt-now-tells-claude-to-use-copy-when-a-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Sandbox system prompt now tells Claude to use \/copy when a clipboard tool fails inside the sandbox\n\nClaude is now told to suggest running \/copy when clipboard commands fail inside the sandbox\n\n**What**\n\nWhen 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.\n\nThe `\/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.\n\n**Why**\n\nThis 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.\n\n- Area: Sandbox\n- Names: `\/copy`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}