Type /status to See Your Session Info at a Glance
When you're deep in a session, it's easy to lose track of the basics — which model am I on? How much context is left? What directory is Claude working in? The /status command answers all of that instantly.
/status
You get a compact summary of your current session state: the active model, context window usage, working directory, loaded CLAUDE.md files, connected MCP servers, and session ID. One glance tells you everything you need.
When /status is most useful:
- Before a big task — check how much context is available. If you're at 80% capacity,
/compactfirst or start a new session. - After switching models — confirm the model change took effect. If you toggled
/fastor changed with/model, verify it stuck. - When something feels off — if Claude seems to be missing context or behaving differently,
/statusshows whether a CLAUDE.md failed to load or an MCP server disconnected. - In long sessions — after hours of work, check the session ID so you can
/resumeit later.
Combine /status with other diagnostic commands:
/status # quick overview of session state
/cost # how much this session has consumed
/hooks # which hooks are registered
These three commands together give you a complete picture of your session's health without reading any documentation or checking config files.
You wouldn't drive without a dashboard — /status is the dashboard for your Claude Code session.
via Claude Code
Log in to leave a comment.
When typing feels slow — describing a complex bug, explaining architecture, or thinking through a problem out loud — press Option+V to switch to voice input. Speak naturally and Claude Code transcribes your words into a prompt, so you can describe what you need at the speed of thought.
When Claude is heading down the wrong path — editing the wrong file, writing code you don't want, or giving a long explanation you don't need — press Escape to stop it immediately. You keep everything it did up to that point and can redirect with a new prompt.
Closed a session and realized you weren't done? Pass --continue (or -c) when launching Claude Code to pick up exactly where you left off — same context, same files, same conversation history — without re-explaining what you were working on.