System prompts
Set the role + guardrails per node, or one shared default for the whole canvas.
Back to all features
models · MODELS.md
Directive Model Control.
Control every aspect of your models from a single MODELS.md file — system prompts, temperature, tool access, routing, fallbacks, and per‑node overrides. One declarative document, versioned right next to your canvas.
In development
MODELS.md
Versioned with your project
what it is
One file. Every model decision.
A single MODELS.md at the project root declares system prompts, temperature, tool access, routing, and fallbacks for every node — instead of settings scattered across node inspectors where they can't be diffed and quietly drift.
Defaults at the top apply to the whole canvas. Per‑node blocks override only what they name — a sharper prompt for Review, zero temperature for Evaluate, a narrowed tool set for Apply. It's a plain file, so it commits with your graph and reviews like code.
prompts
sampling
Temperature & params
temperature, top_p, max_tokens — declarative, never buried in an inspector.
tools
Tool access
Allow- and deny-list tools per node. Apply writes; Investigate only reads.
routing
Model routing
Route node classes to providers — cheap model for drafts, frontier for review.
resilience
Fallbacks
An ordered chain: if the primary errors or rate-limits, the next model takes over.
precision
Per-node overrides
A node block overrides only the keys it names; everything else inherits defaults.
interactive · the directive editor
Toggle a directive. Watch the canvas obey.
Flip a directive on the left — the MODELS.md source rewrites itself and the nodes re-resolve their config, exactly as the file governs a live run.
directives
applied · in sync
resolved on canvas
Investigate
gpt-4o
Plan
claude-opus
Create
gpt-4o
Evaluate
claude-opus
Apply
gpt-4o
Review
claude-opus
how it works
Defaults cascade. Nodes override.
Resolution is a three-step merge the runtime runs once, when the canvas loads.
01
Read defaults
The [defaults] block sets provider, model, temperature, and the base tool set for every node on the canvas.
02
Merge node blocks
Each [node.*] block overrides only the keys it names — a sharper prompt for Review, temperature: 0 for Evaluate.
03
Bind fallbacks
Ordered fallback chains attach so a rate-limit or error rolls the node to the next model — mid-run, without a stall.
reviewable
Diffs like code
A prompt tweak or a routing change is one line in a PR — no hunting through node inspectors.
portable
Travels with the repo
Clone the project, get the exact model setup. No dashboard state to recreate, nothing to wire by hand.
consistent
One source of truth
Defaults stop drift across dozens of nodes. Change the model once; every node that inherits follows.
related features
Activeper node
Model Hotswapping
Set provider + model per node and swap live, mid-run.
openActiveoffline
Local Models
Ollama, llama.cpp, LM Studio — fully local, alongside the cloud.
openIn developmentversioned
Git-backed Canvas
Every workflow is a file — commit, diff, and review like code.
open