View logged runs

View information about a specific run such as the state of the run, artifacts logged to the run, metrics, system metrics, and more.

You can view and monitor runs using the W&B App or the wandb beta leet terminal UI.

App

To view a specific run in the W&B App:

1. Navigate to the W&B App.
2. Navigate to the W&B project you specified when you initialized the run.
3. Within the project sidebar, select the Workspace tab.
4. Within the run selector, click the run you want to view, or enter a partial run name to filter for matching runs.

The URL path of a specific run has the following format:

https://wandb.ai/<team-name>/<project-name>/runs/<run-id>

Where values enclosed in angle brackets (< >) are placeholders for the actual values of the team name, project name, and run ID.

LEET

To view a run locally in your terminal using the wandb beta leet terminal UI:

1. If you started the run locally from a script, navigate to the directory where you ran your code. It contains a wandb/ directory with a subdirectory per run and a latest-run/ symbolic link. Each run directory contains a transaction log named in the format run-<run-ID>.wandb.

   If you did not start the run locally but downloaded a .wandb transaction log file instead, make a note of its location.

2. Start wandb beta leet using one of these commands:

   # View the latest run, stored in ./wandb/latest-run/
   wandb beta leet
   
   # Specify a run directory
   wandb beta leet ./wandb/run-20250813_124246-n67z9ude
   
   # Specify a .wandb file
   wandb beta leet ./wandb/run-20250813_124246-n67z9ude/run-n67z9ude.wandb
   
   

LEET displays a three-panel interface:

• Left sidebar: Run overview with environment variables, configuration, and summary statistics
• Center panel: Metrics grid with Braille-style line charts showing your logged metrics
• Right sidebar: System metrics including GPU/CPU/RAM utilization

Get started with these keyboard shortcuts:

• h or ? - View all keyboard shortcuts
• / - Filter metrics by pattern
• [ / ] - Toggle left/right sidebars
• n / N - Navigate between metric pages
• q / CMD+C - Quit

See the wandb beta leet reference for more details.

Overview tab

Use the Overview tab to learn about specific run information in a project, such as:

• Author: The W&B entity that creates the run.
• Command: The command that initializes the run.
• Description: A description of the run that you provided. This field is empty if you do not specify a description when you create the run. You can add a description to a run with the W&B App UI or programmatically with the Python SDK.
• Tracked Hours: The amount of time the run is actively computing or logging data, excluding any pauses or waiting periods. This metric helps you understand the actual computational time spent on your run.
• Runtime: Measures the total time from the start to the end of the run. It’s the wall-clock time for the run, including any time where the run is paused or waiting for resources. This metric provides the complete elapsed time for your run.
• Git repository: The git repository associated with the run. You must enable git to view this field.
• Host name: Where W&B computes the run. W&B displays the name of your machine if you initialize the run locally on your machine.
• Name: The name of the run.
• OS: Operating system that initializes the run.
• Python executable: The command that starts the run.
• Python version: Specifies the Python version that creates the run.
• Run path: Identifies the unique run identifier in the form entity/project/run-ID.
• Start time: The timestamp when you initialize the run.
• State: The state of the run.
• System hardware: The hardware W&B uses to compute the run.
• Tags: A list of strings. Tags are useful for organizing related runs together or applying temporary labels like baseline or production.
• W&B CLI version: The W&B CLI version installed on the machine that hosted the run command.
• Git state: The most recent git commit SHA of a repository or working directory where the run is initialized. This field is empty if you do not enable Git when you create the run or if the git information is not available.

W&B stores the following information below the overview section:

• Artifact Outputs: Artifact outputs produced by the run.
• Config: List of config parameters saved with wandb.Run.config.
• Summary: List of summary parameters saved with wandb.Run.log(). By default, W&B sets this value to the last value logged.

View an example project overview here.

Workspace tab

Use the Workspace tab to view, search, group, and arrange visualizations such as autogenerated and custom plots, system metrics, and more.

View an example project workspace here

Runs tab

Use the Runs tab to filter, group, and sort your runs.

The following tabs demonstrate some common actions you can take in the Runs tab.

Customize columns

The Runs tab shows details about runs in the project. It shows a large number of columns by default.

• To view all visible columns, scroll the page horizontally.
• To change the order of the columns, drag a column to the left or right.
• To pin a column, hover over the column name, click the action menu .... that appears, then click Pin column. Pinned columns appear near the left of the page, after the Name column. To unpin a pinned column, choose Unpin column
• To hide a column, hover over the column name, click the action menu .... that appears, then click Hide column. To view all columns that are currently hidden, click Columns.
• To show, hide, pin, and unpin multiple columns at once, click Columns.
  • Click the name of a hidden column to unhide it.
  • Click the name of a visible column to hide it.
  • Click the pin icon next to a visible column to pin it.

When you customize the Runs tab, the customization is also reflected in the Runs selector of the Workspace tab.

Sort

Sort all rows in a Table by the value in a given column.

1. Hover your mouse over the column title. A kebab menu will appear (three vertical docs).
2. Select on the kebab menu (three vertical dots).
3. Choose Sort Asc or Sort Desc to sort the rows in ascending or descending order, respectively.

The preceding image demonstrates how to view sorting options for a Table column called val_acc.

Filter

Filter all rows by an expression with the Filter button above the dashboard.

Select Add filter to add one or more filters to your rows. Three dropdown menus will appear. From left to right the filter types are based on: Column name, Operator , and Values

	Column name	Binary relation	Value
Accepted values	String	=, ≠, ≤, ≥, IN, NOT IN,	Integer, float, string, timestamp, null

The expression editor shows a list of options for each term using autocomplete on column names and logical predicate structure. You can connect multiple logical predicates into one expression using “and” or “or” (and sometimes parentheses).

Group

Group all rows by the value in a particular column with the Group by button above the dashboard.

By default, this turns other numeric columns into histograms that each show the distribution of values for that column across the group. Grouping is helpful for understanding higher-level patterns in your data.

The Group by feature is distinct from a run’s run group. You can group runs by run group. To move a run to a different run group, refer to Assign a group or job type to a run.

Logs tab

The Log tab shows output printed on the command line such as the standard output (stdout) and standard error (stderr).

Choose the Download button in the upper right hand corner to download the log file.

View an example logs tab here.

Files tab

Use the Files tab to view files associated with a specific run such as model checkpoints, validation set examples, and more

View an example files tab here.

Artifacts tab

The Artifacts tab lists the input and output artifacts for the specified run.

View example artifact graphs.

Export runs table to CSV

Export the table of all your runs, hyperparameters, and summary metrics to a CSV with the download button.