Missing agents
When Claude Code, Codex, or Gemini doesn't show up in the agents list.
- Desktop
- CLI Daemon
Glueprint doesn’t bundle the underlying coding agents; it runs whichever ones you have installed on your machine. If Settings > Agents shows an empty list or a missing entry, the agent isn’t installed where Glueprint can find it.
Step 1: confirm the agent is installed
Open a terminal on the host. Run the agent’s CLI directly:
| Agent | Command to check |
|---|---|
| Claude Code | claude --version |
| Codex | codex --version |
| Gemini | gemini --version |
If you see a version, the agent is installed and on the shell’s PATH. Move on to Step 2.
If you see “command not found,” the agent isn’t installed or it isn’t on PATH. Install it per the vendor’s docs, then come back here.
Step 2: confirm Glueprint sees the same PATH
Glueprint on macOS and Linux launches with a login shell, which inherits your ~/.zshrc or ~/.bashrc environment. But if you installed the agent via a tool that only modifies a non-login shell’s path, Glueprint won’t see it.
Quick test: in your terminal, run echo $PATH. The agent’s directory should be in the list.
If it isn’t:
- Move the
PATHexport from your~/.zshrc(or whatever) to a file that login shells read:~/.zprofileon Zsh,~/.bash_profileon Bash. - Quit and relaunch Glueprint. The next launch picks up the new path.
On Windows, Glueprint uses the system PATH. Confirm the agent is in PATH from cmd.exe, not just from PowerShell with profile-specific aliases.
Step 3: re-scan in Glueprint
- Open Glueprint on the host.
- Settings > Agents.
- Click Re-scan.
The list refreshes. If the agent is found, you’ll see its row. If it’s still missing, move to Step 4.
Step 4: add it manually
Each agent row has an Edit button. Click + Add agent (or Edit if the agent is half-detected) and paste the full path to the binary.
- macOS / Linux example:
/Users/you/.local/bin/claude. - Windows example:
C:\Users\you\AppData\Local\Programs\claude\claude.exe.
Save. The agent is now registered explicitly; Glueprint won’t try to re-find it on auto-scan.
Step 5: confirm the agent works
Start a one-message session. Pick the agent. Send “say hi”. If you see a reply, you’re done.
If the session immediately fails:
- The agent might be missing credentials. Each agent reads its credentials from its own location; check the vendor docs.
- The agent might be a different version than Glueprint expects. We support the released versions; if you’re on a pre-release branch, things may be wobbly.
The agent shows up but every session fails
The agent is detected but immediately errors when Glueprint launches it. Usually one of:
- Authentication. The agent CLI needs to be signed in or have an API key configured. Run the agent in a terminal once to confirm it works on its own.
- Sandbox or permissions. macOS sometimes blocks Glueprint from spawning subprocesses on first run; approve the dialog if it appears.
- Old version. Update the agent to its latest release. Bug fixes in our integration are sometimes blocked by an outdated agent.
CLI daemon
On a CLI daemon host, agents are detected the same way; you just can’t see the list from a UI. Run glueprint agent detect on the host to see what was found. See CLI Daemon for the full command reference.