Skip to content

fix(cli): display platform-correct secrets path in keyring config dialog#8328

Merged
michaelneale merged 1 commit into
aaif-goose:mainfrom
SushaanthSrinivasan:fix/configure-secrets-path-display
Apr 6, 2026
Merged

fix(cli): display platform-correct secrets path in keyring config dialog#8328
michaelneale merged 1 commit into
aaif-goose:mainfrom
SushaanthSrinivasan:fix/configure-secrets-path-display

Conversation

@SushaanthSrinivasan
Copy link
Copy Markdown
Contributor

@SushaanthSrinivasan SushaanthSrinivasan commented Apr 5, 2026

Summary

  • The keyring configuration dialog in goose configure hardcoded ~/.config/goose/secrets.yaml in warning and confirmation messages
  • This path is only correct on Linux — on Windows the actual path is C:\Users\<user>\AppData\Roaming\Block\goose\config\secrets.yaml, on macOS it's ~/Library/Application Support/Block/goose/
  • Replaced hardcoded string with Paths::config_dir().join("secrets.yaml"), which is already imported and used elsewhere in the same file

Fixes #8326

Before / After

Before (hardcoded Unix path on Windows):
old

After (correct platform path):
new

Test plan

  • Built and tested on Windows 11 — path now shows correct platform path
  • Compilation verified on Linux (WSL) via cargo check

The keyring configuration dialog hardcoded `~/.config/goose/secrets.yaml`
in its warning and confirmation messages. This path is only correct on
Linux. On Windows and macOS, the actual secrets file is in a different
location determined by the platform's config directory conventions.

Replace the hardcoded string with `Paths::config_dir().join("secrets.yaml")`
which is already imported and used elsewhere in the same file.

Fixes aaif-goose#8326

Signed-off-by: SushaanthSrinivasan <SushaanthSrinivasan@users.noreply.github.com>
@SushaanthSrinivasan SushaanthSrinivasan force-pushed the fix/configure-secrets-path-display branch from 69aa402 to c907fa3 Compare April 5, 2026 19:32
@michaelneale michaelneale added this pull request to the merge queue Apr 6, 2026
@michaelneale
Copy link
Copy Markdown
Collaborator

thanks @SushaanthSrinivasan

Merged via the queue into aaif-goose:main with commit e8c66f8 Apr 6, 2026
24 checks passed
lifeizhou-ap added a commit that referenced this pull request Apr 7, 2026
* origin/main: (32 commits)
  docs: rework homepage and add aaif migration blog post (#8356)
  chore(aaif): rename a bunch of repository references (#8152)
  fix: use OPENAI_API_KEY secret for recipe security scanner (#8358)
  feat: configurable extension timeouts via ACP _meta and global default (#8295)
  fix: hide hidden extensions in UI (#8346)
  refactor: skills as its own platform ext (#8244)
  fix baseUrl (#8347)
  Fix desktop slash commands (#8341)
  fix(cli): display platform-correct secrets path in keyring config dialog (#8328)
  feat(acp): add reusable ACP provider controls (#8314)
  fix: resolve MDX compilation error in using-goosehints.md (#8332)
  fix: use v1beta1 API version for Google/MaaS models on GCP Vertex AI (#8278)
  docs: add MCP Roots guide (#8252)
  rust acp client for extension methods (#8227)
  fix: reconsolidate split tool-call messages to follow OpenAI format (#7921)
  fix: clean up MCP subprocesses after abrupt parent exit (#8242)
  build: raise default stack reserve to 8 MB (#8234)
  fix(config): honour GOOSE_DISABLE_KEYRING from config.yaml at startup (#8219)
  feat: add configurable fast_model for declarative providers (#8194)
  fix(authentication): Allow connecting to Oauth servers that use protected-resource fallback instead of the WWW-authenticate header (#8148)
  ...
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.

fix(cli): keyring config dialog shows hardcoded Unix path instead of platform-specific secrets path

2 participants