Output & rendering

Replies render in place, inside the panel: code is highlighted, formulas compose, diagrams draw themselves. Everything happens locally — no rendering service involved.

One reply: highlighted code, a KaTeX formula, and a Mermaid diagram rendered in place — One reply: highlighted code, a KaTeX formula, and a Mermaid diagram — rendered in place.

Streaming replies & queued follow-ups

Replies stream in token by token; Esc or the ✕ stops them anytime. You can keep typing while a reply streams — messages queue up automatically and send in order the moment the reply finishes.

Markdown & code

Full GFM: tables, task lists, nested quotes;
Syntax highlighting for 40+ languages; diff blocks color + green and - red;
⎘ copies the complete raw Markdown of any reply;
Hover any message to see when it was sent.

LaTeX formulas

Inline $...$ and display $$...$$ both render via KaTeX. Formula-heavy messages are automatically offloaded to a Web Worker so the panel never janks.

Diagrams: flowcharts · charts · mind maps

Just ask — "draw a flowchart of this table", "turn this outline into a mind map". The model emits a code block in the matching format and browsa renders it in place:

```mermaid — flowcharts / sequence diagrams;
```echarts — charts;
```markmap — mind maps.

Each diagram gets a hover toolbar: zoom, copy source, export SVG. When a Mermaid block fails to parse, a one-click button sends it back to your model for repair — the fixed diagram is validated locally before it replaces the broken one.

Follow-up: go deep on a selection

Select any text inside a reply and a "follow-up" entry appears — a scoped side-conversation about just that excerpt. Follow up freely; the main history stays untouched. The card is resizable.

Outline navigation

After 4 turns a quiet tick rail appears: click to jump to a turn, hover to preview it. No more scroll-wheel archaeology in long conversations.

Fixing & redoing

✏ Edit & resend: revise any message you sent and restart from there;
⟳ Regenerate: re-run any reply;
Error cards: when a provider errors, you get a plain-language headline first (auth / rate-limit / timeout / network / 5xx), with the raw error folded below — expandable and copyable.