pi extension/package for managing ralph loops from inside the pi TUI.
- Status widget below the editor when loops exist
/ralphoverlay to inspect loops, follow logs, and run common loop actionsralph_loop(...)LLM tool to start loops in a PTY (so the native ralph TUI can be embedded)
pi(works with the current pi package system)ralphon yourPATH(tested withralph 2.4.4)
pi install npm:@rhobot-dev/pi-ralphpi install ~/projects/pi-ralph- Start
piin a project whereralphworks (has aralph.yml). - When loops exist, a small status widget appears below the editor.
- Open the loop manager overlay:
/ralph
Overlay:
Escclose (or back out of confirm/subviews)←/→switch focused loopShift+Up/Downscroll (PTY)sstop (confirm withy/n)mmergeddiscard (confirm withy/n)rretryHhistory view (qback, arrows orj/kscroll)Ddiff view (qback)aattach a shell in the loop's directory/worktree
Main editor:
Ctrl+Shift+Rcycle focused loop
The extension registers a tool:
ralph_loop(prompt, directory, config?, maxIterations?, backend?, customArgs?)
This spawns ralph run in a PTY so the native ralph TUI can be embedded in the overlay.
ralph loops list --jsonmay label the in-place loop as(primary). For commands that require an actual loop ID (history/diff/logs/retry), pi-ralph attempts to resolve it from.ralph/current-loop-id.- If
ralphis not found onPATH, the extension disables itself gracefully.
This repo publishes to npm via GitHub Actions.
- Bump
package.jsonversion. - Commit.
- Tag and push a matching
v*tag:
git tag v0.1.0
git push origin v0.1.0The workflow supports npm Trusted Publishing (OIDC). Configure it in npm package settings (Trusted Publisher: GitHub Actions). If you haven't set that up yet, the workflow falls back to NPM_TOKEN.
