Code in Claude Desktop on 3P changedthird-party/claude-desktop/code
Nearest release: v2.1.251, published under an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+4added
Lines−0removed
From line
55
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
## Remote sessions over SSH
The whole hunk
from line 55, old and new numbered
/
from line 55
5555 In a third-party deployment there is no Anthropic authentication, so Claude Code's server-managed settings tier is never present. If you have not separately deployed a Claude Code `managed-settings.json` or OS profile, Claude Desktop's policy applies automatically and you do not need to set `parentSettingsBehavior`.
5656</Note>
5757
58## Remote sessions over SSH
59
60A Code session can run its Claude Code engine on a remote host over SSH while the Code tab stays on the user's device. In a 3P deployment this is off until you set [`sshHostAllowlist`](/docs/third-party/claude-desktop/configuration#sshhostallowlist), because the app forwards the session's inference credential to the host. [SSH remote sessions](/docs/third-party/claude-desktop/ssh-remote-sessions) lists the credential kinds that work on a remote host and which of the keys above apply there.
61
5862## Further reading
5963
6064* [Claude Code settings reference](https://code.claude.com/docs/en/settings-reference)
No line in this hunk matches that.