{"version":"2.1.284","anchor":"remote-tool-serve-project-hooks-that-cannot-be-sandboxed-no","canonical_anchor":"remote-tool-serve-project-hooks-that-cannot-be-sandboxed-no","heading":"Usage reports now say why a project hook could not run in the sandbox for remote calls","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/remote-tool-serve-project-hooks-that-cannot-be-sandboxed-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Usage reports now say why a project hook could not run in the sandbox for remote calls\n\nWhen a project pre-tool hook cannot be sandboxed for a remotely served tool call, Claude Code now records why; the hook's outcome is unchanged\n\n**Unclear.** It is not clear how remote tool serving is switched on.\n\n**What**\n\nA `PreToolUse` hook is a command you set up to run before a tool call, where a tool call is Claude asking to use a tool such as running a command. When Claude Code runs tool calls on behalf of a remote session and a project's `PreToolUse` hook cannot be run inside the sandbox (a restricted environment for commands), the reason is now recorded in usage reporting. Before, these cases were not reported. The reasons are:\n\n- `unpinnable`\n\n- `shell`\n\n- `shell_prefix`\n\n- `stopped`\n\n- `outside_readable`\n\n- `unknown_reach`\n\nThe sandbox mode is also now passed through to the sandbox for these hooks.\n\n**Why**\n\nOnly the reporting changes. What happens to the hook and the tool call is the same as before.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}