Skip to content
Runnit Docs

Component Builder

The Component Builder lets you author custom pages and dashboard widgets by chatting with an AI agent inside Runnit Studio. The agent runs entirely in-app and drives a full plan → build → test → review → refine loop, streaming its progress into the chat as it works.

How the agent works

Section titled “How the agent works”

Each message you send is routed by intent:

  • Questions (“why did the build fail?”, “what data does this widget use?”) are answered directly. The agent may read your files and query data to ground its answer, but makes no changes.
  • Create or modify requests (“add a chart”, “restyle this”, “fix the totals”) trigger the full build loop:
    1. Plan: a short plan that ends with explicit acceptance criteria.
    2. Validate: confirms the real data fields exist before writing data-bound UI.
    3. Build: writes the component and compiles it.
    4. Review & refine: checks the result against the acceptance criteria and iterates until it is done.

When you build task views, tell the agent how backlog work should appear. A task can have no assignee, estimate, or planned dates. Components should show a clear Unscheduled or Unassigned value instead of inventing dates or hiding the task.

Components can also read a project’s discussion, which is the project’s own conversation together with the comments on its tasks. Ask for a project status or latest-updates panel and the agent can show real messages with their author and time, rather than only counts and dates.

Working with it

Section titled “Working with it”
  • Paste images into the chat for visual references.
  • Switch between past conversations for a component from the chat history.
  • Watch the live phase indicator to see whether the agent is planning, building, or reviewing.
  • Long build sessions keep working. When a conversation grows very large, the agent automatically condenses older tool output (you’ll see a short note in the chat) and continues instead of stopping with a context error.

If a saved component’s preview bundle is missing, the editor automatically rebuilds it once from the saved source files. A successful rebuild reloads the preview. If the rebuild fails, review the displayed build errors, correct the source, and choose Build to try again.

Built components are stored as versioned artifacts and can be published to your organisation. See Runnit Studio for the artifact types and how widgets reach dashboards.