VS Code Extension Settings Documented in README Not Recognized
A VS Code extension documents configuration settings in its README that are not actually recognized by the extension at runtime. Users configure settings that silently have no effect.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyLM Studio Provider Misreports Context Window Size to Copilot Chat
The LM Studio provider for a coding extension reports a fixed 147K-token context window to VS Code Copilot Chat regardless of the model's actual configured window (e.g., 32,768 tokens), and usage stays stuck at 0%. This prevents Copilot Chat's automatic conversation compaction from triggering as the real context fills up.
VSCode notification when Claude Code needs input over SSH
When using Claude Code via VSCode Remote SSH, there is no notification when Claude stops and needs input. Standard notification methods fail on headless servers.
AI Agent Fleet Configs Corrupted by Global Settings Mutations
In multi-agent coding tool fleets, commands that appear to be session-scoped (like /model and /effort) actually write to a shared global config file. Any agent invoking these mid-session silently overwrites the config for all other agents and future spawns. There is no per-agent isolation or way to detect which agent last mutated shared state.
CLI Companion Speech Bubble Duration Not Configurable
The CLI companion pet speech bubble disappears too quickly for non-native English speakers to read. There is no configuration option to adjust the display duration, making useful companion feedback inaccessible.
Desktop Coding App Usage Popover Lost Session Context Window Indicator
A desktop coding assistant regressed so the usage popover no longer shows session context usage, leaving users unable to see how close a long session is to compaction. Plan usage can read low while the session is nearly full.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.