What this error means
Stream stall ~15-30s at start of new session with AskUserQuestion tool is a Claude Code failure pattern reported for developers trying to fix claude code vs code extension stream freezing for 15-30 seconds at session start with askuserquestion tool. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Open issue with 'has repro' label. Specific to VS Code extension with claude-opus-4-7[1m] model. Stream freezes for 15-30s when AskUserQuestion tool is invoked at session start. Clear reproduction steps.
Common causes
- The stream freezes at the start of a new session when the model invokes AskUserQuestion tool, causing a 15-30 second delay before any response appears. This affects user experience in the VS Code extension with claude-opus-4-7 model.
- Open issue with 'has repro' label. Specific to VS Code extension with claude-opus-4-7[1m] model. Stream freezes for 15-30s when AskUserQuestion tool is invoked at session start. Clear reproduction steps.
Quick fixes
- Confirm the exact error signature matches
Stream stall ~15-30s at start of new session with AskUserQuestion tool. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.