Create an assistant

You can create an assistant in any surface that’s signed in to your account. The desktop is the most thorough; portal and mobile cover the basics.

On desktop

1. Click Assistants in the left navigation rail.
2. From the empty state click Create assistant, or click the New assistant tile in the assistants grid.
3. Fill in the form:
   • Name — what the assistant is called. Short is fine.
   • Agent — which underlying agent to use (Claude Code, Codex, Gemini).
   • Working directory — the folder the assistant lives in.
   • Persona — a paragraph in plain language describing the assistant’s role and voice.
   • Constitution — the rules the assistant follows (optional — the organization constitution still applies if you skip this).
4. Click Create. The assistant appears in the sidebar.

The assistant is now idle. It won’t do anything until you send it a chat message, queue it a task, or hook up a routine.

On the portal

The portal mirrors the desktop flow. From the Assistants view, click the New assistant tile. The assistant is created on the host you’re currently looking at in the portal — to put it on a different host, switch the host picker first. Fill the same fields as desktop (name, agent, working directory, persona, constitution).

On mobile

Mobile supports creating assistants from the Assistants screen. Tap +, pick a host, give the assistant a name and persona, and pick the working directory (mobile shows folders the host already knows about). For the constitution, mobile gives you a multi-line text editor.

If you want to do heavier setup — large persona files, complex constitutions, routine setup — do it on desktop or portal.

Defaults that just work

If you’re not sure what to fill in:

• Name — something descriptive, like auth-refactor or weekly-review. You can change it later.
• Agent — pick whichever underlying agent you use most.
• Persona — one or two sentences. “You’re a careful Rust reviewer who flags unsafe code and unhandled errors.” Better to be specific than long.
• Constitution — leave empty for your first assistant. The organization constitution provides reasonable defaults.

What gets created on disk

The assistant gets its own folder inside Glueprint’s data directory. Inside you’ll find the persona and constitution files, a memory/ directory (long-term, reference, journal, and an index), an append-only chat log, an instructions folder for routines, and a workbench/ directory. Most users never touch these files directly — the desktop’s Memory tab and Workbench tab are the easier way in. Power users can read and edit them as plain Markdown.

Multiple assistants

You can run dozens of assistants on one host. Each is independent; their memory and chat don’t bleed into each other. The host’s memory and CPU are the only practical limits.

Common patterns:

• One assistant per major project.
• One “infra” assistant for monitoring, one “feature” assistant for shipping.
• A small team of assistants on different roles, grouped under a Team.

Next step

• Send your first chat message to wake the assistant.
• Set up a routine so the assistant wakes on a schedule.
• Add the assistant to a team for cross-host collaboration.