Signed-off-by: Michael Neale <michael.neale@gmail.com> Co-authored-by: Michael Neale <michael.neale@gmail.com> continuing migration to aaif
17 KiB
| sidebar_position |
|---|
| 1 |
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import { RateLimits } from '@site/src/components/RateLimits'; import { OnboardingProviderSetup } from '@site/src/components/OnboardingProviderSetup'; import { ModelSelectionTip } from '@site/src/components/ModelSelectionTip'; import MacDesktopInstallButtons from '@site/src/components/MacDesktopInstallButtons'; import WindowsDesktopInstallButtons from '@site/src/components/WindowsDesktopInstallButtons'; import LinuxDesktopInstallButtons from '@site/src/components/LinuxDesktopInstallButtons'; import { PanelLeft } from 'lucide-react';
Install goose
Choose to install the Desktop and/or CLI version of goose:<Tabs groupId="interface">
<TabItem value="ui" label="goose Desktop" default>
Install goose Desktop directly from the browser or with [Homebrew](https://brew.sh/).
<h3 style={{ marginTop: '1rem' }}>Option 1: Install via Download</h3>
<MacDesktopInstallButtons/>
<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 periodically [update goose](/docs/guides/updating-goose).
:::
</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' }}>
:::info 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](/docs/troubleshooting/known-issues#macos-permission-issues)
:::
</div>
</TabItem>
<TabItem value="cli" label="goose CLI">
Install goose directly from the browser or with [Homebrew](https://brew.sh/).
<h3 style={{ marginTop: '1rem' }}>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
```
:::tip Updating goose
It's best to keep goose updated. To update goose, run:
```sh
goose update
```
:::
<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
```
</TabItem>
</Tabs>
Choose to install the Desktop and/or CLI version of goose:
<Tabs groupId="interface">
<TabItem value="ui" label="goose Desktop" default>
Install goose Desktop directly from the browser.
<h3 style={{ marginTop: '1rem' }}>Install via Download</h3>
<LinuxDesktopInstallButtons/>
<div style={{ marginTop: '1rem' }}>
**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
:::tip Updating goose
It's best to periodically [update goose](/docs/guides/updating-goose).
:::
</div>
</TabItem>
<TabItem value="cli" label="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
```
:::tip Updating goose
It's best to keep goose updated. To update goose, run:
```sh
goose update
```
:::
</TabItem>
</Tabs>
Choose to install the Desktop and/or CLI version of goose:
<Tabs groupId="interface">
<TabItem value="ui" label="goose Desktop" default>
Install goose Desktop directly from the browser.
<h3 style={{ marginTop: '1rem' }}>Install via Download</h3>
<WindowsDesktopInstallButtons/>
<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 periodically [update goose](/docs/guides/updating-goose).
:::
</div>
</TabItem>
<TabItem value="cli" label="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
Run the installation command in your chosen environment:
```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:**
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
```
:::info 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.
:::
<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
```
:::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/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>
</TabItem>
</Tabs>
Set LLM Provider
goose works with supported LLM 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.
On the welcome screen the first time you open goose, choose how to configure a provider: 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.
:::info 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:
echo 'export OPENAI_API_KEY=your_api_key' >> ~/.bashrc
source ~/.bashrc
:::
:::tip :::
:::info 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. :::
Update Provider
You can change your LLM provider and/or model or update your API key at any time.
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](/docs/getting-started/providers#configure-provider-and-model). 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, 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 guide.
:::info 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. :::
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. 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 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:
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 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.