Diagrams, charts and rich answers

What the assistant can render beyond plain prose.

Answers are not limited to text. When the assistant produces structured output, AODex renders it properly rather than dumping the markup at you.

Code

Code blocks are syntax-highlighted and set in a monospaced face, with copy-to-clipboard. Inline code is marked up distinctly from prose.

Diagrams

Mermaid diagrams render as diagrams — flowcharts, sequence diagrams and the rest. Ask for one directly (“draw this as a flowchart”) and you get a picture instead of a code block.

If the syntax is malformed you will see Could not parse Mermaid diagram; ask the assistant to fix it and it generally can.

Charts

Numeric results can come back as charts rather than tables. You will see Generating chart… while one is being produced.

Mathematics

LaTeX renders as typeset mathematics. LaTeX Source reveals the underlying markup and copies it, which is what you want when the destination is a paper rather than the screen.

Cards

Some answers arrive as purpose-built cards rather than prose — comparisons, timelines, maps, polls, weather, recipes, and a Sources card for cited research. Maps offer Open in Maps.

Cards are a rendering of the answer, not a separate feature to turn on. Asking for a comparison of three options may produce a comparison card; asking the same thing differently may produce a table. Both are fine.

When a card will not render

An occasional malformed payload produces Invalid chart data, Invalid comparison data or similar. The answer is still there — ask the assistant to present it as plain text or a table.