Skip to main content
This guide walks you through installing GlooCode and connecting your Gloo AI credentials. The whole process takes about 5 minutes.

​
Prerequisites

Before you start, make sure you have:
  • macOS or Linux (ARM64 or x64) — see platform support below
  • A Gloo AI account — sign up here if you don’t have one
  • API credentials — you’ll create these in Step 2 below

​
Platform Support

GlooCode ships as a self-contained binary for macOS and Linux: No runtime dependencies are required. The installer detects your platform and downloads the correct binary.
Windows is not currently supported. Windows users can run GlooCode through WSL (Windows Subsystem for Linux) using the Linux binary.

​
Step 1: Install the Binary

Run the installer script. It detects your OS and architecture, downloads the correct binary, and adds it to your PATH.
The installer places the binary in your PATH (typically /usr/local/bin/gloocode on macOS) and updates your shell profile if needed.
Open a new terminal window after installing. Your current session won’t have the updated PATH until you do.
Verify it worked in a new terminal:
If you see a version number, the install succeeded. If you get “command not found”, see Troubleshooting below.

​
Step 2: Connect Your Credentials

GlooCode authenticates with the Gloo AI platform using OAuth2 client credentials (Client ID and Client Secret). This is different from the API key authentication used by other Gloo AI services — GlooCode is the only product that still uses client credentials. You create these credentials in Gloo AI Studio. When GlooCode sends a model request, it routes through Gloo AI — which handles provider selection, safety screening, and failover automatically. You don’t need to manage API keys for individual model providers.

​
Option A: Let GlooCode prompt you (easiest)

If you launch GlooCode without credentials configured, it will automatically prompt you to enter your Client ID and Client Secret interactively. Just run gloocode and follow the prompts.

​
Option B: Set environment variables

If you prefer to configure credentials ahead of time (or want them available to scripts and CI), add them to your shell profile (~/.zshrc, ~/.bashrc, or ~/.config/fish/config.fish):
Then open a new terminal or reload your shell:

​
Getting your credentials

If you don’t have credentials yet:
  1. Sign in to Gloo AI Studio
  2. Go to API Keys in the sidebar (or open it directly)
  3. Select the API Credentials tab
  4. Click Create New Key — copy both the Client ID and Client Secret
GlooCode cannot function without these credentials. Every model request routes through your Gloo AI account, so there is no way to skip this step.
If you don’t have a Gloo AI account yet, create one and set up billing to enable API access. The Developer Quickstart walks through account setup step by step.

​
Changing credentials later

To switch to different credentials, update the environment variables in your shell profile and open a new terminal. GlooCode reads credentials fresh on each launch.

​
Updating GlooCode

Re-run the installer to update to the latest version:
The installer checks your current version and only downloads if an update is available. You can also use the built-in update command:

​
Troubleshooting

​
”Authentication failed” or “No credentials found”

GlooCode can’t find or validate your API credentials. Check that your environment variables are set:
If either prints empty, add them to your shell profile and reload (see Step 2). If both are set but authentication still fails, verify the values match what’s shown on the API Credentials page in Studio.

​
”Command not found: gloocode”

The most common cause is running the command in the same terminal session where you installed. Open a new terminal window and try again. If it still doesn’t work, check where the binary was installed:
If the binary exists but isn’t on your PATH, add its directory manually:
Add this line to your shell profile (~/.zshrc or ~/.bashrc) so it persists across sessions.

​
Binary won’t run on Linux

On older Linux systems, the installer may select the wrong libc variant. If you see errors about missing shared libraries:
  • Check your libc: ldd --version (glibc) or musl-ldd --version (musl)
  • The installer auto-detects this, but you can also download the correct variant manually from the install URL

​
Next Steps

Launch GlooCode

Start the TUI or the Web UI and run your first task.