# Claude Code v2.1.243

> Claude Code v2.1.243, released 24 Aug 2026 (2026-08-24). 3 entries read out of the shipped bundle. Unofficial, and not affiliated with Anthropic.

Web version: https://changelogs.core-directive.com/v/2.1.243

This build carries the scaffolding for language-server support, but nothing in it turns that support on. There is a manager with start, restart and shutdown entry points, and none of those entry points is called anywhere in the shipped bundle. The tool that would use a language server only ever reads connection status, so no server is ever launched and the tool stays dark. Treat it as groundwork for a later release rather than something you can try today.

## What probably matters to you

Anything you can use today, anything that visibly changes, and anything worth poking at. One line each, open for detail.

### Nothing in the shipped code starts an LSP server

Language-server support is fully built but nothing in the app ever starts one, so it stays dark.

**What**

The language-server support has a manager with start, restart and shutdown entry points, but none of them are called anywhere in the shipped bundle. The LSP tool only ever reads connection status, so in practice no server is launched and the tool stays dark.

**Details**

- The manager exposes get, status, connected, ever-connected, wait-for-initialization, initialize, reinitialize and shutdown; only the four read-only ones have callers.
- The tool's own code waits on initialization if status is pending and checks the ever-connected flag to decide whether it is enabled, but nothing triggers the initialization it waits for.
- The initializer additionally returns early unless the `lspServers` feature flag is on, so even a future caller would be gated.
- Same shape as the previous build; this is not new in 2.1.243.

**Evidence**

`[LSP MANAGER] initializeLspServerManager() called`

- Area: LSP
- Tier: Not switched on
- Useful: 2/5
- Signal: 5/5
- Present in the build but not switched on

### Gateway loopback escape hatch is still present

Pointing the gateway's key-set URL at a loopback address still needs that environment variable set.

**What**

An earlier reading of this build suggested the check behind `CLAUDE_GATEWAY_ALLOW_LOOPBACK` had been removed. It has not: the check and its error text are unchanged, so pointing the gateway's key-set URL at a loopback address still requires that environment variable to be set.

**Details**

- The code moved position in the bundle rather than being deleted.
- Without the variable, a loopback target is rejected with the message naming `cri.jwks_url`.

**Evidence**

`cri.jwks_url targets loopback but CLAUDE_GATEWAY_ALLOW_LOOPBACK is not set`

- Area: Elsewhere
- Names: `CLAUDE_GATEWAY_ALLOW_LOOPBACK`
- Tier: Use it now
- Useful: 2/5
- Signal: 2/5

## Internal Changes

### Version constant bumped to 2.1.243

The version number now reads 2.1.243 everywhere it shows up.

**What**

The build stamp changed from 2.1.242 to 2.1.243. Everything that reports a version now reports the new one, including `--version`, the /status version row, the updater's npm commands, the user-agent strings and the bug-report Environment Info block.

**Details**

- Only the version, build time and git commit fields changed; the package URL, README URL, issues explainer, feedback channel, hooks worker URL and sourcemap group are untouched.
- The same build-metadata object is inlined at roughly 118 places, so the daemon start log line, the `x-environment-runner-version` request header and the Remote Control minimum-version message all pick it up together.
- No behaviour change beyond the reported string.

**Evidence**

`BUILD_TIME: "2026-08-24T21:05:22Z"`

- Area: Elsewhere
- Names: `--version`, `/status`
- Tier: Under the hood
- Useful: 2/5
- Signal: 1/5