# Install goose

> Choose to install the Desktop and/or CLI version of goose:

- 网址：https://funcoding.ai/agents/goose/getting-started/installation/
- 来源：goose 官方文档原文（英文），Apache-2.0 许可，同步于 2026-10-11
- 官方原文：https://goose-docs.ai/docs/getting-started/installation

---
**macOS**

Choose to install the Desktop and/or CLI version of goose:

**goose Desktop**

Install goose Desktop directly from the browser or with [Homebrew](https://brew.sh/).

<h3>Option 1: Install via Download</h3>

<div>
  1. Unzip the downloaded zip file.
  2. Run the executable file to launch the goose Desktop application.

<div class="callout callout-tip">

**Updating goose**

It's best to periodically [update goose](https://funcoding.ai/agents/goose/guides/updating-goose/).

</div>

</div>
<h3>Option 2: Install via Homebrew</h3>
Homebrew downloads the [same app](https://github.com/Homebrew/homebrew-cask/blob/master/Casks/b/block-goose.rb) but can take care of updates too.
```bash
brew install --cask block-goose
```
---
<div>

<div class="callout callout-note">

**Permissions**

If you're on an Apple Mac M3 and the goose Desktop app shows no window on launch, check and update the following:

Ensure the `~/.config` directory has read and write access.

goose needs this access to create the log directory and file. Once permissions are granted, the app should load correctly. For steps on how to do this, refer to the  [Known Issues Guide](https://funcoding.ai/agents/goose/troubleshooting/known-issues/#macos-permission-issues)

</div>

</div>

**goose CLI**

Install goose directly from the browser or with [Homebrew](https://brew.sh/).

<h3>Option 1: Install via Download script</h3>
Run the following command to install the latest version of goose on macOS:

```sh
curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | bash
```
This script will fetch the latest version of goose and set it up on your system.

If you'd like to install without interactive configuration, disable `CONFIGURE`:

```sh
curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash
```

<div class="callout callout-tip">

**Updating goose**

It's best to keep goose updated. To update goose, run:
```sh
goose update
```

</div>

<h3>Option 2: Install via Homebrew</h3>
Homebrew downloads the [a precompiled CLI tool](https://github.com/Homebrew/homebrew-core/blob/master/Formula/b/block-goose-cli.rb) and can take care of updates.
```bash
brew install block-goose-cli
```

**Linux**

Choose to install the Desktop and/or CLI version of goose:

**goose Desktop**

Install goose Desktop directly from the browser.

<h3>Install via Download</h3>

<div>
  **For Debian/Ubuntu-based distributions:**
  1. Download the DEB file
  2. Navigate to the directory where it is saved in a terminal
  3. Run `sudo dpkg -i (filename).deb`
  4. Launch goose from the app menu

<div class="callout callout-tip">

**Updating goose**

It's best to periodically [update goose](https://funcoding.ai/agents/goose/guides/updating-goose/).

</div>

</div>

**goose CLI**

Run the following command to install the goose CLI on Linux:

```sh
curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | bash
```
This script will fetch the latest version of goose and set it up on your system.

If you'd like to install without interactive configuration, disable `CONFIGURE`:

```sh
curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash
```

<div class="callout callout-tip">

**Updating goose**

It's best to keep goose updated. To update goose, run:
```sh
goose update
```

</div>

**Windows**

Choose to install the Desktop and/or CLI version of goose:

**goose Desktop**

Install goose Desktop directly from the browser.

<h3>Install via Download</h3>

<div>
  1. Unzip the downloaded zip file.
  2. Run the executable file to launch the goose Desktop application.

<div class="callout callout-tip">

**Updating goose**

It's best to periodically [update goose](https://funcoding.ai/agents/goose/guides/updating-goose/).

</div>

</div>

**goose CLI**

To install goose natively on Windows, you need one of the following environments:
- **Git Bash** (recommended): Comes with [Git for Windows](https://git-scm.com/download/win)
- **MSYS2**: Available from [msys2.org](https://www.msys2.org/)
- **PowerShell**: Available on Windows 10/11 by default

**Git Bash / MSYS2: Standard**

```bash
curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | bash
```

To install without interactive configuration, disable `CONFIGURE`:

```bash
curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash
```

**PowerShell Installation: Standard**
Download the PowerShell installation script to your current directory.

```powershell
Invoke-WebRequest -Uri "https://raw.githubusercontent.com/aaif-goose/goose/main/download_cli.ps1" -OutFile "download_cli.ps1";
```
Then run the script to install goose:
```powershell
.\download_cli.ps1
```

<div class="callout callout-note">

**Windows PATH Setup**

If you see a warning that goose is not in your PATH, you need to add goose to your PATH:

<details>
  <summary>For Git Bash/MSYS2</summary>
  ```bash
  echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
  source ~/.bashrc
  ```
</details>

<details>
  <summary>For PowerShell</summary>
  ```powershell
  # Add to your PowerShell profile
  $profilePath = $PROFILE
  if (!(Test-Path $profilePath)) { New-Item -Path $profilePath -ItemType File -Force }
  Add-Content -Path $profilePath -Value '$env:PATH = "$env:USERPROFILE\.local\bin;$env:PATH"'
  # Reload profile or restart PowerShell
  . $PROFILE
  ```
</details>

After updating your PATH, you can run `goose` commands from any directory.

</div>

<details>
<summary>Install via Windows Subsystem for Linux (WSL)</summary>

  We recommend running the goose CLI natively on Windows, but you can use WSL if you prefer a Linux-like environment.

  1. Open [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows) as Administrator and install WSL and the default Ubuntu distribution:

  ```bash
  wsl --install
  ```

  2. If prompted, restart your computer to complete the WSL installation. Once restarted, or if WSL is already installed, launch your Ubuntu shell by running:

  ```bash
  wsl -d Ubuntu
  ```

  3. Run the goose installation script:
  ```bash
  curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | bash
  ```

<div class="callout callout-tip">

If you encounter any issues on download, you might need to install `bzip2` to extract the downloaded file:

```bash
sudo apt update && sudo apt install bzip2 -y
```

</div>

  If you'd like to install without interactive configuration, disable `CONFIGURE`:

  ```sh
  curl -fsSL https://github.com/aaif-goose/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash
  ```

  If needed, add goose to your path:

  ```
  echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
  echo 'export OPENAI_API_KEY=your_api_key' >> ~/.bashrc
  source ~/.bashrc
  ```

</details>

## Set LLM Provider
goose works with [supported LLM providers][providers] that give goose the AI intelligence it needs to understand your requests. On first use, you'll be prompted to configure your preferred provider.

**goose Desktop**

On the welcome screen the first time you open goose, choose how to configure a provider:

**goose CLI**

  The CLI automatically enters configuration mode where you can choose how to configure a provider:

  - **OpenRouter Login** - Sign in with OpenRouter to automatically configure models
  - **Tetrate Agent Router Service Login** - Sign in with Tetrate Agent Router Service to automatically configure models
  - **Manual Configuration** - Choose a provider and enter credentials manually

  Example configuration flow:

  ```
  ┌   goose-configure
  │
  ◇ How would you like to set up your provider?
  │ Tetrate Agent Router Service Login
  │
  Opening browser for Tetrate Agent Router Service authentication...
  [goose opens the browser and prints details]

  Authentication complete!

  Configuring Tetrate Agent Router Service...
  ✓ Tetrate Agent Router Service configuration complete
  ✓ Models configured successfully

  Testing configuration...
  ✓ Configuration test passed!
  ✓ Developer extension enabled!
  └ Tetrate Agent Router Service setup complete! You can now use goose.
```

<div class="callout callout-note">

**Windows Users**

If you choose to manually configure a provider, when prompted during configuration, choose to not store to keyring. If you encounter keyring errors when setting API keys, you can set environment variables manually instead:

```bash
export OPENAI_API_KEY={your_api_key}
```

Then run `goose configure` again. goose will detect the environment variable and display:

```
● OPENAI_API_KEY is set via environment variable
```

To make API keys persist across sessions, add them to your shell profile:
```bash
echo 'export OPENAI_API_KEY=your_api_key' >> ~/.bashrc
source ~/.bashrc
```

</div>

<div class="callout callout-tip">

</div>

<div class="callout callout-note">

**Free Credits Offer**

You'll receive $10 in free credits the first time you automatically authenticate with Tetrate through goose. This offer is available to both new and existing Tetrate users.

</div>

## Update Provider
You can change your LLM provider and/or model or update your API key at any time.

**goose Desktop**

1. Click the  button in the top-left to open the sidebar.
2. Click the `Settings` button on the sidebar.
3. Click the `Models` tab.
4. Choose to update your provider, switch models, or click `Reset Provider and Model` to clear your settings and return to the welcome screen. See details about these [configuration options](https://funcoding.ai/agents/goose/getting-started/providers/#configure-provider-and-model).

**goose CLI**

1. Run the following command:
```sh
goose configure
```
2. Select `Configure Providers` from the menu.
3. Follow the prompts to choose your LLM provider and enter or update your API key.

**Example:**

To select an option during configuration, use the up and down arrows to highlight your choice then press Enter.

```
┌   goose-configure
│
◇ What would you like to configure?
│ Configure Providers
│
◇ Which model provider should we use?
│ Google Gemini
│
◇ Provider Google Gemini requires GOOGLE_API_KEY, please enter a value
│▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
│
◇ Enter a model from that provider:
│ gemini-2.0-flash-exp
│
◇  Hello there! You're all set to use me, so please ask away!
│
└  Configuration saved successfully
```

## Running goose

**goose Desktop**

Starting a session in the goose Desktop is straightforward. After choosing your provider, you'll see the session interface ready for use.

Type your questions, tasks, or instructions directly into the input field, and goose will get to work immediately.

**goose CLI**

From your terminal, navigate to the directory you'd like to start from and run:
```sh
goose session
```

## Shared Configuration Settings

The goose CLI and Desktop UI share all core configurations, including LLM provider settings, model selection, and extension configurations. When you install or configure extensions in either interface, the settings are stored in a central location, making them available to both the Desktop application and CLI. This makes it convenient to switch between interfaces while maintaining consistent settings. For more information, visit the [Config Files][config-files] guide.

<div class="callout callout-note">

While core configurations are shared between interfaces, extensions have flexibility in how they store authentication credentials. Some extensions may use the shared config files while others implement their own storage methods.

</div>

**goose Desktop**

Navigate to shared configurations through:
1. Click the  button in the top-left to open the sidebar.
2. Click the `Settings` button on the sidebar.

**goose CLI**

Use the following command to manage shared configurations:
```sh
goose configure
```

## Pin a goose version in CI/CD
In CI/CD (and other automated, non-interactive environments), pin a specific version with `GOOSE_VERSION` to make installs reproducible and avoid 404s when downloading the goose CLI binary assets if the `stable` release tag doesn’t include them.

See [CI/CD Environments](https://funcoding.ai/agents/goose/tutorials/cicd/) for a complete example and usage details.

## Generate manpages for Linux distributions

If you're packaging goose for a Linux distribution or creating a custom build, you can generate Unix manpages from the CLI command definitions:

```bash
just generate-manpages
```

This creates ROFF-formatted manpages in `target/man/` (e.g., `goose.1`, `goose-session.1`) that can be installed to `/usr/share/man/man1/` to provide offline documentation via the `man` command.

Manpage generation requires the goose source repository and is intended for distribution packagers preparing packages for Fedora, Debian, and other Linux distributions. See the [generate_manpages.rs source](https://github.com/aaif-goose/goose/blob/main/crates/goose-cli/src/bin/generate_manpages.rs) for implementation details.

## Additional Resources

You can also configure Extensions to extend goose's functionality, including adding new ones or toggling them on and off. For detailed instructions, visit the [Using Extensions Guide][using-extensions].

[using-extensions]: /agents/goose/getting-started/using-extensions/
[providers]: /agents/goose/getting-started/providers/
[handling-rate-limits]: /agents/goose/guides/handling-llm-rate-limits-with-goose/
[mcp]: https://www.anthropic.com/news/model-context-protocol
[config-files]: /agents/goose/guides/config-files/
