Claude Code v2.1.305 · 20 Oct 2026
A desktop host can set the name Claude Code's requests are sent under
CLAUDE_CODE_ENTRYPOINT_ON_REQUESTS sets the name requests go out under, but only when CLAUDE_CODE_ENTRYPOINT is claude-desktop-3p
Use it now Notable
No documentation found New Features
Copy link
Copy markdown
JSON
All of v2.1.305
Use it now Tier: how much it should matter to you
4 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Desktop Area: what it touches
New Features Kind: in v2.1.305, 20 Oct 26
What probably matters to you Section of the release
What
Claude Code reads a new environment variable, CLAUDE_CODE_ENTRYPOINT_ON_REQUESTS , once at startup and then clears it. Environment variables are settings passed to a program when it starts. Its value sets the name that Claude Code's requests are sent under.
The value is ignored, with a debug message, when:
requests already go out under a name
CLAUDE_CODE_ENTRYPOINT is not claude-desktop-3p
the value is not 1 to 32 characters of lowercase letters, digits, _ and - starting with a letter
the value starts with sdk
the value is reserved: an existing entrypoint name, any name starting with remote , or local_projects
Why
This is meant for one specific desktop app that embeds Claude Code. If you run Claude Code yourself, setting it has no effect.
How sure we are
One source agrees One thing we can check says the same as this entry.
The name it cites is new in this build New in this build: CLAUDE_CODE_ENTRYPOINT_ON_REQUESTS
See this entry in the whole of v2.1.305 →
20 Oct 2026 · 252 entries, this one is #30.
Use it now18 You'll notice118 Nothing to try yet31 Under the hood85
Open the release →
Names in this entry
env CLAUDE_CODE_ENTRYPOINT_ON_REQUESTS CLAUDE_CODE_ENTRYPOINT_ON_REQUESTS sets the name requests go out under, but only when CLAUDE_CODE_ENTRYPOINT is claude-desktop-3p
env CLAUDE_CODE_ENTRYPOINT Waiting for MCP servers before a headless run is tidied up and logs more detail.
setting sdk Headless runs decide more carefully whether to wait for MCP servers before starting.
setting remote Notifications sent from a remote session now actually reach you instead of being silently discarded.
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 29 of 252
Images can display in iTerm2 in fullscreen mode
You'll notice Terminal UI
In v2.1.305 What probably matters to you release-page order
Next → · 31 of 252
Cloud sessions can sync early even after a refused settings fetch
Use it now Cloud Sessions