Start a session

A session is one running conversation with a coding agent inside a working directory. You can start one in two clicks on every surface.

On desktop

1. Click Sessions in the left navigation rail.
2. The Sessions view shows the new-session composer when nothing is selected. It has an Agent picker, a project picker, and a message box.
3. Pick which agent to run (Claude Code, Codex, or Gemini), confirm the project / working directory, type the opening prompt, and click Send.

You can return to the new-session composer at any time by selecting the empty-state slot in the Sessions sidebar.

You can start many sessions in parallel. Each runs in its own subprocess. Use the sort menu above the sidebar to group them — by project, agent, status, or recent activity. The default sort is most-recent first.

On the portal

The portal mirrors the desktop. Open Sessions in the nav and use the New session control in the sidebar. The composer asks which host to start the session on (any host you’ve activated). Pick a host, an agent, a working directory, and a prompt. Click Send.

Folders are scoped to the host: the portal lists folders that exist on the host you pick. You can’t start a session on a folder that doesn’t exist on the host that will run it.

On mobile

You can start a session from the Sessions tab:

1. Tap Sessions in the bottom navigation.
2. Tap New session at the top.
3. Pick a host, agent, and working directory. Type your message.
4. Tap Send.

The mobile composer doesn’t offer the editor; for heavier setup, use desktop or portal.

From the CLI

The CLI daemon doesn’t have a UI of its own. To start a session on a CLI-only host, use the portal or the mobile app and pick the daemon as the host. The daemon picks up the request, spawns the agent locally, and streams events back through the cloud relay.

If you want to drive the daemon entirely from a terminal, see CLI Daemon > Commands for session subcommands that list and stop sessions on the host. Direct session-creation from the command line is part of a future release.

What gets created

When you start a session, Glueprint:

• Spawns the agent as a subprocess inside the chosen working directory.
• Begins recording every message, tool call, and file change to a local log.
• Adds the session to your sidebar with a teal pulsing status dot.
• If you have cloud relay on, immediately publishes the session to your other surfaces.

The session belongs to the host where it was started. Stopping the desktop app stops the session unless that host is the CLI daemon (which keeps running).

What if I closed the wrong folder?

The working directory is set at session start and doesn’t change. To switch folders, stop the session and start a new one. The conversation transcript stays in the sidebar; you can copy any context from it into your new session.

Related topics

• The session view — what you see while a session is running.
• Permissions and approvals — how Glueprint pauses for risky actions.
• AI Assistants — for sessions that should be persistent and named.