Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.208 Home All releases olderv2.1.207 v2.1.209newer
Claude Code v2.1.208

Linux sandbox violation monitor

What

When running with the Linux sandbox enabled, Claude now starts a Unix-socket observer that monitors for filesystem violations (writes to paths that should be denied). Violations are reported in real time rather than only being caught after the fact.

Details
  • Creates a temporary socket file under /tmp/srt-obs-*
  • Receives structured violation events (syscall name, path, command) from the sandbox kernel module
  • Applies ignoreViolations filters (by path prefix and by command name)
  • The monitor socket path is passed to the sandbox so it can report outbound writes
  • If the socket fails to start, violation monitoring is disabled but the sandbox itself continues running
Evidence

Linux sandbox monitor (search for "Started Linux seccomp violation monitor" and "[Sandbox Linux Monitor]")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.208 →