RunShelf
RunShelf brings configuration, source context, selected metrics, and artifact references together without copying checkpoints into another service.

At a glance
- For
- Researchers revisiting local and remote experiment records
- Primary use
- Find a failed run, inspect its context, and follow references back to the original artifacts.
- Product status
- In development
- Platforms
- macOS · CLI
Overview
The macOS app and Python package treat files as the source of truth. Run records remain inspectable without requiring a cloud backend.
Example workflow
Example workflow
Use an example workspace to inspect one failed run without exposing remote infrastructure.
Open the run list
Compare completed, running, and failed example records.
Choose the failure
Focus on one failed run that needs inspection.
Review run context
Check configuration, example source commit, and selected metrics.

Inspect the context around one failed run. Run names, commits, metrics, and reference URIs are deterministic demo data. Follow references
Inspect privacy-safe artifact references without copying a checkpoint.

Follow privacy-safe references without moving large artifacts. Run names, commits, metrics, and reference URIs are deterministic demo data.
Key features
- Completed, running, and failed run states
- Configuration and source context
- Selected metric summaries
- External artifact references
- Local file-backed records
Data and privacy
The approved screenshots use Example data and reference:// identifiers. The private repository URL and real remote paths are omitted.
Tech stack
Languages
- Python
- Swift
Interface
- SwiftUI
Technology icons are repository-owned category symbols; the verified technology name remains visible.
Studio relationship
Studio may show a compact recent-run summary and open RunShelf; it does not own run indexing.
Current state
Run records, metadata, metrics, ideas, and artifact references are available in the standalone local app. Studio summaries remain under review.
Current limitations
- A stable selected-run route is not yet available for Studio.
- Distribution and app identity still need final review.
Technical notes
- Python owns the file-backed run model and CLI.
- SwiftUI presents the macOS browser.
- Checkpoints remain references rather than copied assets.
Next milestones
- Add a stable selected-run route.
- Complete local distribution checks.
Technical facts
- Source provenance
- Private source repository
- Source commit
7657067cfeae- Studio integration
- Under review
- Content reviewed
- Jul 12, 2026
