What the Console tab does

The Console tab in the bottom drawer is a live, in-app dev console for the sandboxed playground iframe. Any call to console.log, console.info, console.warn, console.error, or console.debug in your playground JS shows up here in real time, even though the iframe has sandbox set to null origin and you can't open the browser devtools against it directly.

Opening it

Open the bottom drawer and click the Console tab (next to Keys and Inspect). The drawer expands; the Console list takes the full panel height.

What you see

Each log entry shows the level (log / info / warn / error / debug), an HH:MM:SS timestamp, and the message.
Multi-argument calls (e.g. console.log('user', user)) are joined into one entry. Objects are pre-serialized in the iframe before being posted to the parent — we don't ship live references across the postMessage boundary, so you'll see them as JSON strings rather than expandable trees.
Levels are colour-coded; error entries also stand out so you can scan quickly.

Clearing

Click the Clear button in the console toolbar to drop everything currently rendered. Logs are not persisted server-side, so a tab refresh or a navigation also clears them.

What gets captured

Captured: any console.* call from your authored JS, plus any console.* call from libraries you load via <script> tags inside your HTML.
Not captured: uncaught exceptions, network errors, and browser-issued warnings (CSP, mixed content, deprecation). Those still show up in the real browser devtools.
Not captured: logs from inside cross-origin iframes you embed inside the playground.

Tips

Use console.warn and console.error for signals you actually care about — they're visually distinct and easy to scan when you're debugging a sheet renderer or an SDK call.
If you're trying to figure out why a workflow trigger isn't firing, log inside flowfn.onResponse((res) => …) — you'll see the raw workflow_run_ids or error the engine returned.
Console output is local to your editor session. Public visitors viewing the published playground at /p/<slug> never see your console logs — but their browser devtools will, so don't console.log secrets.