Skip to content
Gluon

Overview

Gluon is a terminal app (the command is gluon) where you run coding agents side by side: Claude Code, Codex, Antigravity, Grok Build, OpenCode and Kimi Code, each on your own API key or your own subscription. Its home is the list of your sessions. Under it, the intake agent (an LLM with read-only access to your repository) asks a few questions about what you want to build, then proposes the agent as harness × model × effort with an agent-ready spec.

Enter starts the session: the agent’s own UI, unchanged, inside Gluon’s frame. Start more, switch between them, go home with one key. Nothing has to be quit to switch.

Get started

Section titled “Get started”

Pick your system, install Gluon, then run it in a repository. Gluon asks you to connect your agents the first time.

Works on Linux, macOS and WSL. It installs ~/.local/bin/gluon (no sudo) after checking the download against the release’s SHA256SUMS.

Terminal window
curl -fsSL https://github.com/fidipro/gluon/releases/latest/download/install.sh | sh

On Alpine and other musl systems, also run apk add libstdc++ libgcc.

Then start Gluon in any repository:

Terminal window
cd your-repo
gluon

Continue with the quickstart →

What you can do

Section titled “What you can do”

Describe the work, not the agent

Say what the session is for. The intake agent looks around your repository, asks only what it cannot tell from the code, and writes the spec the agent will get.

Let routing pick the agent

Your routing.yaml turns the session’s kind and difficulty into an agent, a model and an effort, among the models your connections can really reach. See Routing.

Run several agents at once

Each session is an agent’s own binary in its own terminal, in Gluon’s frame. Switch with one key while every session keeps running, and reopen them later with gluon resume. See Sessions.

Use your key or your plan

Connect each agent with an API key (Anthropic, OpenAI, Gemini, xAI, Amazon Bedrock, OpenRouter) or your own subscription. See Connections.

Explore or plan before it builds

Start a session in build, explore (read-only) or plan mode. See Modes.

Keep sessions apart

In a git repository each session works in its own worktree and branch, so sessions do not step on each other. See Worktrees.

See what a session costs

Every row shows the agent’s state, its cost and its context use, counted by Gluon’s own tables. See Cost and context.

Stay in control of your keys

Keys stay out of Gluon’s environment, repository content goes nowhere but the intake agent’s provider, and there is no telemetry. See Security and privacy.

Next steps

Section titled “Next steps”