Slow startup when AWS_PROFILE is set

[Biacode]

Description

When you have AWS_PROFILE env var it assumes you gonna use AWS bedrock and the CLI starts ethernity

Plugins

doesn't matter

OpenCode version

v1.1.11

Steps to reproduce

1, Set AWS_PROFILE
2. Open opencode
3. see it takes too long to start

Screenshot and/or share link

No response

Operating System

Linux Ubuntu 22.04

Terminal

Gnome terminal, Ghosy, no matter what

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Infinite installation loop of @aws-sdk/credential-providers on startup when AWS_BEARER_TOKEN_BEDROCK is set #6765: Infinite installation loop of @aws-sdk/credential-providers on startup when AWS_BEARER_TOKEN_BEDROCK is set
• opencode forces using Amazon Bedrock when AWS_PROFILE env var is set #242: opencode forces using Amazon Bedrock when AWS_PROFILE env var is set

Feel free to ignore if none of these address your specific case.

[Biacode]

as a fix

alias opencode='AWS_PROFILE= BUN_TMPDIR=$HOME/.opencode/tmp opencode'

[Biacode]

OpenCode runs this command on every startup:
bun add --force --exact --cwd ~/.cache/opencode @aws-sdk/credential-providers@latest

This causes:

• --force bypasses the local cache
• @latest requires npm registry lookup
• ~30 second delay even with packages already installed

Log Evidence

INFO +0ms service=bun cmd=["opencode","add","--force","--exact","--cwd","/home/user/.cache/opencode","@aws-sdk/credential-providers@latest"]
INFO +29183ms service=bun code=143 stdout=bun add v1.3.5 ... stderr=Resolving dependencies

Root Cause

OpenCode's provider detection sees AWS_PROFILE → assumes user wants AWS Bedrock → installs AWS SDK with --force flag on every startup, defeating caching.

Workaround

AWS_PROFILE= opencode