Skip to main content
research.prbe.ai Everything the CLI, SDK and agent plugin record lands here. Nothing in the dashboard is a separate store — it reads the same API.

​
The surfaces

The sidebar holds Assistant, Projects, Data and Notes. Team, Workspaces, Settings, Integrations and Install sit in the account menu.

Projects

The workspace canvas, and each project’s page: metrics, experiments, runs, papers and its summary.

Experiments and runs

Experiment comparisons, run detail, lineage, spans, trials and logs.

Charts

Curves, stat tiles, expression panels, zoom, and the captured rows behind them.

Data

Datasets, checkpoints and sources, where each came from, and the files on every entity.

Search and Ask

Find work by name, or ask about it in plain words.

Assistant

Ask questions of your lab’s history, and review the changes it proposes.

Workspaces and team

Shelves, write permissions, members, devices, AI agents and settings.

Integrations

GitHub, Weights & Biases and Benchling.
Notes gathers the team note and every project, experiment and run note in one place. See notes.

​
The workspace canvas

Projects opens on the workspace canvas: one board with every project in the workspace, its experiments and runs inside it, and the recorded links between them drawn as arrows. Choose All workspaces in the workspace menu for one combined board.
  • Move around. Drag to pan, scroll or pinch to zoom, and use −, + and Fit at the bottom right. Cmd/Ctrl+drag rearranges projects and experiments; hold Alt/Option to skip snapping. Positions and the camera are saved in your browser, per workspace.
  • Zoom changes the drawing. From 45% up, project frames show their experiments and runs, plus a collapsed Research papers list where the project has papers. Between 20% and 45%, projects become titles grouped by meaning on coloured backgrounds; click a group to filter the board to it. At 20% and below, each group becomes one label with its project and run counts.
  • Filter by time. Live, 24h, 7d, 30d or All (the default), at the bottom left.
  • Read a link. Hover an arrow for its Link popup: the stored reason, when its writer gave one, and one word for where the link came from — Fork, Agent, SDK, Person, Backfill or Session. Click the arrow to pin it.
  • Open anything. Click a project, experiment or run to open its page. Hover a project or run for a preview.
The Search / Ask bar stays open at the bottom of the canvas, and Cmd/Ctrl+K focuses it. A search highlights its matches on the board and keeps your zoom. The Workspace details pane beside the board holds the workspace overview and a project directory, newest first. The canvas is on for everyone. To go back to the Projects list, turn off Workspace canvas in Settings → Preferences. With the canvas on, a project’s own page also has an Overview / Canvas toggle: the canvas shows its experiments and runs, or its papers on a research project.

​
Things worth knowing up front

Projects, the canvas and Search are all filtered by the workspace you are in. Choose All workspaces for cross-workspace discovery — a project you cannot find is usually a project filed somewhere else.Your selection persists. A missing selection falls back to the oldest workspace.
A project’s or experiment’s Summary is written by the recorders — the Probe daemon’s writer, or an agent working inline — as work happens. There is no regenerate button, and nothing is queued: an entity nobody has written up yet says “No summary yet.” The page history labels each write by who made it and from where (via daemon, via cli).See summaries.
Expression panels carry an ƒ chip; derived series carry a derived chip with producer and computed-at on hover. Grouping, smoothing and pivoting are never presented as source rows, and a panel’s value table is labeled computed.This is a hard rule throughout the dashboard: post-hoc numbers do not masquerade as training-loop capture.
Every member of the team reads every workspace. What a workspace can restrict is who may edit what is filed in it. See workspaces.
A failed load renders as a failure, never as “nothing here”. “No papers recorded” on a project that has papers would be a confident lie about your own data, so the two states are kept distinct everywhere they appear.

​
Getting set up

Install, in the account menu, carries the one command you need and nothing else — everything that used to live in collapsed “if something is not working” sections now lives in the wizard, which can act on the state instead of describing it.