Skip to main content

Experiment Dashboard

The Experiment Dashboard replaces the traditional kanban board with an outcomes-oriented interface. Instead of tracking task status, it answers the question: which experiments worked and why? Three views serve different levels of detail:
ViewURLWho it’s forWhat it shows
Timeline/experimentsEngineers, team leadsAll experiments for an initiative with metric trends
Detail/experiments/<id>Anyone working on an experimentFull lifecycle of a single experiment
Portfolio/experiments/portfolioLeadership, team leadsAll initiatives at a glance

Timeline View

The Timeline is the main dashboard — the first thing you see when you click Experiments in the sidebar. It shows all experiments for the currently selected initiative, sorted by date or impact.

Experiment Cards

Each experiment appears as a card showing:
  • Name and creation date
  • Source type icon — research resource, hypothesis, incident, or recommendation
  • Status badge — Configure, In Progress, Complete, or Validated
  • Target metric and observed delta (color-coded: green positive, red negative, gray pending)
  • Tags for grouping

Metric Trend Chart

A line chart at the top tracks your target metric across completed experiments. This is the “are we getting better?” view — a visible trend line showing improvement (or lack thereof) over time. The chart is collapsible. When collapsed, trend values remain visible in the summary bar.
ControlWhat it does
Search barInstant filtering by name, hypothesis, initiative, or tags
Status chipsFilter by All / Configure / In Progress / Complete / Validated (with counts)
Source filtersToggle by source type
SortBy date (newest first) or by impact (largest delta first)

Creating an Experiment

Click New Experiment in the top-right corner. The create form supports multiple source modes:
Search for a paper, repo, or model by title. Remyx autocompletes from its resource index. The resource is linked as the experiment source, and a launch context is built automatically when you open the detail page.Fields: Name, Resource (search), Hypothesis, Target metric, Tags, Target repository.
After creation, you’re redirected to the experiment detail page.

Detail View

The Detail view shows the full lifecycle of a single experiment. It’s a two-column layout: main content on the left, metadata and links in the right sidebar.

Main Content

Origin Section

For research-sourced experiments, the Origin section shows the launch context:
  • Resource title with link to the resource viewer
  • Abstract excerpt — one-sentence summary (editable inline)
  • Key methods — technique badges extracted from the resource (add/remove inline)
  • Target repository — the repo where the implementation lands (change triggers context rebuild)
  • Implementation plan — AI-generated plan referencing actual file paths (collapsible, editable, regeneratable)
  • Docker image — reference to the pre-built environment (when available)
Every field is click-to-edit. Changing the target repo triggers a rebuild-context call that re-fetches the repo file tree and regenerates the implementation plan. For hypothesis-sourced experiments, the Origin section shows the hypothesis text.

Analysis Section

Combined Hypothesis and Decision in a single card:
  • Hypothesis: The team’s prediction, shown at the top
  • Decision: Logged after results are in. Includes the decision text, author, and timestamp. Click to edit.

Implement Section

A compact bar showing how to implement via Claude Code:
  • Copy-paste command to run Claude Code with the Remyx MCP connection
  • Link to the Integrations page for setup
When a PR exists, a green banner appears at the top of the page with the PR title, status, and link.

Activity Feed

A unified chronological feed combining:
  • Comments with @mention support (powered by Tribute.js), edit/delete
  • System events from the knowledge graph (experiment created, status changed, decision logged, PR opened)
SectionContents
StatusDropdown: Configure → In Progress → Complete → Validated
MetricTarget metric dropdown, observed delta, confidence
ResourcesLinked artifacts: PR, ticket, repo, dataset, tracking run, other
Related ExperimentsBidirectional linking with cross-project search
ProjectInitiative context from project settings
TagsEditable tag list

Linked Resources

The Resources section shows all external artifacts connected to this experiment:
  • GitHub PR: Link and status, auto-synced via webhooks
  • Linear / Jira ticket: Link and status, auto-synced via webhooks
  • Target repo: The implementation repository
  • Dataset: Link to dataset used for evaluation
  • Tracking run: Link to MLflow or other experiment tracking
  • Custom links: Any other URL with a label

Portfolio View

The Portfolio view is designed for leadership — people who need to see all initiatives at a glance without diving into individual experiments.

Initiative Cards

Each initiative appears as a row showing:
ColumnWhat it shows
NameInitiative name (e.g., “Customer Support AI”)
StatusHealth dot: green (on track), yellow (needs attention), red (stalled)
ExperimentsTotal count
Hit RateBar showing positive / total completed experiments
Metric TrendSparkline showing target metric over time
DeltaOverall metric change (e.g., “34% → 52%“)
FocusMost common tags from recent experiments
Click any row to switch project context and navigate to that initiative’s Timeline.

Creating Initiatives

Click Create Initiative to set up a new project. This redirects to Project Settings where you configure:
  • Initiative name and description
  • Allowed metrics (dropdown options for experiments in this initiative)
  • Linked GitHub repos
  • Linear project connection
  • Data sources
  • A/B testing provider

Insights View

Navigate to Insights in the sidebar to see cross-experiment patterns for the current initiative.

Pattern Clusters

Each cluster appears as a collapsible row:
ElementDescription
Tag nameThe grouping tag (e.g., “retrieval”)
Signal badgeHIGH (green), LOW (red), or MIXED (yellow)
Hit rate”5 of 5 positive”
Avg deltaAverage observed improvement
Experiment countNumber of experiments in this cluster
Expand a cluster to see:
  • Experiment list: Each experiment with its delta, status, and decision summary
  • Recommended resources: Research-backed next steps matched to this direction

Starting from a Recommendation

Each recommended resource has a Start Experiment button. Clicking it creates a new experiment with:
  • The resource linked as the source
  • The cluster’s tag pre-filled
  • The current initiative selected
This is the fastest path from pattern insight to next experiment.

Keyboard Shortcuts

ShortcutAction
/Focus the search bar
nOpen the New Experiment form
EscClose modals and edit modes

Next Steps

Integrations

Connect GitHub, Linear, Jira, Slack, and Claude Code

ExperimentOps Concepts

The methodology behind the dashboard

MCP Server

Automate experiment workflows via MCP

API Reference

REST API documentation