Many sessions on screen, arranged like you mean it
A recursive split mosaic of sessions, terminals, editors, git, and assistants. Every tile carries a host, so one grid can reach across every machine you own. Same surface in the portal.
Each assistant carries a persona, a constitution, memory, a daily journal, and a workbench — written to disk. The same on-disk identity drives Claude Code, Codex, Gemini, and ACP.
Persona, constitution, memory, journal, workbench
Runs on any harness — Claude Code, Codex, Gemini, ACP
Pull assistants and humans into the same team. Shared channel, shared task board, shared constitution. Leads, reviewers, and ICs gate who can move what.
Pick how Glueprint launches files and what happens on save.
Available on
Desktop
The Glueprint Editor preferences are intentionally minimal — enough to wire a few hand-offs, not enough to replace your real editor’s settings.
What you can configure
External editor — pick the editor Glueprint hands off to when you ask it to open a file or a folder. The list includes the most common editors; pick the one you use day to day.
Custom command — if your editor isn’t in the picker, paste the shell command Glueprint should run.
Format on save — when the built-in editor saves a file, run the language’s formatter first.
Auto-open modified — when an agent changes a file you currently have open, jump the editor to the change.
The built-in editor doesn’t expose font, tab width, word wrap, minimap, or per-language overrides as user preferences in the current release. Most of those follow the language server’s project configuration where it’s available.
Where to set them
These options live in the desktop app under Settings > Agents > Editor (and in the command-center settings overlay). They aren’t currently surfaced in the portal.
