nth Labs Help centre
⌘K
Open console

The console

A tour of the console

Thirteen destinations down the left. Here is what each one is for, with the screen itself.

Overview

What to do next, in one screen. Ship-blocking findings ranked by confidence, coverage underneath, and the four states a finding can be stuck in.

The console overview: five ship-blocking findings ranked by confidence, with coverage and re-check status below.
The four states across the middle are the honest ones: never re-checked, waiting on your verdict, no fix checked, nothing guarding against a repeat.

Those four are not decoration. Each is a specific gap between “the tool found something” and “this is actually handled”, and each links to the list of what is sitting in it.

Findings

Every open finding, with its surface, severity and confidence. Two views: a flat list, and a board grouped by page. Which one you are on is remembered.

The findings list: every open finding with its surface, severity and confidence score.
Ordered by confidence multiplied by severity, the same order the CLI prints.

The inspector

Clicking a finding opens it beside the list: the evidence, the selector, the confidence and the frame the browser was looking at when it filed.

A finding opened: the inspector beside the list showing the page, the severity, the confidence and the frame the browser was looking at.
The frame is the run’s own capture. When a run is deleted its screenshots go too, and the console says the captures are gone rather than drawing something.

Review

One finding at a time, keyboard-first, nothing else on screen. This is where verdicts happen, and it exists as its own screen because giving thirty findings a verdict in a list is a different job from reading one.

The review screen: one finding at a time, with keyboard shortcuts to confirm, drop or skip it.
Confirm, drop or skip without touching the mouse. The precision figure at the top is only shown once enough verdicts exist to support it.

Runs

Every run: the module, what it found, what it cost, and how long it took. Opening one gives you its report and its replay.

Run history: each run with the module it ran, what it found and what it cost.
Cost is the real figure from the provider’s usage, not an estimate.

Changes

The review loop. Every surface is captured and diffed against the accepted baseline for the branch; only what actually changed is queued.

The review loop: every surface captured and diffed against the accepted baseline.
Accept a change and it becomes the new baseline. Reject it and it becomes a finding.

This is the screen that turns “the site looks different” into a decision somebody made on purpose, with a note attached.

Reports

The assembled documents, and where you get the shareable one. See Report.

Settings

The product profile, your model keys, and the console password if you are hosting it. Nothing here leaves the machine on a local install.