First Claude Code Session

With installation and authentication complete, launching Claude Code is straightforward.

Starting a session

1. Navigate to a project directory:

   cd ~/projects/myapp

2. Launch Claude Code:

   claude

Alternatively, seed the session with an initial prompt:

claude "explain what this project does"

Claude Code reads the project structure, any CLAUDE.md files, and relevant source files to build context. The first interaction often takes a few seconds as the agent indexes the codebase.

Basic interaction patterns

Effective first sessions follow a predictable rhythm: explore, then act.

Before requesting changes, ask Claude to read and understand the relevant code:

> read the authentication module and explain how sessions are managed

Once context is established, request specific changes:

> add a logout endpoint that invalidates the current session

The feedback loop

Claude Code operates in continuous cycles: gather context, take action, verify results, correct errors.

When implementing a feature, the agent:

1. Reads files
2. Writes code
3. Runs tests
4. Iterates based on failures

Each cycle adds information and refines the solution.

The developer's role in this loop is directorial. Provide clear objectives, let the agent iterate, and intervene when it drifts off course.

Managing context

Use /clear between unrelated tasks to reset conversation history. This prevents context pollution accumulated irrelevant information that degrades agent performance.