claude update detects its own spawned process as 'another Claude process running'

Resolved 💬 6 comments Opened Dec 21, 2025 by blasphemetheus Closed Feb 27, 2026

Description

The claude update command fails with the error "Another Claude process is currently running" even when no other Claude process is running. The issue is that the update mechanism spawns a subprocess that is then detected as "another process."

Steps to Reproduce

  1. Ensure no Claude processes are running: pkill -9 -f claude
  2. Run claude update
  3. Observe the error: "Another Claude process is currently running."

Expected Behavior

The update should proceed normally when no actual Claude sessions are active.

Actual Behavior

The update command detects its own spawned subprocess and refuses to proceed. The --force flag on claude install also does not work.

Workaround

Manual update by downloading the binary directly and updating the symlink.

Environment

  • OS: Linux (Manjaro)
  • Claude Code version: 2.0.74 → 2.0.75

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗