A canvas that keeps the thread of your ideas.
Ask for a screen from Chat or Code. The agent proposes three options; you keep what sticks, the library retains what repeats.
"Finally a canvas that remembers which option I killed and why. My feedback loops are half as long."
"The thread from Chat to canvas is the part I didn't know I needed. Context just shows up."
"Track B was the one we shipped. Track A is still there, three weeks later, when the client asked to revisit."
Inside the canvas
Cortex Design — design.cortex.foundation
- Frame
- Note
- Image
- Library
Option B · selected
B keeps the hierarchy: image first, title second. Keep both buttons, test at 390.
Components Pages Tokens
Pill button · Article card · Nav bar · Source chip · Composer · Footer
FROM CORTEX CHAT · design_write
« Revisit B, let the title breathe, and propose a dark variant. » → Frame B updated · Frame D added · 2 components in the library
CANVAS · SHARED
Auto-saved · just now
Between every revision, something disappears — the option you nearly chose, the constraint that ruled it out. The next session starts without that memory. Cortex Design keeps every path open.
Three tracks. One thread.
The canvas keeps A, B and C — and the conversation that produced them. You can revisit B without erasing the others.
A · Title first
A first pass sets the title, the image, and the action — the skeleton every revision starts from.
B · Image first
Image leads, title follows, both buttons stay. A note explains the choice at 390px.
C · Side by side
Image on the left, content on the right. All three options live in the same canvas — you never lose B to try C.
A canvas is born from a conversation or a code session.
Host Chat or host Code, never both at once; the list finds your canvases by today, yesterday, or search. Titles and files are numbered, the export takes them all — Cortex Design is where they land.
The web holds the door; the canvas lives in Cortex Design.
Updates from releases.cortex.foundation