Use /context to Inspect Token Usage

When a Claude Code session starts feeling slow or unfocused, inspect the context before guessing.

Run:

/context

Use it to see what is taking space: messages, files, tools, memory, MCP servers, and other loaded context.

When to use it

• Before a long refactor.
• After a large investigation.
• When Claude seems to forget earlier instructions.
• Before deciding whether to /compact or /clear.
• When tuning CLAUDE.md, skills, MCPs, or status line context.

What to do next

• If the session contains unrelated work, use /clear.
• If the session is still one coherent task, use /compact.
• If always-loaded instructions are too heavy, prune CLAUDE.md.
• If external tools are loading too much, disable or scope MCPs more tightly.