This morning, a post on r/ClaudeAI with over 130 points drew attention to something most people never noticed: Claude Code's Prompt Suggestions, the dim grey text that appears in the input box after every reply suggesting what to type next, aren't free. Generating each suggestion requires re-reading the entire conversation context in the background, and that counts against your usage.
What are Claude Code's Prompt Suggestions?
It's the greyed-out "ghost text" that appears at the end of the input line once a reply finishes, suggesting your next prompt, something like "commit and push" or "continue". Accept it with Tab, right arrow or End, and it becomes a real prompt once you confirm it.
Does this really eat into my weekly limit?
Yes, the mechanism is real, and Anthropic itself confirms it, just not with a number. The official changelog for the anthropics/claude-code repository has a recent entry that only makes sense if the feature is billed against your quota:
"Fixed CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION=true not keeping prompt suggestions on when your account is near, but not over, its usage limit"
In other words: Claude Code already turns this feature off on its own when you get close to your limit, proof that generating the suggestion is measured against the same quota as the rest of your usage.
The specific number isn't official. The Reddit post that triggered this article (user SmoothParfait) measured their own telemetry and reported that, in a long context, the cost of generating one suggestion came close to the cost of the actual prompt that triggered it, with a full cache read of the history on every turn. That's a self-instrumented, non-audited report, but the underlying mechanism (re-reading context to generate ghost text, billed against your quota) matches what the official changelog already acknowledges.
How do I actually turn this off?
There are two paths, both officially documented:
| Method | Where to set it | Command |
|---|---|---|
| Setting (official) | ~/.claude/settings.json (user), .claude/settings.json (project), .claude/settings.local.json (local), or via /config | "promptSuggestionEnabled": false |
| Environment variable | your shell, or inside the "env" block of settings.json | CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION=false |
The fastest path, straight from the terminal:
export CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION=falseOr, inside a Claude Code session, type /config and look for the prompt suggestions option to turn it off without editing any file.
Does turning this off make anything worse?
No. It's a purely cosmetic convenience feature: without it, you just stop seeing the grey ghost text suggesting your next prompt, and keep typing normally. No model capability changes.
What if my limit keeps draining fast even after I turn it off?
Then that wasn't the cause. Run /usage before and after a normal turn to compare real consumption, and if the drain persists, the next place to look is subagents running in parallel, connected MCP servers, or a session context that's grown too large.
Hunting down a convenience feature that quietly eats your quota is the kind of investigation that only exists because a quota exists in the first place. Verboo Code's plans run with unlimited tokens, so it doesn't matter how much context a prompt suggestion needs to re-read: there's no ceiling to hit.
