You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
opencode forces using Amazon Bedrock when AWS_PROFILE env var is set #242
Was very confused why the docs said this can work with Claude Pro/Max subscription because it would only ever use Amazon Bedrock. Had to find out by trial and error that I need to unset AWS_PROFILE in order for it to show the provider configuration screen.
This behavior seems weird to me - why would AWS users always want to use Amazon Bedrock?
No - I think because I had no other providers configured.
I see now that you have to run “open opencode login” to add more providers. When I tried this morning I expected that everything could be done interactively just by running “opencode” - didn’t think to check for sub-commands.
Activity
thdxr commentedon Jun 20, 2025
when you had it set and you opened the model selector were you able to press left/right to see the other providers that loaded?
jahands commentedon Jun 20, 2025
No - I think because I had no other providers configured.
I see now that you have to run “open opencode login” to add more providers. When I tried this morning I expected that everything could be done interactively just by running “opencode” - didn’t think to check for sub-commands.
So I suppose this is user error
Merge branch 'shuvcode-dev' into integration
Merge pull request anomalyco#242 from t-s-li/fix/observe-hook-phase-d…
feat: guide owpenwork setup flow (anomalyco#242)