Reading output

When a cell runs, its output shows up underneath. Clusy renders it richly instead of dumping everything as text, so a DataFrame looks like a table and a plot looks like a plot.

DataFrames

A returned DataFrame renders as a table, with sticky headers, zebra rows, and horizontal scroll for wide frames. It's built for actually looking at the data, and large frames are handled without locking up the notebook.

Charts and images

Plotly figures render inline and stay interactive, so you can hover, zoom, and pan. Static plots (matplotlib and friends) render as images, as do any images your code produces from a file, a URL, or raw bytes. The chart libraries load only when a cell produces a chart, so notebooks without plots stay lean.

Training and progress

Long loops get proper treatment instead of scrolling text. tqdm-style loops render as a compact, updating bar. Training runs show as a card with the metrics that matter, like loss, epoch, and step, including a dedicated view for Hugging Face Trainer runs. A long training run stays readable.

Text and logs

Plain text and print output render as text. Terminal color codes are interpreted, so colored logs show up colored instead of as escape gibberish.

Errors

When a cell raises, you get the full traceback, formatted and readable, with the failing output marked. This is also what the agent reads when it goes to fix the problem, so if you ask it to, it's working from the same trace you're looking at.

Rich objects

Objects that know how to render themselves (HTML, SVG, custom displays) show up that way in a sandboxed frame, rather than as a bare repr.