Source Intelligence
Follow Discord

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.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Device bridge registers this machine as a remote-tools device

Not switched on
Useful3 Signal5
Device Bridge Notable not in their notes

Your machine can register as a named remote device with a tool that reports its environment.

A WebSocket device bridge with an MCP server named claude-code-device sits behind the tengu_violin_wood gate, defaulting false, with an overridable bridge URL.

Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.225: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.225. It isn't a statement about your account. What a flag value here can and cannot tell you

CLAUDE_REMOTE_TOOLS_BRIDGE_URLallow_remote_sessions
What

A new subsystem connects the CLI to a claude.ai bridge over WebSocket as a named device and exposes an MCP server for it. It is off in this build unless the remote gate turns on.

Details
  • MCP server name claude-code-device, with one tool get_device_info, described as "Returns runtime environment details for this device (platform, architecture, Claude Code version, and device name). Call this to confirm the device connection is live."
  • handles handshake, heartbeats ({"type":"hb"}), reconnect backoff, slot contention and a 33554432-byte inbound frame cap
  • the default enable check awaits the remote gate tengu_violin_wood and falls back to false if it throws
  • additionally requires non-first-party egress to be allowed, provider firstParty, and the allow_remote_sessions policy
  • default endpoints are wss://bridge.claudeusercontent.com and wss://bridge-staging.claudeusercontent.com, overridden by CLAUDE_REMOTE_TOOLS_BRIDGE_URL
Evidence

[deviceBridge] skipped: non-essential egress disabled, non-first-party provider, or remote sessions policy-denied

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →