Claude Code for beginners: inspect usage with /context
A long Claude Code conversation can hold much more than your latest questions. Instructions, tools and earlier messages also use context. With /context, you can inspect that usage before deciding what to change.
The context window is the amount of information the model can have available at once. This micro-guide follows the Claude Code documentation and uses illustrations.
Inspect context in three steps
You need Claude Code and an active session. For setup, follow Anthropic's setup guide.
- Type
/contextin the Claude Code prompt input. The report shows usage as a colored grid and a category breakdown. - If you use fullscreen mode, type
/context allto expand the full per-item breakdown. The normal view collapses those details to keep the grid visible. - Inspect a category that takes up substantial space and read any optimization suggestions. Then decide which separate action fits your task.
For example, you can check which CLAUDE.md and auto-memory files have loaded. The report can also flag context-heavy tools, memory bloat and capacity issues.
Sources: Claude Code: commands. Claude Code: context window.
Use the report to choose your next step
/context shows usage; it does not free space by itself. If the conversation exceeds the context window, the report can show how far over the limit it is and identify a command that frees space. Read what the suggested action does before using it.
Try the report next time you want to understand what a long session contains. Start with the breakdown rather than changing instructions at random. If you need to return to an earlier point in your work instead, see our /rewind guide.
The Forge newsletter
Get new articles in your inbox
Pick the topics you care about. No noise, at most one email a week.
We follow GDPR. Unsubscribe anytime.