anthropics / anthropics/claude-code-action

Bedrock: 400 error - output_config.effort: Extra inputs are not permitted

Open
#1,005 4 comments 18 reactions 0 assignees View on GitHub
bug p2 provider:bedrock
Dominant language
TypeScript
Stars
8.9k
Forks
2.1k
Avg merge
3d 9h
Merged PRs (30d)
10

Description

## Description

When using `claude-code-action@v1` with Amazon Bedrock (`use_bedrock: "true"`), the action fails with:

```
API Error: 400 output_config.effort: Extra inputs are not permitted
```

The Bedrock API does not support the `output_config.effort` parameter that the action is sending.

## Reproduction

Workflow configuration:

```yaml
- uses: anthropics/claude-code-action@v1
env:
AWS_REGION: us-east-1
ANTHROPIC_DEFAULT_SONNET_MODEL: arn:aws:bedrock:us-east-1:...:application-inference-profile/...
with:
use_bedrock: "true"
claude_args: |
--model "sonnet[1m]"
--max-turns 8
```

## Error Log

```
"result": "API Error: 400 output_config.effort: Extra inputs are not permitted",
"stop_reason": "stop_sequence",
"total_cost_usd": 0,
"usage": {
"input_tokens": 0,
"output_tokens": 0
}
```

The action exits with code 1 without processing any tokens.

## Expected Behavior

The action should either:
1. Not send `output_config.effort` when using Bedrock, or
2. Strip unsupported parameters before forwarding to the Bedrock API

## Environment

- `claude-code-action@v1`
- Bedrock with Application Inference Profiles
- `--model "sonnet[1m]"` (1M token context window)

Contributor guide

Open the contributing guide

Research direction

Start at the Bedrock request handling used when `use_bedrock: "true"` is enabled, using the provided workflow and 400 error to trace where `output_config.effort` is forwarded. Confirm the behavior with the reproduced Application Inference Profile configuration; done means Bedrock requests no longer send the unsupported parameter and the action processes tokens successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
api, backend, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.