goose/documentation/docs/getting-started/installation.md

sidebar_position

sidebar_position
1

import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import SupportedEnvironments from '@site/src/components/SupportedEnvironments'; import RateLimits from '@site/src/components/RateLimits'; import DesktopInstallButtons from '@site/src/components/DesktopInstallButtons';

Install Goose

Choose to install Goose on CLI and/or Desktop:

<Tabs groupId="interface">
  <TabItem value="ui" label="Goose Desktop" default>
    Install Goose directly from the browser or with [Homebrew](https://brew.sh/).
    
    <h3 style={{ marginTop: '1rem' }}>Option 1: Install via Download</h3>
    <DesktopInstallButtons/>

    <div style={{ marginTop: '1rem' }}>
      1. Unzip the downloaded zip file.
      2. Run the executable file to launch the Goose desktop application.

      :::tip Updating Goose
      It's best to keep Goose updated by periodically running the installation steps again.
      :::
    </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 style={{ marginTop: '1rem' }}>
      :::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  [Troubleshooting Guide](/docs/troubleshooting.md#macos-permission-issues)
      :::
    </div>
  </TabItem>
  <TabItem value="cli" label="Goose CLI">
    Run the following command to install the latest version of Goose on macOS:

    ```sh
    curl -fsSL https://github.com/block/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/block/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash
    ```

    :::tip Updating Goose
    It's best to keep Goose updated. To update Goose, run:
    ```sh
    goose update
    ```
    :::
  </TabItem>
</Tabs>

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

```sh
curl -fsSL https://github.com/block/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/block/goose/releases/download/stable/download_cli.sh | CONFIGURE=false bash
```   

There isn't native installation support for Windows, however you can run Goose using WSL (Windows Subsystem for Linux).

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. Restart your computer if prompted.

3. Run the Goose installation script:
```bash
curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash
```
:::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
  ```
:::

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

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

Set LLM Provider

Goose works with a set of supported LLM providers, and you'll need an API key to get started. When you use Goose for the first time, you'll be prompted to select a provider and enter your API key.

Upon installing, the Provider screen will appear. Here is where you can choose your LLM Provider.

![Set Up a Provider UI](../assets/guides/set-up-provider-ui.png)

Once selecting your provider, you'll be prompted to enter an API key if applicable. Do so, and click `Submit`.

Upon installing, Goose will automatically enter its configuration screen. Here is where you can set up your LLM provider.

:::tip Windows Users
Choose to not store to keyring when prompted.
:::

Example:

```
┌   goose-configure
│
◇ What would you like to configure?
│ Configure Providers
│
◇ Which model provider should we use?
│ OpenAI
│
◇ Provider openai requires OPENAI_API_KEY, please enter a value
│▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
│
◇ Enter a model from that provider:
│ gpt-4o
│
◇  Welcome aboard! You're all set to start using this agent—let's achieve great things together!
│
└  Configuration saved successfully

:::info Windows Users
On initial run, you may encounter errors about keyrings when setting your API Keys. Set the needed environment variables manually, e.g.:

```bash
export OPENAI_API_KEY={your_api_key}

To make the changes persist in WSL across sessions, add the goose path and export commands to your .bashrc or .bash_profile file so you can load it later.

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

:::

Update Provider

**To update your LLM provider and API key:**

1. Click on the three dots in the top-right corner.
2. Select `Provider Settings` from the menu.
2. Choose a provider from the list.
3. Click Edit, enter your API key, and click `Set as Active`.

**To update your LLM provider and API key:** 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

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.
</TabItem>
<TabItem value="cli" label="Goose CLI">
    From your terminal, navigate to the directory you'd like to start from and run:
    ```sh
    goose session
    ```
</TabItem>

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 at ~/.config/goose/config.yaml, making them available to both the Desktop application and CLI. This makes it convenient to switch between interfaces while maintaining consistent settings.

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

Navigate to shared configurations through: 1. Click `...` in the upper right corner 2. Click `Advanced Settings` Use the following command to manage shared configurations: ```sh goose configure ```

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.