> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation & Setup

> Install Gloo Code and sign in through the browser with your Gloo AI account.

This guide walks you through installing Gloo Code and signing in with your Gloo AI account. It usually takes a few minutes.

## Prerequisites

You need:

* **macOS or Linux** (ARM64 or x64) — see [platform support](#platform-support) below
* **A Gloo AI account** — [sign up here](https://studio.ai.gloo.com/sign-up) if you don't have one
* **An [organization](https://docs.gloo.com/getting-started/glossary.md#organization) with a Gloo Code subscription** — and a seat assigned to you. Your Gloo AI admin can sort this out; see [Billing & Plans](https://docs.gloo.com/studio/billing.md#choosing-a-gloo-code-tier) for tiers, seats, and how to buy.

### Platform Support

Gloo Code ships as a self-contained binary for macOS and Linux:

| OS | Architecture | Variant |
| - | - | - |
| macOS | ARM64 (Apple Silicon) | — |
| macOS | x64 (Intel) | — |
| Linux | ARM64 | glibc |
| Linux | x64 | glibc |
| Linux | ARM64 | musl |
| Linux | x64 | musl |

No runtime dependencies are required. The installer detects your platform and downloads the correct binary.

> [!NOTE]
>
> On **Windows**, run Gloo Code through WSL (Windows Subsystem for Linux) using the Linux binary.

## Install and sign in

**1. Install the binary**

Run the installer script:

```bash theme={null}
curl -fsSL https://gloocode.ai.gloo.com/install.sh | sh
```

The installer places the binary in your PATH (typically `/usr/local/bin/gloocode` on macOS) and updates your shell profile if needed.

> [!WARNING]
>
> **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:

```bash theme={null}
gloocode --version
```

A version number means the install succeeded. If you get "command not found", see [Troubleshooting](#troubleshooting) below.

**2. Sign in**

Sign-in happens in your browser. Start Gloo Code in any project directory:

```bash theme={null}
gloocode
```

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.

> [!NOTE]
>
> **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](https://docs.gloo.com/tutorials/authentication.md#legacy-client-credentials-and-oauth). Type `/login` to open the same dialog.

> [!TIP]
>
> 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](https://docs.gloo.com/api-guides/provider-failover.md). You don't enter API keys for individual model providers.

## Working across several organizations

Each organization you sign in with is saved as its own **profile**.

| Command | What it does |
| - | - |
| `/login` | Sign in to another organization and switch to it |
| `/profiles` | Switch between saved profiles, or press **Ctrl+D** to delete the highlighted one |

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.

> [!TIP]
>
> [Gloo Code Desktop](https://docs.gloo.com/gloocode/desktop.md) 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:

```bash theme={null}
curl -fsSL https://gloocode.ai.gloo.com/install.sh | sh
```

The installer checks your current version and only downloads if an update is available.

You can also use the built-in update command:

```bash theme={null}
gloocode update
```

## Troubleshooting

> [accordion] Sign-in fails or won't finish
>
> Gloo Code names the reason in the terminal. The ones you're most likely to see:
>
> | Message | What to do |
> | - | - |
> | Your account has no organizations eligible for Gloo Code | Ask your Gloo AI admin to add a Gloo Code subscription, or to assign you a seat — see [Teams and seats](https://docs.gloo.com/studio/billing.md#teams-and-seats) |
> | Your organization's billing setup does not allow [API keys](https://docs.gloo.com/studio/manage-api-credentials.md) yet | Finish billing setup in [Studio](https://studio.ai.gloo.com/), then sign in again |
> | The sign-in request expired | Attempts expire after 10 minutes — run `/login` to start a new one |
> | Sign-in was denied in the browser | You (or your identity provider) declined the request; run `/login` to retry |
>
> 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 subscription and a seat for each user; see [re-enabling a team that used client credentials](https://docs.gloo.com/studio/billing.md#if-your-team-used-gloo-code-before-with-a-client-id-and-secret).

> [accordion] Command not found: gloocode
>
> Usually the terminal session you installed from doesn't have the updated PATH yet. Open a **new** terminal window and try again.
>
> If it still doesn't work, check where the binary was installed:
>
> ```bash theme={null}
> which gloocode       # should show /usr/local/bin/gloocode or ~/bin/gloocode
> ls /usr/local/bin/gloocode ~/bin/gloocode 2>/dev/null
> ```
>
> If the binary exists but isn't on your PATH, add its directory manually:
>
> ```bash theme={null}
> export PATH="/usr/local/bin:$HOME/bin:$PATH"
> ```
>
> Add this line to your shell profile (`~/.zshrc` or `~/.bashrc`) so it persists across sessions.

> [accordion] 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

> [card] [Launch Gloo Code](https://docs.gloo.com/gloocode/launch.md)
>
> Start the terminal UI and run your first task.

> [card] [What's new in Gloo Code](https://docs.gloo.com/gloocode/whats-new.md)
>
> Connectors, safety settings, and more.

> [card] [Migrate to Gloo Code](https://docs.gloo.com/gloocode/migrate/overview.md)
>
> Coming from Claude Code, Codex, or another tool? Bring your setup with you.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.