-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
enhancementNew feature or requestNew feature or request
Description
What problem does this solve?
Model Usage Limits
The agent can change models if one stops responding due to limits.
Multiple Accounts
The same (or different models) with differing accounts can be used to spread usage across accounts.
Fallback to Local
A fallback to local models. For example, the main model stop responding, the reporting agent can still produce a report using a local model.
Proposed solution
- Create a Strands Model class that contains a list of models.
- Change configuration to specify multiple models, API keys, etc.
- When a model errors, mark as disabled and move on to another model.
- Try disabled models again after a cool down period.
- Some model properties need to be moved from the agent into the model and expect to change, ex: allow_reasoning.
- conversation compression will need to be adaptive to the underlying model properties
- Memory embedder will need to stay consistent.
Alternatives considered
No response
Which area does this affect?
Agent/Tools
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request