Tavina

Canvas and rendered content

📖 This content is synced from the Tavina Handbook.
The canonical version always lives at https://tavina.ai/docs/friendly/tools/canvas

Canvas and rendered content

Some Tavina planning notes use the word Canvas for live rendered HTML, SVG, or Markdown content. In the current TavinaCore source verified for this handbook update (November 2026), there is not a standalone default toolbar tool named Canvas, and no Canvas entry exists in the toolbar’s default tool order. Rendered-canvas code exists on the backend for internal surfaces, but it does not surface as a subscriber toolbar tool.

That means Canvas should not be treated the same way as Tasks, Shopping, Notepad, Links, Routines, Calendar, Weather, Pins, or Knowledge Library until a Canvas work panel ships in source.

What this means for you

Today, if Tavina renders rich content, it may appear as part of a conversation, a preview, or another tool-specific surface rather than as a separate Canvas toolbar button.

Use the native tools for durable app data:

  • Tasks for work items.
  • Calendar for schedule events.
  • Shopping for lists.
  • Notepad for lightweight notes.
  • Links for saved URLs.
  • Knowledge Library for uploaded documents and citable Sources.

What to ask Tavina

Examples:

  • “Can you render this as a simple table in chat?”
  • “Can you make an HTML mockup I can preview?”
  • “Should this become a task, note, link, or Knowledge Library Source instead?”

If Tavina says a Canvas tool is available in your environment, ask it to open that tool and explain what can be saved there. Otherwise, treat rendered content as temporary unless you save it into a native tool or upload it to the Knowledge Library.

When this page should change

This page should be updated when TavinaCore adds a standalone Canvas native tool or a documented rendered-content work panel. The current page is intentionally conservative so the Handbook does not promise a tool that is not present in source.

Related pages

Scroll to Top