Add Bedrock adaptive thinking support for Claude Opus 4.7

[kernelalex]

Problem

AWS Bedrock Claude Opus 4.7 rejects the current reasoning payload emitted by PentAGI/langchaingo:

thinking.type.enabled with budget_tokens

Bedrock returns a 400 validation error because Opus 4.7 requires adaptive thinking:

thinking.type.adaptive with output_config.effort

The settings UI also only exposed reasoning effort and max token budget, so users could not configure Bedrock adaptive
thinking from /settings/providers.

Solution

This PR introduces explicit reasoning modes to the provider configuration and settings UI. Here’s what’s included:

New ReasoningMode type: Supports adaptive and budget options, fully wired up across GraphQL, backend config, and frontend type generation.
Updated settings UI: Provider configs now include a Reasoning Mode dropdown with Automatic, Token Budget, and Adaptive options. The max tokens field automatically hides when Adaptive is selected since it’s not applicable.
Adaptive mode enhancements: Added xhigh and max reasoning effort levels. Adaptive mode will auto-select for Bedrock’s Claude Opus and Sonnet 4.6+ models, with Opus 4.7 defaulting to xhigh.
Bedrock middleware: Intercepts adaptive-thinking Converse requests and rewrites them to properly set thinking.type=adaptive and output_config.effort.
Model metadata & docs: Added Claude Opus 4.7 to Bedrock’s model metadata and updated the corresponding documentation.
Backward compatibility: Existing budget-based reasoning setups continue to work exactly as they do now, so there are no breaking changes.

Closes #

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Configuration change
• 🧪 Test update
• 🛡️ Security update

Areas Affected

• Core Services (Frontend UI/Backend API)
• AI Agents (Researcher/Developer/Executor)
• Security Tools Integration
• Memory System (Vector Store/Knowledge Base)
• Monitoring Stack (Grafana/OpenTelemetry)
• Analytics Platform (Langfuse)
• [ x] External Integrations (LLM/Search APIs)
• [ x] Documentation
• Infrastructure/DevOps

Testing and Verification

Test Configuration

PentAGI Version: Latest Release (2.0)
Docker Version: Docker version 29.3.1, build c2be9cc
Host OS: Ubuntu 24.04.4 LTS on WSL2
LLM Provider: AWS Bedrock, Claude Opus 4.7
Enabled Features: Langfuse and Grafana

Test Steps

1. Built and ran a local PentAGI image.
2. Configured AWS Bedrock with us.anthropic.claude-opus-4-7.
3. Selected Reasoning Mode: Adaptive and a reasoning effort value in /settings/providers.
4. Ran provider/agent tests from the settings UI.
5. Verified the original Bedrock 400 validation error no longer occurs.
6. Ran focused backend, frontend, formatting, and lint validation.

Test Results

Passed:
cd backend
go test ./pkg/providers/bedrock ./pkg/providers/pconfig ./pkg/database/converter ./pkg/graph
go vet ./pkg/providers/bedrock ./pkg/providers/pconfig ./pkg/database/converter ./pkg/graph

cd frontend
npm run build
npm run test
npx prettier --check src/pages/settings/settings-provider.tsx src/graphql/types.ts graphql-schema.graphql
npx eslint src/pages/settings/settings-provider.tsx

Security Considerations

No new dependencies, credentials, permissions, or environment variables are introduced.

The Bedrock request rewrite only changes the serialized Converse request body for calls explicitly configured with
Adaptive reasoning mode. It does not log request bodies or expose provider secrets.

Performance Impact

Runtime overhead is minimal: adaptive Bedrock calls perform one small JSON body rewrite before the AWS SDK sends the request.

Model-side performance may vary because adaptive thinking lets Claude choose reasoning depth based on task complexity.
This can change latency and output token usage compared with a fixed reasoning token budget.

Documentation Updates

• README.md updates
• API documentation updates
• Configuration documentation updates
• GraphQL schema updates
• Other:

Deployment Notes

No migration or environment variable changes are required.
Existing provider configs remain backward compatible. Configs without reasoning.mode keep the previous behavior. For Claude Opus 4.7 on Bedrock, select Reasoning Mode: Adaptive and configure Reasoning Effort instead of Reasoning Max Tokens.

Checklist

Code Quality

• My code follows the project's coding standards
• I have added/updated necessary documentation
• I have added tests to cover my changes
• All new and existing tests pass
• I have run go fmt and go vet (for Go code)
• I have run npm run lint (for TypeScript/JavaScript code)

Security

• I have considered security implications
• Changes maintain or improve the security model
• Sensitive information has been properly handled

Compatibility

• Changes are backward compatible
• Breaking changes are clearly marked and documented
• Dependencies are properly updated

Documentation

• Documentation is clear and complete
• Comments are added for non-obvious code
• API changes are documented

Additional Notes

[asdek]

hey @kernelalex
thank you for the PR! we moved your changes by cherry-pick to the main branch.

also, the actual main branch and the latest docker image tag have changes for supporting opus-4.x, opus-5, sonnet-5 and fable-5 anthropic models, please check the code state