Skip to content

Bedrock + Opus 4.7 still fails with thinking.type.enabled error (v1.0.107) #1265

@tomoki-takahashi-oisix

Description

@tomoki-takahashi-oisix

Summary

Follow-up to #1225. The Bedrock path (use_bedrock: true) still sends the
legacy thinking.type.enabled parameter to Opus 4.7 and fails with HTTP 400.

The v1.0.99 fix appears to only have addressed the direct Anthropic API path.
Bedrock users on Opus 4.7 are still broken as of v1.0.107.

Reproduction

Workflow:

- uses: anthropics/claude-code-action@v1.0.107
  with:
    use_bedrock: "true"
    claude_args: |
      --model arn:aws:bedrock:ap-northeast-1:<acct>:application-inference-profile/<id>
      --max-turns 100

The Application Inference Profile points to global.anthropic.claude-opus-4-7.

Error

SDK execution error: ...
API Error: 400 {"type":"error","error":{"type":"invalid_request_error",
"message":"\"thinking.type.enabled\" is not supported for this model.
Use \"thinking.type.adaptive\" and \"output_config.effort\" to control thinking behavior."}}

User-agent in upstream logs: claude-cli/2.1.119 (external, claude-code-github-action)

Environment

  • Action: anthropics/claude-code-action@v1.0.107
  • Provider: AWS Bedrock (ap-northeast-1)
  • Model: global.anthropic.claude-opus-4-7 (via Application Inference Profile)
  • Agent SDK: 0.2.113 (bumped in v1.0.100 per release notes)

Expected

Action should send thinking.type.adaptive for Opus 4.7 over Bedrock,
matching the fix already applied to the direct Anthropic API path.

Workaround

Pinning Bedrock Application Inference Profiles back to Opus 4.6.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingp2Non-showstopper bug or popular feature requestprovider:bedrockAWS Bedrock API

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions