[FEATURE] add --label or --name argument to distinguish among claude processes

Resolved 💬 3 comments Opened Feb 19, 2026 by amacbride Closed Feb 23, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I often have multiple project-specific claude instances running, and it would be nice to have some way to label each instance (perhaps with libbsd setproctitle() or prctl(PR_SET_NAME)).

A command-line option would be great, and a facility for Claude to be able to internally set its own label after execution.

Proposed Solution

Some examples might be:

% claude --name "libfoo"
...

% ps -e | grep claude
2150110 pts/6 00:06:13 claude [libfoo]

In a session:
> hey claude, please set your process label to "bugfixer"
_Cogitating...._
Done. Process label is now set to "claude [bugfixer]"

The same mechanism could additionally be used to set a status (running, waiting for input, idle, etc.)

Alternative Solutions

One could wrap claude instances in a launch script.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example:
I'm working on several parts of a project across multiple windows and/or tmux sessions. The status/label both orients me to where each thing is running, and could also provide context:

1234 claude pts/4 [bugfixer, waiting for input]
4563 claude pts/5 [tester, running]
7892 claude pts/7 [supervison, idle]

Additional Context

potential implementations:
libbsd setproctitle() or prctl(PR_SET_NAME))
node process.title
python setproctitle

...etc., depending on environment.

View original on GitHub ↗

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