[DOCS] Quickstart Guide: Logical circularity in Login (Step 2) and Startup (Step 3)

Resolved 💬 3 comments Opened Jan 17, 2026 by coygeek Closed Feb 28, 2026

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/quickstart

Section/Topic

Quickstart Guide: Step 2 (Log in to your account) and Step 3 (Start your first session).

Current Documentation

Step 2: Log in to your account Claude Code requires an account to use. When you start an interactive session with the claude command, you'll need to log in: ``bash claude # You'll be prompted to log in on first use ` `bash /login # Follow the prompts to log in with your account ` ... **Step 3: Start your first session** Open your terminal in any project directory and start Claude Code: `bash cd /path/to/your/project claude ``

What's Wrong or Missing?

The current sequence is logically circular for a first-time user.

  • Step 2 instructs the user to use the /login slash command. However, slash commands only function inside the Claude Code interactive REPL.
  • Step 3 is where the documentation tells the user how to actually enter the REPL by running the claude command.

If a user follows these steps linearly, they will attempt to run /login in their standard shell (Bash, Zsh, or PowerShell), which will result in a "command not found" error because the application hasn't been started yet. Furthermore, Step 2 already includes the claude command in its code block, making Step 3 redundant and confusing.

Suggested Improvement

Reorder and consolidate the steps so that starting the application precedes (or includes) the login process.

Suggested Revised Flow:

Step 2: Start your first session and Log in
Navigate to your project directory and launch Claude Code. On your first run, the application will automatically guide you through the login process.

cd /path/to/your/project
claude

Follow the instructions in your browser to authenticate.

Note: If you are already in a session and need to switch accounts, you can use the /login slash command.

Step 3: Verify your status
Once authenticated, you can check your connection and account details:

> /status

Impact

High - Prevents users from using a feature

Additional Context

  • Related documentation: The [Interactive Mode](/en/interactive-mode) documentation correctly identifies that slash commands are session-specific, but the Quickstart Guide breaks this mental model by placing the slash command before the startup instructions.
  • User Experience: New users often copy-paste line by line. Copying /login into a terminal before claude is running is a guaranteed failure point for onboarding.

View original on GitHub ↗

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