Follow Discord
Sweep 31 Oct 2026 · 01:10Z Build v2.1.316 534 read Stable v2.1.309 Latest v2.1.316 Next v2.1.316 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.316entry #1

Claude Code v2.1.316 ·

macOS helper app now takes its permission details from the Claude Code program itself

On macOS, the helper app's Info.plist now comes from the Claude Code program; without one, background sessions run from the installed path instead

Under the hood Internal Changes
JSON All of v2.1.316
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
macOSArea: what it touches
Internal ChangesKind: in v2.1.316,
Internal ChangesSection of the release

Unclear It is not clear whether released Claude Code programs carry the embedded description, so the stable helper path may or may not still be used.

What

On macOS, background sessions (Claude Code work that keeps running without an open terminal window) start through a stable copy of the program inside the ClaudeCode.app helper app. Beside that copy sits an Info.plist file, a small description macOS reads to identify the app when it asks you for permissions. That file used to be written from fixed text built into Claude Code. That text named the app com.anthropic.claude-code, kept it out of the Dock, and explained why it wants the microphone, control of other apps (Apple Events) and the local network.

Claude Code now reads that description out of its own program file, where it can be stored in a dedicated section, and writes it to Info.plist. If the program file has no such section, the stable copy is not used at all, and background sessions start from the installed program's own location instead.

This setup only runs on macOS, and only when Claude Code is installed under a claude/versions folder. You can turn it off by setting either of these environment variables:

Why

The stable copy gives macOS a consistent identity in permission prompts. When the description is missing from the program file, background sessions lose that identity without any warning. They run from the raw program path instead, and macOS may then treat them differently when deciding about permissions.

What the documentation says
process.execPath Build an MCP client modified, high confidence > : process.execPath; see the edit
process.execPath Build an MCP client modified, high confidence > : process.execPath; see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether released Claude Code programs carry the embedded description, so the stable helper path may or may not still be…
Anthropic's documentation agreesprocess.execPath on Build an MCP client

See this entry in the whole of v2.1.316 →

Feedback