[BUG] No feedback in VSCode extension when bedrock auth token is expired
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I am using Claude code via the extension with Amazon bedrock.
My aws creds expire every day. When this has happened and I interact with Claude via the extension it just hangs saying "Manifesting..." etc and I am never told that my tokens have expired:
<img width="179" height="103" alt="Image" src="https://github.com/user-attachments/assets/395b25c8-1c39-45a8-9390-4380066d6bba" />
If I open up "Output > Claude VS Code" then I can see the error:
From claude: [ERROR] Error streaming, falling back to non-streaming mode: 403 The security token included in the request is invalid
When using Claude Code from the CLI I do see a message:
<img width="458" height="67" alt="Image" src="https://github.com/user-attachments/assets/c82642a7-5abf-4bca-a6ef-8c83e7c8531e" />
What Should Happen?
The VSCode extension should show the security token error when it doesn't have the relevant permissions to connect to bedrock rather than just spinning forever
Error Messages/Logs
Steps to Reproduce
Try to prompt Claude in the extension when configured for bedrock without a valid token in your ~/.aws/credentials
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.13 (Claude Code)
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
8 Comments
Update - it does _eventually_ show the error:
<img width="579" height="112" alt="Image" src="https://github.com/user-attachments/assets/5954dcb0-a2e1-4e0d-adc7-f904c35cc6c2" />
But I guess only after the 10 retries. It would be great if it could show the error that was causing the retry in the same way as the CLI does so that I don't spend too long sitting there waiting for a response!
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
The problem still exists :'(
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
I guess a comment doesn't count as activity?
The issue still exists. I don't know if there is anything I can do to make it qualify to be looked at by something other than the
github-actionsbot?Yes another issue unresolved
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.