Your first session

A session is one running conversation with an AI coding agent inside a working directory. Glueprint shows what the agent does in real time, asks you to approve risky actions, and saves the whole transcript.

Pick an agent

Glueprint launches an external coding agent on your machine; it doesn’t ship its own model. There are three first-party agents and a growing catalog of community agents reached through the Agent Client Protocol.

First-party agents — detected automatically when you install them:

• Claude Code — from Anthropic.
• Codex — from OpenAI.
• Gemini CLI — from Google.

ACP agents — any agent that speaks the Agent Client Protocol is also supported. Browse the ACP agent registry to see what’s available, install one per its docs, then point Glueprint at the binary in Settings > Agents.

Open Settings > Agents to see which agents Glueprint has detected. If an agent is missing, install its CLI and relaunch the app — detection runs at launch. The order shown in Agents is the order Glueprint suggests when you start a session.

Pick a working directory

A session is always tied to one folder — usually a git repository. Multiple sessions can share the same folder; Glueprint deduplicates the heavy lifting so file watchers and git status calls don’t multiply.

If you haven’t picked any folders yet, open Settings > Projects and add a project. The folder picker is also offered the first time you start a session.

Start a session

1. Click Sessions in the left navigation rail.
2. The empty Sessions view shows the new-session composer. Pick the agent, the working directory, and write your first message.
3. Click Start session.

The session appears in the sidebar with a teal pulsing status dot. The center pane shows messages, tool calls, file edits, and command output as they happen.

You can start more than one session at the same time. Each session runs in its own subprocess and has its own conversation history.

Approve actions

When the agent wants to do something risky — write a file outside the working directory, run a shell command, talk to a non-allowlisted tool — Glueprint pauses and asks. A pinned card appears at the top of the session with the requested action and Approve / Deny buttons.

Permission defaults are scoped per assistant under the assistant’s Settings, and inline approvals let you say “always allow” for a specific tool right from the chat. Defaults are intentionally cautious; loosen them as you build trust with a workflow.

Pause, resume, stop

• Pause keeps the session alive but tells the agent to wait. Useful when you want to read what’s happened so far without new output piling on.
• Stop ends the session. The transcript stays in the sidebar; you can open it any time and start a follow-up session from where it left off.
• Reopening a stopped session and sending a new message resumes the same conversation when the agent supports it.

See your session from another device

If you’ve connected the cloud relay, your session shows up immediately on the portal at portal.glueprint.ai and in the mobile app. The transcript and approvals are end-to-end encrypted between your machine and the other surface. The relay routes the events but never sees plaintext content.

Next step

Continue to the Glossary to learn the rest of Glueprint’s vocabulary, or skip ahead to Sessions for the full reference.