Document template
A Word (.docx), HTML, spreadsheet (.xlsx), CSV or Markdown file the agent fills in. Letterheads, report layouts, invoices and email signatures all work this way.
Blueprints
A Blueprint saves a result you liked, such as a letterhead, a deck theme or a tone of voice, so your other agents can match it without you explaining it again.
A Skill says how to do a job. Knowledge says what to know. A Blueprint says what the result should look like.
Four kinds
Section titled “Four kinds”Deck theme
The colors, fonts and layout of a deck you liked, so the next presentation from your agents matches it.
Writing style
The tone and layout your text should follow. It can also hold wording to reuse as is, such as your standard terms.
Image
A logo variant, a signature or a stamp that agents place in what they make.
Saving one
Section titled “Saving one”From a conversation. When you’re happy with something an agent made, it can offer to save it as a Blueprint. A card shows what will be saved and asks you to choose Save or Not now before anything happens. The card appears at every autonomy level. Without your Save, nothing is kept.
In the Console. Open Blueprints and choose Add Blueprint to upload a document template or an image, or to write out a writing style. Deck themes are saved from a conversation.
Using one
Section titled “Using one”Your agents check your Blueprints when they make something a Blueprint could shape, or when you name one: “Write the update with my Board memo Blueprint.” They use one only when it fits the job. Nothing is added to every conversation, so an agent that never needs a Blueprint never reads one.
A document template or an image is copied into the agent’s workspace, where the agent fills it in or places it.
Loops can use your Blueprints, but they never offer to save one.
Sharing with your team
Section titled “Sharing with your team”A new Blueprint is yours alone, available to all of your agents. To let your whole team’s agents use it, choose Share with team on the Blueprints page.
- When an owner or admin shares a Blueprint, the team gets it right away.
- When a member shares one, it waits for an owner or admin to approve it. Owners and admins see it under Waiting for approval, where they can read it, then Approve or Decline.
- An approval covers the version the reviewer read. If the Blueprint changed in the meantime, the page says so and the reviewer reads it again, so the team always gets the version that was approved.
- When a member edits a Blueprint the team already uses, it goes back for approval.
- Stop sharing makes it yours alone again.
Limits
Section titled “Limits”| Blueprints per person | 50 (shared ones count toward their owner’s 50) |
| File size | 5 MB per file |
| Writing style | 20,000 characters per writing style |
| Document template files | .docx, .xlsx, .html, .htm, .csv, .md |
| Image files | .png, .jpg, .jpeg, .webp, .svg |
Customers of a customer-facing agent never see Blueprints (see Agent types). Neither do agents with no workspace, or an agent connected to your machine read-only.
Blueprints, Skills and memory
Section titled “Blueprints, Skills and memory”| Says | Holds | Reaches an agent | |
|---|---|---|---|
| Skill | How to do a job | Steps, plus optional scripts and reference files | Attached to an agent |
| Blueprint | What the result looks like | A file, a deck theme or a writing style | All of your agents, or your team’s once approved |
| Memory | What the agent learned about you | Short notes | Recalled in conversation |
A Skill’s steps can point to a Blueprint: “format the report with the Quarterly report Blueprint”. See Skills and Memory.