Skip to main content
This guide walks you through installing Gloo Code and signing in with your Gloo AI account. 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
  • An organization with a Gloo Code plan — and a seat assigned to you. Your Gloo AI admin can sort this out; see Billing & Plans for tiers, seats, and how to buy.

​
Platform Support

Gloo Code 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 Gloo Code 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: Sign In

Sign-in happens in your browser. Start Gloo Code in any project directory:
On a new install it opens Sign in to Gloo straight away. Press Enter on Sign in with browser and your browser opens Gloo AI Studio.
  1. Sign in to Studio and choose the organization you want to use Gloo Code with.
  2. Approve access. Studio shows a success page you can close.
  3. Back in the terminal, Gloo Code confirms you’re signed in and drops you at the prompt.
Already used Gloo Code on this machine? Then it starts straight into the TUI without asking — including if you set it up with the old Client ID and Secret. Type /login to open the same dialog.
The browser only opens after you press Enter, so a session started over SSH or in a container never spawns a window unasked. If the browser doesn’t open, Gloo Code prints the sign-in URL — open it on any machine and finish there. A sign-in attempt expires after 10 minutes.

​
Where your sign-in is stored

On macOS, Gloo Code stores your credential in the login keychain, readable only by your user. On Linux it lives in ~/.config/gloo/credentials.json with 0600 permissions. Either way it stays on your machine and is used only to authenticate your requests to Gloo AI. Requests route through Gloo AI, which handles provider selection, safety screening, and failover. You never manage API keys for individual model providers.

​
Working across several organizations

Each organization you sign in with is saved as its own profile. Switching profiles persists, so your next session starts on the same one. Deleting a profile removes it locally and revokes its access on the Gloo AI platform.
Gloo Code Desktop signs in exactly the same way and keeps its own profiles. The two share sessions and project data, so a session you start in one shows up in the other.

​
Updating Gloo Code

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

​
Sign-in fails or won’t finish

Gloo Code names the reason in the terminal. The ones you’re most likely to see: If the browser never opened, copy the sign-in URL Gloo Code prints and open it yourself. If a run later stops working, your access may have been revoked — for example an admin removing your seat. Run /login to sign in again. If your team used Gloo Code with a Client ID and Secret before, those credentials no longer sign you in. Your organization needs a Gloo Code plan and a seat for each user; see re-enabling a team that used client credentials.

​
”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 Gloo Code

Start the terminal UI and run your first task.