inspect-robots-wandb
The inspect-robots-wandb plugin logs Inspect Robots evaluation summaries to
Weights & Biases.
Install
pip install inspect-robots-wandb
wandb login
The plugin registers the wandb sink in the inspect_robots.sinks entry-point
group, so after installing it the sink appears in inspect-robots list and
resolves by name.
Use from Python
Passing sinks= replaces the default JSON sink, so include both sinks when you
want the local immutable log and the W&B summary:
from inspect_robots import eval
from inspect_robots.logging import JsonLogSink
from inspect_robots_wandb import WandbSink
logs = eval(
"cubepick-reach",
"scripted",
"cubepick",
sinks=[
JsonLogSink("logs"),
WandbSink(project="robot-evals", tags=("cubepick", "nightly")),
],
)
WandbSink creates one W&B run for each evaluation lifecycle. It stores the
evaluation specification as run config, then logs final status, scene and trial
counts, errored trials, total steps, duration, and every aggregate result metric.
The same sink instance can be reused by eval_set(); each task receives its own
W&B run.
Warning: The evaluation specification is uploaded as W&B run config. Keep credentials and other secrets out of policy and embodiment configuration.
If an evaluation aborts with an exception, the sink logs eval/status: error
with the exception text and finishes the run with exit code 1. This needs an
inspect-robots core with the optional on_eval_error sink hook. With older
cores the sink still works, but an aborted run is left for the W&B SDK to close
when the process exits.
Use mode="offline" to write a local W&B run for later synchronization, or
mode="disabled" to exercise the integration without recording data.
Configuration
| Argument | Default | Meaning |
|---|---|---|
project |
inspect-robots |
W&B project name. |
entity |
unset | W&B team or user name. |
name |
unset | Display name for the run. |
group |
unset | W&B run group. |
tags |
unset | Sequence of W&B tags. |
mode |
unset | W&B mode such as online, offline, or disabled. |
dir |
unset | Local directory used by W&B. |
Development
uv sync --extra dev
uv run ruff check . && uv run ruff format --check . && uv run mypy
uv run pytest
The tests replace the W&B SDK with an in-process double, so they need no network access or W&B account.
License
MIT
Metadata
Release files for inspect-robots-wandb 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| inspect_robots_wandb-0.1.0.tar.gz | 7.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inspect_robots_wandb-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / inspect_robots_wandb-0.1.0.tar.gz
| Download URL | inspect_robots_wandb-0.1.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd92b969bb2426bc738cfbbe9c36e61146c14fced1b6594084d1b4aab8e30062
|
|
BLAKE2b-256 checksum How to use checksums |
1cc2fef5f2c2c852bfd405e630d1d0836ed1e50c04d1c87427aad713587c92d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logRelease files / inspect_robots_wandb-0.1.0-py3-none-any.whl
| Download URL | inspect_robots_wandb-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fee8d3d90ad968f92c8ea1787325e966f0d39bed841bc54e9ffae75bc1a37195
|
|
BLAKE2b-256 checksum How to use checksums |
8f59d08038ecf21d0d49556da56a361429ec11432a0fc48b091406d659b04bc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency log