{"version":"2.1.284","anchor":"telemetry-sandbox-mode-on-sandbox-fallback-events-held-ms","canonical_anchor":"telemetry-sandbox-mode-on-sandbox-fallback-events-held-ms","heading":"Directory-sync usage data no longer measures hold time, and sandbox fallback reports record the mode","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/telemetry-sandbox-mode-on-sandbox-fallback-events-held-ms","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Directory-sync usage data no longer measures hold time, and sandbox fallback reports record the mode\n\nDirectory-sync publishing stops waiting for a snapshot and drops its hold-time figure; sandbox fallback reports now include the sandbox mode\n\n**Unclear.** Whether anything relied on the directory-sync step waiting for the snapshot is not known.\n\n**What**\n\nTwo changes to the usage data Claude Code records:\n\n- Directory-sync publishing between tool calls no longer waits for a snapshot to be taken before it finishes, and no longer reports how long the sync was held. It now reports only the outcome and how long the step took.\n\n- The report sent when a sandboxed command falls back or is rewritten now includes a `sandbox_mode` field. A sandbox is the restricted environment Claude Code can run commands in.\n\n**Why**\n\nBecause the directory-sync step no longer waits on a snapshot, it may finish slightly earlier than before. The hold-time measurement that had been recorded for that step is gone.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}