Failed to create provider: Unknown provider: bedrock

[Dan-Wuensch]

Describe the bug

Our code to run goose headlessly using "bedrock" as the provider stopped working this week. We're getting the following error:

Downloading stable release: goose-x86_64-unknown-linux-gnu.tar.bz2...
Extracting goose-x86_64-unknown-linux-gnu.tar.bz2...
Moving goose to /home/runner/.local/bin/goose
Skipping 'goose configure', you may need to run this manually later
thread 'main' panicked at /home/runner/work/goose/goose/crates/goose-cli/src/session/builder.rs:32:64:
Failed to create provider: Unknown provider: bedrock
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

To Reproduce

mkdir -p /home/runner/.local/bin
curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | CONFIGURE=false INSTALL_PATH=/home/runner/.local/bin bash
echo "/home/runner/.local/bin" >> $GITHUB_PATH

mkdir -p ~/.config/goose
cat <<EOF > ~/.config/goose/config.yaml
GOOSE_PROVIDER: bedrock
GOOSE_MODEL: us.anthropic.claude-3-7-sonnet-20250219-v1:0
keyring: false
extensions:
   developer:
      enabled: true
      name: developer
      type: builtin
EOF

        
echo "$ENHANCED_CONTENT" >> instructions.txt
goose run --instructions instructions.txt | \

Expected behavior
goose runs using the config file and provider bedrock

Screenshots
If applicable, add screenshots to help explain your problem.

Please provide following information:

• OS & Arch: GitHub Action Runner 2.322.0
• Interface: CLI
• Version: latest via Curl download and install command
• Extensions enabled: developer
• Provider & Model: bedrock, us.anthropic.claude-3-7-sonnet-20250219-v1:0

Additional context
Running as part of CI/CD pipeline

[Dan-Wuensch]

Could this be related to a change in the last week, for example #1563

[Dan-Wuensch]

Downgrading to v1.0.14 resolves this issue, likely introduced since. We're using this as a workaround for now. We were having problems installing earlier versions using the installer SH file so had to copypasta the contents of the installer and use the parts we needed along with a download path, ex. https://github.com/block/goose/releases/download/v1.0.14/goose-x86_64-unknown-linux-gnu.tar.bz2.

Keeping this issue open so that we can take latest updates again once fixed.

Curious about recommended approach for pinning a specific version as well to avoid breaking changes in any critical consuming workflows

[bryan-valant]

ran into same today. reverting to 1.0.14 got me running again.

[laanak08]

the problem is that "bedrock" is not a registered provider in the codebase. the codebase uses "aws_bedrock" instead.
see here

for implementer: either add bedrock as an alias to "aws_bedrock" or update documentation to direct users to use "aws_bedrock" instead.

[Dan-Wuensch]

@laanak08 thanks, we were going off of this list originally:

goose/crates/goose/src/providers/mod.rs

Line 4 in 9447b79

pub mod bedrock;

I couldn't find the list of valid provider options in documentation anywhere so tried to use values from source. Would be a good thing to include in the section about CI/CD use of goose.

Anyways, we tried to switch back to the latest goose version and change GOOSE_PROVIDER from bedrock to aws_bedrock but got the following error:

thread 'main' panicked at /home/runner/work/goose/goose/crates/goose-cli/src/session/builder.rs:32:64:
  Failed to create provider: Failed to access keyring: Platform secure storage failure: DBus error: The name org.freedesktop.secrets was not provided by any .service files

[zakiali]

@Dan-Wuensch the latest error you're seeing should be fixed with #1886, which we'll get into the next release

edit: this has merged, closing issue

[gaurav219]

Downgrading to v1.0.14 resolves this issue, likely introduced since. We're using this as a workaround for now. We were having problems installing earlier versions using the installer SH file so had to copypasta the contents of the installer and use the parts we needed along with a download path, ex. https://github.com/block/goose/releases/download/v1.0.14/goose-x86_64-unknown-linux-gnu.tar.bz2.

Keeping this issue open so that we can take latest updates again once fixed.

Curious about recommended approach for pinning a specific version as well to avoid breaking changes in any critical consuming workflows

Even after downgrading, I'm experiencing the same issue. I'm using openrouter as the provider.

thread 'main' panicked at /home/runner/work/goose/goose/crates/goose-cli/src/session/builder.rs:32:64:
Failed to create provider: Failed to access keyring: Platform secure storage failure: DBus error: The name org.freedesktop.secrets was not provided by any .service files

Stage output -

Run mkdir -p /home/runner/.local/bin
  mkdir -p /home/runner/.local/bin
  # Download specific version 1.0.14 of Goose CLI
  curl -fsSL -o goose.tar.bz2 https://github.com/block/goose/releases/download/v1.0.14/goose-x86_64-unknown-linux-gnu.tar.bz2
  # Extract the archive
  tar -xjf goose.tar.bz2
  # Move the binary to the local bin directory
  chmod +x goose
  mv goose /home/runner/.local/bin/
  # Add to path
  echo "/home/runner/.local/bin" >> $GITHUB_PATH
  # Verify installation
  goose --version
  shell: /usr/bin/bash -e {0}
  env:
    GH_TOKEN: ***
    RUST_BACKTRACE: 1
    PROVIDER_API_KEY: ***
    PR_NUMBER: 1
  
 1.0.14

[gaurav219]

Nvm, I figured it out.

Anyone facing this issue, make sure you're using provider's LLM API Key name as mentioned here.

[lukasjuhas]

Thank you @gaurav219, you saved me from a headache.

[Dan-Wuensch]

Confirmed working as expected on latest version! Thanks all