Signals

2026-10-13 / Claude Code

Restricted Claude graders now filter built-ins registered after launch

Edited by Michael Ruescher

2.1.295 (2026-10-08) fixes --restricted and --tools failing to apply to late-registering built-ins, and deprecated names reaching tools outside the caller's set. Earlier 2.1.290 also closes restricted cross-session messaging and a changed-link read path. Latest at cutoff, 2.1.296, contains these repairs; stable 2.1.287 does not. The previous issue's stable grader recommendation therefore needs a newer minimum.

What this changes for operators

  • CI and evaluation owners using restricted graders: pin latest 2.1.296; 2.1.295 is the first release with the late-tool fix. Keep sandbox or container restrictions and --permission-prompts none where an ask must stop unattended work. A package on the stable channel is insufficient.
  • Enumerate available tools after late registration and try a harmless excluded built-in, a deprecated alias and cross-session messaging. Record denial and absence of side effects before treating the tool set as effective. This acceptance work replaces a false restricted-mode assumption, not the grader’s assessment of output quality.

Signal metadata

Source findings

Featured in

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-13-claude-code-restricted-graders-need-late-tool-fix

Research evidence and publication history are open in the repository.