Follow Discord
Sweep 12 Nov 2026 · 20:38Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Writing the changelog v2.1.323 rate entries · 3/5

Claude Code v2.1.284 ·

Self-relaunch carries home-directory trust so the prompt is not asked again

When Claude Code restarts itself from your home directory after you accepted the trust prompt, the restarted copy no longer asks again

Group of 2 You'll notice Bug Fixes
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Bug FixesKind: in v2.1.284,
Bug FixesSection of the release

Unclear Exactly which two paths are compared before the prompt is skipped is not confirmed.

What

Claude Code sometimes restarts itself, for example on the --resume path. When it opens a folder it has not been told to trust, it shows a trust prompt first, and your home directory has its own version of that prompt.

  • On relaunch, Claude Code already set CLAUDE_BG_WORKSPACE_TRUSTED to "1". It now also adds a further set of environment variables, which are settings handed to the new process, and removes one more variable first.
  • If you already accepted the home-directory trust prompt, the old process sets CLAUDE_CODE_RELAUNCH_HOME_TRUST to <pid>:<token>. Here pid is the process number and the token comes from a lookup tied to that process.
  • The new process checks three things: that the pid matches its parent (on Windows, its parent's pid), that a path check passes, and that a fresh lookup with skipCache returns the same token. If all three pass, it skips TrustDialog and treats trust as accepted.
  • Any value of CLAUDE_CODE_RELAUNCH_HOME_TRUST inherited from elsewhere is removed before relaunching.

You do not set this variable yourself. Claude Code sets it internally.

Why

The home-directory trust prompt no longer comes back after Claude Code restarts itself. Because the value is tied to the process and a token, a copy of the variable left in your shell cannot be used to skip the trust prompt.

Read from
Names in the bundle--resume
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Manage sessions touched a line naming --resume after this was published. Once you name a session through a CLI route or from claude.ai, return to it with `claude --resume <name>` or `/resume <name>`; a desktop-app session resumes in the [desktop app](/docs/en/desktop#work-in-parallel-with-sessions). See [Resume… sessions see the edit
Confirmed since Anthropic's documentation has since written up --resume, on Claude Code changelog. * Added `claude --desktop` to open the Claude desktop app on the current directory, or on a session with `--continue` / `--resume <id>` changelog 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 doubtExactly which two paths are compared before the prompt is skipped is not confirmed.
Anthropic's documentation agreesAnthropic's documentation has since written up --resume, on Claude Code changelog.

See this entry in the whole of v2.1.284 →

Feedback