Essential Commands and Navigation
Introduction
Welcome to the third unit of Foundation — Getting Started with Claude Code! In the previous units, we learned what Claude Code is and how to manage basic sessions using commands like /clear, /exit, and /resume. Now we are ready to gain more control over our development environment.
This lesson introduces the essential commands that allow us to inspect and configure our Claude Code sessions. We will learn how to check our current session state, switch between different Claude models, manage what Claude can access, and understand the settings that govern our workflow. These commands give us the visibility and control we need to work effectively with Claude Code. Let's explore these powerful tools together.
Controlling Your Environment
When we work with Claude Code, we are not just having a conversation; we are operating within a specific environment with particular settings, permissions, and capabilities. Understanding and controlling this environment is crucial for effective development.
Think of these commands as the "dashboard" of a car: they tell us what mode we are in, what resources are available, and how to adjust our settings. Just as we would not drive without checking our mirrors and gauges, we should not develop without understanding our Claude Code environment. These commands help us work more intentionally and troubleshoot issues when things do not behave as expected.
Checking Session Status
The first and most fundamental command is /status, which provides a detailed snapshot of our current session. This command reveals the inner workings of our environment through a tabbed interface. Let's see what information it reveals:
The output is organized into tabs that you can cycle through using the Tab key. In the Status view, we see several critical pieces of information. The Session ID is a unique identifier for your current work. The cwd (current working directory) shows exactly where Claude Code will create and modify files. Finally, the Model section confirms which AI version is currently processing your requests.
This command becomes invaluable when something seems off. If Claude Code is not finding files we know exist, checking the cwd confirms we are in the right directory. If you are unsure why Claude is behaving a certain way, the Setting sources line tells you which configuration files (like Local or Shared project settings) are influencing the session. The /status command is our first line of investigation.
