Desktop app: prompt suggestions (Tab to accept) silently stopped — host gate off since ~Aug 14-20 while user setting is on

Status Open
Reported on v2.1.247
Maintainer reply None cached
Activity 1 comment · opened Aug 28, 2026

Summary

The prompt-suggestion feature (the greyed-out predicted next prompt accepted with Tab, internally "Prompt suggestions" / promptSuggestionEnabled) stopped appearing in the desktop app (Claude Code sessions inside Claude Desktop) between Aug 13 and Aug 20, 2026. Evidence below points to the desktop app's host-side feature gate being turned off server-side, not to any local setting. I relied on this feature daily and would like it back, or a user-visible setting for it.

Environment

  • Claude Desktop for macOS 1.40609.0 (Darwin 25.6.0), bundled Claude Code CLI 2.1.247
  • Terminal CLI 2.1.251 (separate lane, not the subject of this report)
  • Account-level feature flag tengu_chomp_inflection: true (cached in ~/.claude.json the same day as this report)
  • No promptSuggestionEnabled: false anywhere in my settings; CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION unset

Evidence

  1. Clean changepoint in my own session store. The desktop app persists the last suggestion per session (promptSuggestion in the session JSONs). Across 373 stored sessions: suggestions are present in sessions through Aug 13 (49 sessions have one), and zero of the 30 sessions from Aug 20 through Aug 28 have one.
  1. The bundled CLI is being launched without the flag. All 10 live desktop-spawned CLI processes carry --replay-user-messages and --include-partial-messages but not --prompt-suggestions. In app.asar these are set together when the session is created; promptSuggestions is passed only as wC('1942781881') ? !0 : void 0 (a host-side gate check), so the missing flag means that gate currently evaluates false on this install.
  1. No local recovery path exists. I found no gate-override hook in the app bundle, and CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION cannot force-enable in this lane because the SDK path requires the host to have requested promptSuggestions in the first place (the env var is effectively ANDed; it can only disable).

The CLI-side account flag (tengu_chomp_inflection) is still true, so this looks specifically like the desktop host gate (1942781881) being switched off for some or all users in mid-August, while the feature itself remains shipped and enabled at the account level.

Ask

  • Was turning off the desktop gate intentional (experiment ended?) or a rollout accident?
  • If intentional: please consider a user-facing setting instead of a silent removal — the feature is listed in the in-CLI settings ("Prompt suggestions") and my setting is on, which makes the current state look like a bug from the user's side.

Secondary observation

Even where enabled, suggestions are skipped whenever the previous assistant turn exceeds ~10,000 tokens (input + cache-creation + output; the cache_cold check). For users with tool-heavy sessions this filter alone makes the feature rare. If the mid-August change was motivated by low display rates, this threshold may be the actual cause rather than low user value.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗