Canvas

Agents build native, interactive interfaces (charts, dashboards, calculators, diagrams) right inside the conversation.

Some answers are easier to see and try than to read: a sales chart, a pricing calculator, a filterable table, an architecture diagram. With Neoo Canvas, an agent can build that interface directly inside the conversation instead of describing it.

Visuals without asking

You don't need to ask for a visual. Before each reply, the agent decides on its own whether the answer is easier to see than to read, and builds a canvas when it is:

The reply contains…The agent shows…
Numbers to compare, or a trendA chart or stat tiles
Several items compared on a few criteriaA table or side-by-side cards
A flow, an architecture or a sequenceA diagram
A plan, a roadmap or a migration in stepsA timeline
Test, audit or benchmark resultsStats, progress bars and a table
Options to choose fromCards with follow-up buttons
A calculation you may want to adjustSliders and inputs

Short or conversational answers, code or commands to copy, and questions the agent needs answered stay as plain text. A canvas only uses data the agent actually has, and the text reply adds what the canvas doesn't show instead of repeating it.

You can still ask for one in plain words, for example "Show me a bar chart of this CSV's monthly revenue." or "Draw a diagram of how the auth flow works in this repo." If you prefer text, say so (for example "text only, no visuals"): the agent then sticks to text in that conversation.

It works with every agent that has Neoo's tools (Claude, Codex, Cursor and the others), in every mode, including Plan: showing a canvas never changes your files. Canvases are not available in Neoo Design conversations, which draw in the design canvas instead.

Native interfaces

Most canvases are native: the agent describes the interface, and Neoo draws it with its own components — cards, lists, read-only fields, stats, tables, charts, sliders, switches, dropdowns, text fields, callouts, code blocks and Mermaid diagrams. A native canvas looks and behaves like the rest of Neoo, follows your theme and font, and reads well in both dark and light mode.

Native canvases are drawn flat, as part of the reply: no borders, outlines or boxes around them. A card is a section on the conversation background with a title, a short subtitle and a status pill on the right (for example In progress with a dot). Rows have an icon in a small tinted tile, a title, a subtitle and a value on the right, separated by spacing instead of lines. Tables alternate a light tint on every other row, fields and inputs are lightly tinted, and buttons are rounded pills. A timer or total shows as a large centered number. Tints are computed from your theme, so a canvas matches dark and light mode and the Current and Minimal interface styles. Colors stay neutral; green, amber and red only mark a status.

Native canvases are interactive. Moving a slider, flipping a switch, picking a row in a list, filtering a list or sorting a table updates the interface instantly, without asking the agent again. The selected row is highlighted with a tint. Some buttons send a follow-up to the agent, such as Choose this plan or Go deeper: clicking one posts that message in the conversation as if you had typed it, so you always see what was asked. These buttons only work while the agent is idle.

For what the components cannot draw (free-form drawings, audio, physics simulations), the agent can still publish a regular web page in an isolated frame, styled with your theme and asked to stay flat too.

Diagrams

Diagrams (flowcharts, sequences, states, timelines…) use the same style everywhere: in a canvas and in a Mermaid code block of a normal reply. They are drawn flat, like the rest of a canvas: no frame and no outlines, only soft tints.

  • Flowcharts: each subgraph is a zone with its own soft color (blue, green, amber, violet, sky, red, in the order they are declared) and its title in the top-left corner; the boxes inside take the zone's color. Without subgraphs, steps are blue and questions amber. Questions are boxes with a dotted outline instead of large diamonds, labels such as Yes / No sit in small pills, and arrows are thin open chevrons. When a box label has several lines (A["Title<br/>detail"]), the first line is the title and the next ones are a smaller, dimmer detail.
  • Sequence diagrams use the same palette: participants are tinted blue boxes, notes are amber, and loops are dotted.
  • A diagram shrinks to fit the width of the reply, centered, without a scroll bar. A very wide diagram stops shrinking at 60% so the text stays readable, and then scrolls sideways.
  • A left-to-right flowchart (flowchart LR) too wide for the reply is drawn top to bottom when that version fits better (on a phone, in a narrow panel). It switches back by itself when the reply gets wider.
  • Hover over a diagram to show Zoom in (+) and Zoom out (−) in its bottom-right corner. Ctrl + scroll wheel (Cmd + scroll wheel on macOS) zooms too, up to 5×. Once zoomed in, drag the diagram to move around.
  • Mermaid code (the </> button) shows or hides the source of the diagram below it.
  • Expand diagram opens it full screen, fitted to the window. Close, Esc or a click outside the diagram returns to the conversation. In the iOS/Android app, there is no full-screen button: the zoom and code buttons are always visible.
  • While a diagram is being drawn, a small animated placeholder (four boxes lighting up from left to right) holds its place; the Mermaid source is not shown during loading. A diagram in a tab or panel that was hidden is drawn as soon as it becomes visible.
  • When a label contains parentheses or a | that Mermaid rejects (for example A[Start (dev)]), or a box label starts with a slash (for example A[/login]), Neoo repairs the label and draws the diagram anyway. If the diagram is still invalid, or cannot be drawn within 15 seconds, its source is shown as code.

Where it appears

While the agent builds the canvas, a card shows Building the canvas…. When it is ready:

  • The canvas appears where the agent created it, directly on the conversation background: the sentence that introduces it stays visible just above it, the work that came before stays folded above, and any work that follows (and the final reply) appears below it. It keeps that place after the turn ends, even when Worked for… is folded. This is the same on the desktop app, Remote, the web companion and the mobile app.
  • To give it more room, select Expand: the canvas opens in the side panel, next to the browser and Neoo Design, in its own tab named after the canvas.

On mobile and the web companion, the controls are always visible. Expand opens a full-screen view; Close returns to the conversation.

Hover over the canvas (or focus it with the keyboard) to show a small round toolbar with three buttons in its top-right corner. The canvas keeps that corner free: the header of its first card stops just before the toolbar, so the toolbar never covers its title or status badge. On a touch screen the toolbar stays visible.

ButtonWhat it does
HideFolds the canvas into a small chip at its place in the conversation. Select the chip to show the canvas again.
Copy source / Copy HTMLCopies what the agent wrote — the interface source for a native canvas, the page for a web canvas.
ExpandOpens the canvas in its own tab of the side panel.

Links open in your default browser.

Safety

The agent's interface code never runs inside Neoo itself:

  • A native canvas runs its logic in an isolated background worker that has no network access, no timers, no storage and no access to your files or to the rest of Neoo. Neoo only accepts the components it knows and checks every value before drawing it.
  • If an interface stops responding, Neoo halts it after a few seconds and shows This interface stopped responding and was halted. with a Restart button. The rest of the app stays responsive and the last picture stays visible.
  • A web canvas runs in an isolated frame: no network, no forms, no pop-up dialogs, no browser storage. Scripts load only inline or from a few public library sites (jsDelivr, unpkg, cdnjs, esm.sh).

Before showing a canvas, Neoo checks it. If it contains broken code or loads a script from a site that isn't allowed, the card says Canvas "…" was not shown with the reason, and the agent usually fixes it and tries again. If something fails while the canvas is running, a warning line such as Canvas error: … appears under it; if the interactive part cannot start at all, Neoo shows the canvas text with Interactive view unavailable: ….

Limits

  • A web canvas grows with its content up to 2,000 pixels tall.
  • Canvases appear in desktop, Remote, the web companion and the iOS/Android app, including Agent and Bot conversations. Saved canvases load their full content automatically when the host is reachable. Follow-up actions require a writable conversation and an idle agent.