Skip to content

Default path for CLI install on Windows with Bash does not exist, but script does not fail #4851

@rajbos

Description

@rajbos

Describe the bug

Default path is used from bash, in my case /home/rob/.local/bin/goose.exe. This does not translate to anything in Windows, and the installation docs show that you need to load the .local path, so when I do so goose is still not available.

Warning: Goose installed, but /home/rob/.local/bin is not in your PATH.
Add it to your PATH by editing ~/.bashrc, ~/.zshrc, or similar:
    export PATH="/home/rob/.local/bin:$PATH"
Then reload your shell (e.g. 'source ~/.bashrc', 'source ~/.zshrc') to apply changes.

To Reproduce
Steps to reproduce the behavior:

  1. Run the install script with bash curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash
  2. Follow the docs to update the path (shows to use .local)
  3. Try to run goose and fail
goose: The term 'goose' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Expected behavior
Use a path that exists and things might start to work 😄.

Metadata

Metadata

Assignees

Labels

hacktoberfestIssues awarding points for Hacktoberfest 2025!mediumWeight label for Hacktoberfest 2025 issuesp2Priority 2 - Mediumwindows

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions