Skip to content

Agents

Which coding agents Glueprint has detected, and how to add or remove them.

Available on
  • Desktop

The Agents section lists every coding agent Glueprint has detected on your machine. You point Glueprint at the agents; the agents do the actual coding work.

Supported agents

  • Claude Code — from Anthropic. Conversation, full tool use, session resume.
  • Codex — from OpenAI. Conversation, tool use, mid-turn steering.
  • Gemini CLI — from Google. Conversation, tool use.

Each agent is a CLI you install yourself. Glueprint doesn’t bundle them.

Auto-detection

When Glueprint launches, it scans your PATH for known agent binaries. Detected agents show up in the Agents list with their version and the path Glueprint will use.

If an agent isn’t detected:

  1. Install the agent’s CLI per its vendor’s instructions.
  2. Make sure it’s on PATH for the shell Glueprint launches with (usually a login shell on macOS and Linux).
  3. Open the agent’s card in Settings > Agents and click Detect to re-scan that agent, or relaunch the app to re-scan all agents.

Custom paths

If an agent is installed at a non-standard location, click Edit on its row and paste the full path. Glueprint will use that path instead of the auto-detected one.

Default agent

The first agent in the list is Glueprint’s default for new sessions. Drag to reorder. The reorder applies everywhere — the Sessions composer, the assistant create form, the routine setup.

What Glueprint does with each agent

When you start a session, Glueprint:

  1. Spawns the agent as a child process inside the working directory.
  2. Pipes your initial prompt and any context through the agent’s standard input.
  3. Reads everything the agent produces from its standard output.
  4. Renders messages, tool calls, and file edits in the session view.

Each agent has slightly different capabilities; Glueprint accommodates the differences so you don’t have to think about them. The agents’ configuration (API keys, model selection, rate limits) is managed where the agent itself wants — usually in its own config file or environment variables.

API keys

Glueprint doesn’t store or proxy your agent API keys. Each agent reads its credentials from its usual location:

  • Claude Code — uses your ~/.anthropic or ANTHROPIC_API_KEY.
  • Codex — uses your OpenAI configuration.
  • Gemini CLI — uses Google’s credentials.

Your usage cost is whatever the agent vendor charges; Glueprint doesn’t markup or relay.

Multi-machine

Agents are per-host. If you install Glueprint on a second machine, install the agents on that machine too. The list in Settings > Agents is local to the host you’re on.

PreviousAppearance
NextTool permissions