Canvas and artifacts

Canvas gives you a dedicated workspace beside chat. When a reply becomes something you may want to keep working on, Babbily can open it as an artifact in the Canvas panel. Use Canvas for drafts, tables, code, image briefs, and structured outputs that need more than a one-time chat reply.

​

When Canvas appears

Babbily may open Canvas when you ask for substantial work that benefits from a separate editing surface. Canvas artifacts can include:

• Text drafts and documents.
• Code snippets and scripts.
• Image prompts or creative briefs.
• Tables and spreadsheet-style data.
• Structured visual outputs, such as dashboards, metrics, tables, callouts, and supported interactive views.

If a response includes an artifact card, open it to continue working in Canvas.

​

Edit directly in Canvas

Canvas lets you edit supported artifacts without copying them into another editor first. Depending on the artifact type, you can:

• Edit text or markdown.
• Adjust table-like content.
• Review code in a focused editor.
• Rename the artifact.
• Save a new version.
• Resize the side panel on desktop.
• Close the panel and reopen the artifact later.

​

Revise with the latest Canvas state

When you continue prompting in the same thread, Babbily can use the active Canvas artifact as context. That helps follow-up requests apply to the current version, including edits you made in the panel. Good follow-up prompts include:

• Make this shorter and keep the same section order.
• Turn the second section into a table.
• Update the code to accept a CSV file.
• Add a warning callout under the pricing notes.

If you want to change topics, start a new thread or close the artifact so old Canvas context does not steer the next request.

​

Use versions

Saving changes creates a new artifact version when version history is available. Use the version controls to move between earlier and later versions. Versions are useful when you want to compare a draft before and after a prompt, recover older wording, or review how a table changed.

​

Export and download

Export options depend on the artifact type. Review exported files before sharing them outside Babbily.

​

Send artifacts to connected apps

Some Canvas artifacts can be sent to connected apps from the artifact actions menu. Available destinations depend on your connected apps, permissions, and whether the connector tools are ready. If a destination is not connected, Babbily may ask you to connect it first. If an action writes to another app, review what will be sent before approving it.

​

Run code artifacts

When a code artifact supports execution, use the run action in Canvas to test it. Code execution is intended for quick checks, not production workloads. Execution support can vary by language and artifact state. JavaScript, TypeScript, JSX, TSX, and Python-like code can run through supported JavaScript or Python execution paths. Network access is unavailable during execution, and long-running code may stop before it finishes.

​

Limits to expect

Canvas availability can vary by model, plan, tool mode, and the type of work you request. Keep these expectations in mind:

• Babbily may answer in chat instead of Canvas when the request is simple.
• Structured visual artifacts may take a moment to prepare before the panel opens.
• Some generated structures are for viewing and editing, not for taking external actions.
• Export and connector actions vary by artifact type.
• Connector actions depend on your app permissions and connector readiness.