connecting

RAM

Live look at what the daemon has in memory right now. Volatile — wiped on restart. Start a run from the dashboard; results, commit SHAs, and replayable history live there too (and on disk at .ralph/iterations.jsonl).

segment — · — / —
loop modeidle
runner—
runner pid—
runner rss—
events0 / 0
updated—
How to use
live · volatile · wiped on restart
  1. 1

    Start a run

    Open the dashboard, pick a runner (Claude / Codex / Aider / custom), click Start.

  2. 2

    Watch it stream

    Panels below fill in over WebSocket as iterations run. No refresh needed. "No data" = loop hasn't started.

  3. 3

    Find results

    This view is RAM-only. Past iterations, commit SHAs, validation outputs, and replayable history live on the dashboard timeline and on disk at .ralph/iterations.jsonl.

Agents
8 specialized agents. Click any card to drill into its prompt + decision history.
8 agents · idle
Memory pressure
% of the shared segment and event ring buffer in use right now.
—
Shared memory segment
Raw hex + decoded JSON of the live blackboard the 8 agents read & write.
unknown —
name—
size—
used—
updated—
hex preview —
No segment data.

Start the loop to populate the shared segment with live blackboard JSON.

decoded payload JSON 
—
Process monitor
Live runner PID, RSS, runtime, last exit code.
stopped
No active runner process.

Configure RALPH_RUNNER_CMD and start the loop to see live PID, RSS, and runtime stats.

Live blackboard
—
Event stream
0 events
  • No events yet.

    Events appear when the loop boots, iterations begin and end, validation runs, scratchpad notes are pinned, or checkpoints are taken.

Scratchpad
volatile
0 / 2000
  • Nothing pinned.

    Scratchpad notes are RAM-only — useful for "the spec is wrong" reminders during a session.

Checkpoints
0 checkpoints
  • No checkpoints yet.

    Snapshot the repo + plan + prompt to compare later. Checkpoints live in memory only and disappear on daemon restart.