Skip to main content
Melius is a canvas, not a chat. That distinction matters because it changes how you work with the AI. In a chat interface, you describe what you want, the model responds, and the reasoning is hidden. If the result is wrong, you start over with a new prompt. In Melius, the agent’s work is laid out visually — every model call is a node, every input that feeds into it is an edge, and every prompt is exposed and editable. If the result is wrong, you find the node where it went off and fix that one thing.

​
The four-beat workflow

Almost everything in Melius follows the same shape:
1

Brief

Tell the agent what you want, in plain language. Paste in references, product links, brand assets — whatever helps. The more context you give, the better the output.
2

Watch

The agent assembles a canvas: picks models, writes prompts, routes outputs between nodes. You can see what it’s doing in real time, with each node’s reasoning visible.
3

Tweak

The agent will land you 85–95% of the way there. Step in at the node level — edit a prompt, swap a model, change a reference image, branch a new version — until the output is exactly right.
4

Output

Download production-ready files, or hand the canvas off to a teammate. Multiplayer means designers, marketers, and the agent can all be on the same canvas at once.

​
The building blocks

Three things make the canvas work: nodes, edges, and the agent.

​
Nodes

A node is one AI model call. The main types you’ll use:
  • Text node — a language model (GPT, Claude, Gemini). Treat it like ChatGPT inside a node: prompt in, text out. Useful for ideation, prompt-writing, brand analysis, and as a place to paste a brand brief.
  • Image node — an image model (Nano Banana, GPT Image 2, etc.). Generates from text, an image-to-image reference, or both.
  • Video node — a video model (Veo, Seedance, Sora). Takes text, a starting frame, or a reference image as input.
  • Audio node — voice generation, currently powered by ElevenLabs.
  • Studio node — a layered editing canvas inside a node. Add layers, drop in text overlays, position elements precisely. The right tool for last-mile composition edits without leaving Melius.
  • Stitch node — concatenates video clips into a longer sequence.
There’s a full reference at Pick the right model. For now: every node has a model picker, an aspect ratio picker, a resolution picker, and a prompt field.

​
Edges

An edge is the line connecting one node to another. What an edge actually does on the backend is route context: the output of the source node becomes part of the input for the destination node. Two ways to create edges:
  • Drag the circle. Each node has a small circle on its border. Drag from the source node’s circle into the body of the destination node.
  • Use @ in a prompt. Type @ inside a prompt field and a list of nearby nodes appears. Select one, hit enter, and the edge appears automatically — the same way @ works in Slack.
Whichever way you create it, the destination node will pull in whatever the source produced (an image, a text block, a video) when you run it.

​
The agent

The agent (Mel) sits in a chat panel on the canvas. It has access to every tool on the canvas — it can create nodes, connect edges, write prompts, choose models, run generations, and check its own work. Two modes:
  • Auto-run. The agent decides what to build and runs it without asking. Best for “I trust you, just make me 10 variants.”
  • Ask permission. The agent asks clarifying questions before each major step. Best for high-stakes work where you want to inspect each decision.
While the agent is working, you’ll see a small cyan indicator on the canvas — that’s the agent’s presence marker, showing you where it’s currently building. Same idea as a multiplayer cursor, just for the AI. You don’t have to use the agent. Marketers who know exactly what they want sometimes drop the nodes themselves. But for most jobs, briefing the agent and steering at the node level is faster.

​
What the canvas is not

It’s a production canvas, not a layout tool. Other design surfaces are built for laying out a known design; Melius is for producing the design in the first place. For last-mile composition work, the Studio node lives on-canvas so you don’t have to leave Melius. It’s not a hand-wired node canvas either. Earlier node-based generative canvases were built before agents existed and assume a human wires up every node by hand. Melius was built agent-first — the canvas exists so you can see and steer the agent’s work, not perform every step yourself.
Last modified on June 16, 2026