Skip to content

feat(bedrock): catalog Amazon Nova 2 Lite for Bedrock US - #155

Open
micahwalter wants to merge 9 commits into
charmbracelet:mainfrom
micahwalter:feature/amazon-nova-bedrock-support
Open

feat(bedrock): catalog Amazon Nova 2 Lite for Bedrock US#155
micahwalter wants to merge 9 commits into
charmbracelet:mainfrom
micahwalter:feature/amazon-nova-bedrock-support

Conversation

@micahwalter

@micahwalter micahwalter commented Jan 16, 2026

Copy link
Copy Markdown

Summary

Catalog Amazon Nova 2 Lite for the Bedrock US provider so Crush can list and select it.

This PR is ready for another review pass. Since the last update we:

  • Rebased onto the Bedrock US/EU split (bedrock-united-states.json)
  • Narrowed scope from four Gen 1 Nova models to Nova 2 Lite only
  • Merged main and are current with upstream
  • Validated with Crush end-to-end (model picker + thinking toggle)

Companion PR: fantasy#117

What changed

Added

  • amazon.nova-2-lite-v1:0 — Amazon Nova 2 Lite
    • 1M context window
    • default_max_tokens: 64,000
    • can_reason: true (extended thinking via Bedrock reasoningConfig)
    • Supports attachments

Removed (from original PR scope)

  • amazon.nova-pro-v1:0
  • amazon.nova-lite-v1:0
  • amazon.nova-micro-v1:0
  • amazon.nova-premier-v1:0

Why only Nova 2 Lite?

AWS Bedrock lifecycle (July 2026):

Model Status Catalog?
Nova 2 Lite Active, recommended successor Yes
Nova Pro/Lite/Micro (Gen 1) Active but superseded No
Nova Premier Legacy, EOL Sept 14, 2026 No

Fantasy still routes any amazon.* model if a user adds it manually in Crush config; this PR only defines what Crush lists by default.

Test plan

  • go test ./internal/providers/... -run Nova
  • Assert exactly one Nova model in Bedrock US config
  • Assert Gen 1 Nova IDs are not cataloged
  • Crush shows Amazon Nova 2 Lite under Bedrock after update-providers embedded
  • Maintainer confirms pricing/metadata against current Bedrock docs

Checklist

  • I have read CONTRIBUTING.md.
  • I have created a discussion that was approved by a maintainer (for new features).

- Add amazon.nova-pro-v1:0 with 300K context, image support
- Add amazon.nova-lite-v1:0 with 300K context, image support
- Add amazon.nova-micro-v1:0 with 128K context, no image support
- Add amazon.nova-premier-v1:0 with 300K context, reasoning capability
- Include accurate pricing for all Nova models
- Add comprehensive property and unit tests for Nova model configurations
- Update .gitignore to exclude .kiro directory

Validates requirements 2.1-2.6 from amazon-nova-bedrock-support spec
- Add amazon.nova-2-lite-v1:0 with can_reason: true (supports reasoningConfig API)
- Set amazon.nova-premier-v1:0 can_reason: false (original Nova models don't support reasoningConfig)
- Nova 2 Lite: 1M token context, 10k max tokens, $0.06/$0.24 per 1M tokens

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@micahwalter

Copy link
Copy Markdown
Author

Added a commit here for Nova 2 Lite and Premiere reasoning

micahwalter and others added 4 commits July 8, 2026 14:30
Rebases the Nova model definitions onto the split bedrock-united-states
layout and corrects extended thinking metadata for Nova 2 Lite only.

Co-authored-by: Cursor <cursoragent@cursor.com>
Remove legacy Gen 1 Nova entries including Premier, keep Nova 2 Lite
as the sole Bedrock Nova model with extended thinking metadata.

Co-authored-by: Cursor <cursoragent@cursor.com>
Bring branch current with upstream before PR update.
@micahwalter micahwalter changed the title feat: Add Amazon Nova model definitions to Bedrock provider feat(bedrock): catalog Amazon Nova 2 Lite for Bedrock US Jul 9, 2026
@micahwalter

Copy link
Copy Markdown
Author

Update for maintainers — branch is current with main and ready for another review.

Since the original PR:

  • Rebased onto the Bedrock US/EU provider split
  • Narrowed catalog to Nova 2 Lite only (dropped Gen 1 Nova + Legacy Premier)
  • Merged latest upstream main
  • Tests pass: go test ./internal/providers/... -run Nova

Pairs with fantasy#117 for full Crush support.

Open to adding back Gen 1 models as legacy entries if maintainers prefer broader catalog coverage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants