Creytix
Sign in
Creytix DevPreview

IDE widgets

Agents surface work as rich inline widgets — charts, tables, diagrams, screenshots — instead of walls of text.

AI

Preview — early access.

Overview

Ask a Creytix Dev agent a question and you shouldn't have to squint at a scroll of raw text to find the answer. When the result is naturally visual, the agent renders it that way — a chart instead of a table of numbers in prose, a diagram instead of a paragraph describing how pieces connect, a screenshot instead of "here's what the page looks like now." You stay in the chat and see the work, not a description of it.

How it works

  1. An agent finishes a step that has a visual shape — data, a flow, a before/after, a rendered page.
  2. Instead of describing it in text, it renders an inline widget matched to the content: a chart for numbers, a table for structured data, a diagram for flows or wiring, a screenshot for visual state.
  3. The widget appears directly in the chat thread, in line with the conversation, so you never leave the IDE to see it.
  4. Widget rendering plugs into the same chat surface used for Review Gate decisions.

Steps

  1. •

    Ask Creytix Dev for something visual

    Request a summary, a comparison, a diagram, or a look at a page or result.

  2. •

    The agent picks the right widget

    Based on what it's showing you, the agent chooses a chart, table, diagram, or screenshot rather than defaulting to plain text.

  3. •

    Read it inline

    The widget renders directly in the chat — no separate tab, download, or export needed.

  4. •

    Keep going in the same thread

    Ask follow-up questions or hand off a decision through Review Gate without losing your place.

Capabilities

  • Charts — numeric results rendered visually instead of as a table of digits in prose.
  • Tables — structured data laid out for scanning, not buried in paragraphs.
  • Flow and wiring diagrams — how pieces connect, shown as a diagram rather than described in sentences.
  • Screenshots — a look at current visual state without leaving the chat.
  • Review Gate integration — the same inline surface used for human-decision cards.

Limits & honest scope

Widget rendering is aimed at non-technical readers who want to see the result of a task, not parse it out of text.

  • The set of widget types is still growing — not every kind of result has a dedicated visual yet, and some responses will still be plain text.
  • Widgets summarize; for a full data export or a production report, you'll still want a dedicated tool.
  • Rendering quality depends on the agent choosing the right widget for the content — this matching is still improving.

Related