[BUG] [VSCode Extension 2.1.72] Bedrock integration broken - eager_input_streaming error

Resolved 💬 4 comments Opened Mar 11, 2026 by GaeJobBu Closed Mar 15, 2026

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?

VSCode Extension version 2.1.72 fails when using AWS Bedrock with error:
"API Error: 400 tools.0.custom.eager_input_streaming: Extra inputs are not permitted"

The same Bedrock configuration works perfectly with:

  • Claude Code CLI version 2.1.72 ✅
  • VSCode Extension version 2.1.71 ✅

Only VSCode Extension 2.1.72 is affected.

What Should Happen?

VSCode Extension should work with AWS Bedrock without errors, just like version 2.1.71 and CLI 2.1.72.
The extension should not send unsupported parameters to Bedrock API.

Error Messages/Logs

API Error: 400 tools.0.custom.eager_input_streaming: Extra inputs are not permitted

Steps to Reproduce

  1. Configure AWS Bedrock:
  • Set up ~/.aws/credentials with valid access keys
  • Set environment variables: CLAUDE_CODE_USE_BEDROCK=1, AWS_REGION=us-east-1
  • Or add to VSCode settings.json:

"claudeCode.environmentVariables": [
"CLAUDE_CODE_USE_BEDROCK=1",
"AWS_REGION=us-east-1"
]

  1. Install VSCode Extension 2.1.72
  2. Open any project folder in VSCode
  3. Open Claude Code panel
  4. Send any message/request
  5. Observe 400 error immediately

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

VSCode Extension 2.1.71

Claude Code Version

2.1.72

Platform

AWS Bedrock

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

Investigation findings:

  • Binary search shows eager_input_streaming present in VSCode Extension's claude.exe
  • This parameter appears to be newly added in 2.1.72
  • Bedrock API rejects this custom tool parameter
  • CLI 2.1.72 does not have this issue, suggesting VSCode extension-specific bug

Attempted workarounds (no effect):

  • Environment variable: CLAUDE_DISABLE_EAGER_STREAMING=1
  • Cache clearing: deleted ~/.claude/cache/*
  • Extension reinstallation

Confirmed workaround:

  • Downgrade to 2.1.71: code --install-extension anthropic.claude-code@2.1.71
  • Disable auto-update in VSCode settings

Impact: Complete breakage of Bedrock integration for all VSCode Extension 2.1.72 users.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗