The Agent doesn't answer — it builds the UI to answer with
Most AI chat products give you text back, maybe a code block. We wanted Kopai's agents to answer the way a good analyst would — with the actual chart, table, or calculator, not a paragraph describing one.
So when an agent decides a visual beats prose, it writes real render-able code and it renders live in the chat — inline, not a separate canvas. It runs in a sandboxed iframe with a null origin, so the generated code can't touch your cookies or session, even though it's fully interactive. It also picks up your theme automatically, light or dark, so it never looks bolted on.
It's not one generic "chart mode" either — the agent recognizes what you're actually asking for and reaches for the right shape: an interactive widget, a chart, a diagram, a UI mockup, or generative art, and builds accordingly.
Ask your agent to "compare these three plans" or "show me how OAuth works" and watch what it reaches for instead of text.
What's the most useless "wall of text" answer you've gotten from an AI tool that should've just been a table or a chart?
Replies
the worst offender for me is anything involving pricing tiers - i've asked coding assistants to compare plan limits across providers and gotten four paragraphs of prose restating numbers i then had to re-read three times to line up mentally. that's exactly a table.
question on the sandboxing though - once the agent renders a chart from a data pull, and i ask a follow-up like "now show only Q4", does it re-run the whole generation step and re-render a new iframe, or is there some live binding back to the underlying data so it can patch the existing one? asking because if it's regenerate-from-scratch every time, that's a lot of tokens spent for what should be a filter operation.