1.2Set up Claude Code for discovery

Before you explore the application, configure Claude Code so it works safely and efficiently during the discovery phase.

Start in Plan Mode

Discovery is a read-only activity. You are learning, not building. Start Claude Code in Plan Mode so it can read files, run shell commands, and explore — but cannot edit your source code:

claude --permission-mode plan

You can also press Shift+Tab twice during an existing session to switch into Plan Mode. The status bar shows ⏸ plan mode on when active.

Plan Mode is ideal here because:

• Claude can navigate the running application, read its source, and explore routes without accidentally creating files
• you stay in control: Claude proposes a plan, and you approve before any changes happen
• if discovery spans multiple sessions, you can resume with claude --continue

Name the session

Give this session a descriptive name so you can resume it later:

claude --permission-mode plan -n discovery

Or during the session:

/rename discovery

If you close the terminal and need to come back, run:

claude --resume discovery

Let auto memory work for you

Claude Code has auto memory enabled by default. As you explore the application and correct Claude's assumptions, it saves notes for itself (build commands, architecture observations, naming patterns) in ~/.claude/projects/<project>/memory/. These notes persist across sessions.

You do not need to configure this. Just be aware that Claude is already learning from your corrections during discovery. If it misnames a feature area and you correct it, it will remember the correction next session.