Copying to LLMs
Copy for AI hands a model a link to your live .dai file; Copy XML puts the whole file on your clipboard; ⌘V brings a model’s XML back onto the canvas.
A .dai diagram is high-quality context for whatever model you’re about to talk to: the element tree, its names, descriptions, rules, scopes, and the diagram’s type framing arrive in one structured file. That’s the core loop of DAI Studio — the LLM reads a precise description of your intent instead of you re-typing it into a chat window.
The loop
- Design context in DAI Studio — place, connect, and describe elements until the diagram says what you mean (see Your First Diagram).
- Copy for AI — click the button in the editor’s top bar. It copies a link to the document’s raw
.daifile; paste it into any chat, agent, or tool that can fetch URLs. - Or Copy XML — for tools that can’t fetch links, open Document → Export → Copy XML. The complete
.daifile — every element, value, and description — is on your clipboard as plain text. - Run — execute the workflow, generate the code, answer against the context, whatever the diagram drives.
- Iterate — models that suggest structural changes can say them in
.daiterms. Copy the XML they produce and press⌘Von the canvas to drop it into your diagram; upload it with Upload .dai to keep both versions side by side; or apply the changes by hand in the editor, where everything keeps auto-saving.
Copying part of a diagram
Select some elements and press ⌘C: the selection is copied as a self-contained .dai fragment — the elements, their values, and the connections between them. Paste it into a chat to ask about just that slice, or into another document with ⌘V.
DAI Builder prompts
If drafting a workflow from scratch feels heavy, Document → DAI Builder has ready-made prompts for outsourcing the work to a model:
| Group | Prompts |
|---|---|
| Diagram | Diagram a document, Diagram a PDF, Diagram this codebase |
| Refine | Update existing .dai, Execute workflow, Explain this workflow, Improve this workflow |
Click a prompt to expand it, then copy it into your model along with your document, PDF, codebase, or .dai file. Every prompt tells the model to read the format spec at https://dai.studio/llms.txt first.
Sharing instead of pasting
For tools that can fetch URLs — increasingly most of them — a link beats a paste:
| Who’s copying | Link Copy for AI gives | Notes |
|---|---|---|
| You, the owner | https://dai.studio/you/doc/raw/<token> | Tokenised, so it keeps working if the document is private. Document → Privacy → Rotate raw URL replaces the token and invalidates the old link for private access |
| A visitor to a public document | https://dai.studio/you/doc/raw | No token needed while the document is public |
Raw URLs return the live file as plain text with permissive CORS, so an agent can re-fetch the current version whenever it needs to — the plan evolves in your editor and never goes stale in the agent’s context. Document → Export → Copy URL copies the same link. Full details, including what visibility means for who can see what, are in Sharing & Visibility.
What the model reads
Everything you wrote and nothing you didn’t: the workflow metadata that frames the whole diagram, the type dictionary with your per-diagram descriptions, each element with its type and values, and — since the file is valid BPMN 2.0 — structure any model already understands from its training data. The Reference documents the vocabulary end to end.
That’s the whole discipline: say it once, precisely, in the diagram — then let every model you work with read the same truth.