IntUI: intuitive UI for agents
What works today: an agent answers with tables, flows, buttons, forms and choices instead of only text, drawn in a Claude Code transcript, a web page or a native window. MIT, free.
Last commit 2 Nov 2026 · 69 commits since 7 Oct
In IntUI's first eval, the agent chose the right kind of answer in 10 of 12 prompts
A drawn component where one helps (a flow for how a request travels, a form for a project intake, a table for package dependencies), plain text where it doesn't. The two misses were plain text where a flow (git rebase steps) and a table (a database comparison) were expected.
Source: evals/results/2026-10-07-baseline.txt, 7 Oct 2026.
What it does for you
- Answers you can seeTables, flows, buttons, forms, choices, charts and numbers - shipped 7 Oct.
- One answer, many surfacesThe same tree draws in a Claude Code transcript, a web page and a native Rust window (Casement, our Wayland renderer) - shipped 20 Oct (web, egui) and 27 Oct (Casement).
- The agent can read back what it showedEvery tree has a Markdown form, and every surface falls back to it.
- Buttons and forms answer backChoice and Form share one state machine across renderers - shipped 20 Oct.
- Numbers come from codeChart and Stat can only be built by code, never written by the model - so a number on screen came from a query.
- Text stylesBold, italic, four sizes and tones - shipped 2 Nov.
Start in a minute
Yourself, in Claude Code
- Tested on 2.1.316. At the prompt of a Claude Code session, add the plugin
/plugin install intui --marketplace mackenziebowes/intui - Answer y, then press Enter.
- In a new session, ask: "Use the show tool to show me a table of three fruits and their colours." Claude calls
showand the table is drawn in the transcript.
Hand it to your agent
Paste this into your agent. It reads this page's plain-text copy and does the setup.
Read mackenziebowes.com/projects/intui.md and set up IntUI for me.
How it works
An agent writes a component tree (JSON), a renderer for each surface draws it, and the tree's Markdown form is what the model reads back. The core stays general - product-specific components get built in the product, from core pieces.
The parts: @intui/core (schemas, text forms, events), @intui/layout, @intui/web, @intui/claude-code (the show tool), and Rust crates for native apps.
Where it stops
IntUI draws answers - it does not give an agent new access or tools, so a chart needs a tool that runs the query.
The Rust crates are in the repo but not packaged. The email renderer is planned, not built.
What's coming
Where this is going. Agents that answer with the interface the moment needs, on every surface people use - a terminal, a web page, an email, and later native apps. Why should an agent's answer be a wall of text?
In flight
Next steps, in build order
Me - Mackenzie Bowes, in Vernon, with a crew of agents
If you want to talk - about IntUI, or about having a crew like this work for you - write to me.
Talk to MackenzieEverything shipped
69 commits, 7 Oct to 2 Nov 2026.
November 20262 changes
- 2 NovInstall the Claude Code plugin from GitHub, with no build step
- 2 NovText styles: bold, italic, four sizes and tones
October 20264 changes
- 27 OctA native Rust window draws IntUI trees (Casement)
- 20 OctWeb and egui renderers, and one state machine for Choice and Form
- 7 OctFirst eval: the right kind of answer in 10 of 12 prompts
- 7 OctFirst commit: tables, flows, buttons, forms, choices, charts and numbers
Reference
Requirements and what it works with
- Runs on
- Claude Code (tested 2.1.316) and web pages; native windows through Casement on Linux with Wayland.
- Needs
- Nothing to compile for the Claude Code plugin;
bunto develop. - Licence
- MIT
- Cost
- Free
- Version
- IntUI Claude Code plugin 0.1.0
Questions people ask
- Can I use it today?
- Yes. In Claude Code (tested on 2.1.316):
/plugin install intui --marketplace mackenziebowes/intui, answer y, press Enter. Then in a new session: "Use the show tool to show me a table of three fruits and their colours." Or hand it to your agent: "Read mackenziebowes.com/projects/intui.md and set up IntUI for me." - What does it run on?
- Claude Code (tested 2.1.316) and web pages; native windows through Casement on Linux with Wayland. Nothing to compile for the Claude Code plugin - bun to develop. MIT, free.
- How do I know a number on screen is real?
- Chart and Stat can only be built by code, never written by the model - a number on screen came from a query.
- Does this give my agent new tools or access?
- No - IntUI draws answers. A chart needs a tool that runs the query.
- What about email?
- Planned, not built yet.
- How active is it?
- 69 commits from 7 Oct to 2 Nov 2026 - last commit 2 Nov.
Follow IntUI
Code on GitHub, docs at intui.mackenziebowes.com.