2.1.4 Test (2.1.4)
| # | Feature | Status | Key Finding |
Claude Code 2.1.4 is a minimal release that introduced one operational environment variable, CLAUDE_CODE_DISABLE_BACKGROUND_TASKS, alongside a single OAuth refresh bug fix.
What the release contains
Two items ship in 2.1.4. The env var CLAUDE_CODE_DISABLE_BACKGROUND_TASKS, when set, disables all background task functionality: the Ctrl+B shortcut is silenced, auto-backgrounding of long-running tasks does not occur, and every task runs in the foreground. The OAuth refresh fix addresses a credential-renewal edge case; it carries no user-facing toggle and is not separately testable.
The env var fits a pattern Claude Code has been accumulating since 2.1.2: operational knobs delivered as environment variables rather than config-file entries. Practical targets include non-interactive CI/CD pipelines (where Ctrl+B is meaningless), scripted claude -p invocations, debugging sessions where foreground execution simplifies tracing, and resource-constrained hosts where spawning background processes is undesirable.
Usage is straightforward:
export CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1
claude
or inline:
CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1 claude -p "do something"
What the test found
Testing was performed on 2026-01-16 against version 2.1.9 (the then-current release carrying 2.1.4 features). The test status is CODE REVIEW ONLY: runtime verification of the feature was not completed because confirming that Ctrl+B does nothing and that auto-backgrounding does not occur requires an interactive terminal, known baseline behavior to compare against, and controlled task-duration conditions. The manual test protocol was written and queued but not executed.
"testing a negative... you're testing that something DOESN'T happen. how do you verify Ctrl+B does nothing? how do you verify auto-backgrounding doesn't occur? you need to know what WOULD have happened, then confirm it didn't."
The OAuth fix was classified not testable and left unverified.
Epistemic status
All behavioral claims here are changelog-derived and code-review-derived, not runtime-verified. The described behavior reflects source-level inspection and documented intent, not observed execution. Anyone relying on CLAUDE_CODE_DISABLE_BACKGROUND_TASKS for production pipelines should perform their own before/after verification against the interactive terminal steps documented in the test protocol.
Why it matters
2.1.4 is a "breathing room" release after 2.1.0's large feature drop and 2.1.2-2.1.3's plumbing work. The env var pattern it advances is the Unix-native way to configure runtime behavior without touching config files: predictable, scriptable, CI-friendly. The release demonstrates that not every Claude Code version ships a feature dump; targeted operational controls delivered incrementally are part of the release model.
- file2.1.4/SUMMARY.md
release_2bb05d2463ab64154c53db31ed255199b87705613b1e2fd064d57fa75a6b679d2856ceafad6b1daa8f982493871b6dd4c74cdb228e1c92f39aae2180e0ad6e99f94401d52d111728c6be996f1a01e5e0c57869b6b2b8aca9e143c7db117bf6ab9402025963fd81ec1a9f8a4212a780cSigned with an ed25519 key held off the repo. Anyone can verify against the published public key; nobody without the secret key can forge it. Click verify: it recomputes the signature in your browser. The signature proves integrity and authorship of this exact content — not a third-party timestamp or that the underlying claim is objectively true. signedAt is when the @f3/attest pipeline ran, not when the work happened; the evidence refs carry the source dates.
- introduces CLAUDE_CODE_DISABLE_BACKGROUND_TASKS Primitive