remote
A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.138 and was gone by v2.1.284.
Notifications sent from a remote session now actually reach you instead of being silently discarded.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.223.
In the changelogs
28Releases whose published page names remote.
-
v2.1.305
A desktop host can set the name Claude Code's requests are sent under
CLAUDE_CODE_ENTRYPOINT_ON_REQUESTSsets the name requests go out under, but only whenCLAUDE_CODE_ENTRYPOINTisclaude-desktop-3pfound in this entry's text
-
v2.1.301
Git config check for on-demand fetching can now target a named remote
Claude Code's safety check on git configuration before on-demand fetches can now check a specific named remote
found in this entry's text
-
v2.1.299
Git config reader now keeps names like "origin" in section headers
Claude Code now reads the quoted part of git config headers such as [remote "origin"] instead of skipping it
found in this entry's text
-
v2.1.295
Fixes to plugin scope matching and git remote error detection
Plugin scope lookup and duplicate-scope filtering are fixed, and more git server errors are now recognised
found in this entry's text
-
v2.1.283
Git remotes using plain http:// are now refused
When Claude Code looks up a repository's git remote URL, it now accepts only https:// (or file:// where allowed) and refuses http://
found in this entry's text
-
v2.1.281
isolation:'remote' falls back to local when the session has no disk
An agent asking for remote isolation now runs locally, not in a worktree, when remote is unavailable and the session has no disk
found in this entry's text
-
v2.1.280
Git remote-name parsing simplified/changed
Git's bracketed remote-name parsing was simplified, dropping a separate 'named remote' detection step
found in this entry's text
-
v2.1.280
New remote-control entrypoint detection helper
Remote-control session detection now recognizes a remote_trigger entrypoint
found in this entry's text
-
v2.1.277
Plugin install errors now marked as "ours" for downstream handling
Design login now accepts a manually pasted authorization code more flexibly, with clearer failure reasons
found in this entry's text
-
v2.1.274
Git bundle upload now auto-falls-back to a squashed snapshot for partial/promisor clones
Git bundle uploads now fall back to a squashed snapshot when the repo uses partial or promisor clones
found in this entry's text
-
v2.1.269
New agent-SDK control-request: rename_session
SDK control-request rename_session refined with remote/host distinction and a get_memory_dialog request added
found in this entry's text
-
v2.1.267
Conversation now tracks its own "origin" (local vs remote)
Claude Code now tracks whether a conversation originated locally or was resumed from a remote session
found in this entry's text
-
v2.1.260
Remote agent isolation falls back to worktree when unavailable
Remote agent isolation now falls back to worktree or local when remote execution isn't available.
found in this entry's text
-
v2.1.260
AskUserQuestion "extended" question mode gated by env var, off by default
An extended question mode is gated behind an env var and off by default.
found in this entry's text
-
v2.1.248
Session records now capture how a session ended
Session records now store how a session ended and where its working copy came from.
found in this entry's text
-
v2.1.248
Remote desktop accepted as a session origin
Desktop-hosted remote sessions are no longer rejected as an unknown origin.
found in this entry's text
-
v2.1.248
MCP tools routed through the REPL instead of the tool list, switched off
MCP tools could be called from inside the REPL rather than listed as top-level tools.
found in this entry's text
-
v2.1.246
Cloud agent output is sanitized before use
Text coming back from a remote-isolation agent is cleaned before you see it or it's logged.
found in this entry's text
-
v2.1.242
Repo size for upload is now measured by live objects, not pack files on disk
Repos with lots of dead history are no longer squashed or rejected based on pack file size.
found in this entry's text
-
v2.1.236
Cloud sessions can pick a model for you when you start one
Starting an interactive cloud session now picks a model and permission mode for you, announcing changes.
found in this entry's text
-
v2.1.235
Policy helpers can now be delivered by remote settings, but only after an explicit consent record — and they run in a scrubbed environment
Remote-delivered policy helpers now require explicit consent and run with a scrubbed environment
found in this entry's text
-
v2.1.223
Remote notifications from the session stream are routed into the local notification queue
Notifications sent from a remote session now actually reach you instead of being silently discarded.
found in this entry's text
-
v2.1.223
Managed-settings tier merge no longer falls through for two keys
Two admin-managed settings now come only from the top policy tier, so lower tiers can't sneak values in.
found in this entry's text
-
v2.1.223
Remote-stream notifications are namespaced, sanitized and capped
Notifications sent from remote peers are now trimmed, capped and prefixed so they can't flood your queue.
found in this entry's text
-
v2.1.205
Auto-mode repo visibility lookup
found in this entry's text
-
v2.1.179
CLAUDE_CODE_SUPPRESS_SESSION_ATTRIBUTIONEnvironment Variablefound in this entry's text
-
v2.1.178
Agent Tool:
isolation: "remote"— Cloud-Hosted Subagentsfound in this entry's text
-
v2.1.169
"Remote Session" Renamed to "Cloud Session" Throughout
found in this entry's text
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
2Build by build
149One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.