CLI binary appears as '2.1.62' (version number) in macOS TCC permission prompts instead of readable name

Resolved 💬 3 comments Opened Mar 11, 2026 by philiplh Closed Mar 15, 2026

Summary

When Claude Code CLI requests macOS privacy permissions (e.g., Files and Folders / Desktop access), the process appears in the TCC prompt and in Privacy & Security settings as 2.1.62 — the version number — rather than a human-readable name like Claude Code or claude.

Steps to Reproduce

  1. Run Claude Code CLI (v2.1.62) in a context where it requests a macOS TCC permission (e.g., Desktop & Documents Folders access)
  2. Observe the permission prompt and/or Privacy & Security > Files and Folders in System Settings

Expected Behavior

The prompt should display a recognizable name such as Claude Code so users can make an informed consent decision.

Actual Behavior

The process is identified only as 2.1.62 — indistinguishable from an unknown or malicious process.

Impact

  • Users cannot identify the requesting process without prior knowledge
  • Creates a security UX failure: cryptic process names in permission prompts train users to either deny everything or approve without reading
  • In this case, the user initially suspected malware or an unrelated process (OpenClaw) before investigating

Environment

  • macOS (Darwin 25.3.0)
  • Claude Code CLI v2.1.62
  • Invoked via tmux pane (hive session, multiple instances)

Suggested Fix

CLI binaries that request TCC permissions should register a human-readable process/display name. Options:

  • Set argv[0] to claude or Claude Code at startup
  • If using an Electron or Node.js wrapper, set app.name appropriately
  • Ensure the binary name shown in Privacy & Security matches the product name

🤖 Generated with Claude Code

View original on GitHub ↗

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