[FEATURE] Password for running "claude" command

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

Currently, the Claude Code / Claude for IDE tooling does not provide a simple way to protect the CLI / IDE integration with a user-defined password or “local gate”.

If a malicious or accidentally dangerous script (for example, an npm package with a postinstall hook) can trigger Claude commands automatically, it can start sending my code, file contents or prompts to Claude without any explicit confirmation from me.

Right now, once the API key / auth is configured, any process that can run the CLI or talk to the local server can use Claude “on my behalf” with no additional friction. This makes it harder to safely experiment with community tools, custom wrappers or local automations and increases the impact of supply-chain attacks.

Proposed Solution

Create a password creation option for the "claud" command in the terminal

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

I set a password and get security because a third-party script cannot run the "claud" command

Additional Context

_No response_