Use /context to see what is eating your window

Context Management·14 hours ago·verified 14 hours ago·easy·~2 min setup·verified

Run /context to break down token consumers—CLAUDE.md, MCP tools, conversation—and prune the expensive ones.

#context #mcp #tokens #diagnostics

The problem

Sessions feel slow or dumb and you cannot tell whether MCP schemas, memory, or chat history is the culprit.

The hack

Periodically run `/context` (and `/mcp` / `/memory`) to find oversized startup or tool costs, then disable or trim.

Why it works

You cannot optimize what you cannot see. Context breakdowns make cost and rot fixes concrete.

Setup

1. Mid-session, run `/context`. 2. Note heavy categories (MCP, CLAUDE.md, skills, history). 3. Disable unused MCP servers or move CLAUDE.md bulk into skills. 4. Re-check `/context` after changes.

Prompt

/context

Additional details

Pair with /usage to see spend by skill, subagent, and MCP server.

Source

anthropic·View original →·by Anthropic Docs

Does this still work?

Discussion

No comments yet. Be the first to say whether this worked for you.