Prompt Jump

Find your prompts. Keep your place. Leave the conversation untouched.

Prompt Jump adds a one-line sticky prompt strip and keyboard navigation to Pi's fullscreen conversation. It scrolls the displayed branch; it does not resend a prompt, fork a session, change model context, or edit history.

v0.1.0, licensed under MIT. Currently supported: Pi 1.1.0, fullscreen mode only. Component tests and an automated real-CLI pseudo-terminal smoke test passed; a synthetic long-session benchmark is recorded. See TEST-RESULTS.md for evidence and limits.

Features

• Jump to the previous or next user prompt with Alt+Shift+↑ / ↓ (Option on macOS).
• Pick a prompt with /prompt-jump list.
• See the prompt at or above the viewport in a sticky strip; click it to jump to its beginning.
• Return to the position before your most recent prompt jump with /prompt-jump back.
• Resume following new output with /prompt-jump end.
• Recognize native skill invocations and label matching prompt templates by slash-command name.
• Recompute positions from rendered heights, including wrapped text and expanded tools.

Install

pi install npm:pi-prompt-jump@0.1.0

Or install from GitHub:

pi install git:github.com/rrrrrrrrrricoxi/pi-prompt-jump@v0.1.0

Requires Pi 1.1.0 fullscreen. Installation adds the package to your Pi settings. Do not enable it alongside the original sticky-prompt-strip addon: they share commands and layout integration.

The pi-package keyword makes the npm package eligible for Pi's official catalog. Catalog indexing can lag behind publication.

Try the source without installing

From this directory, start a separate Pi invocation with only this extension:

pi --no-extensions --extension ./index.ts --tui-mode fullscreen

This does not add the package to your settings. Other normally discovered extensions are disabled for that invocation. Do not load Prompt Jump alongside the original sticky-prompt-strip addon: they own the same navigation commands and layout integration.

Source repository: rrrrrrrrrricoxi/pi-prompt-jump. npm package: pi-prompt-jump.

Commands

Command	Action
/prompt-jump or /prompt-jump current	Beginning of the prompt at or above the viewport
/prompt-jump prev	Nearest prompt beginning strictly above the viewport
/prompt-jump next	Nearest prompt beginning strictly below the viewport
/prompt-jump last	Last text/skill prompt in the displayed branch
/prompt-jump list	Prompt picker; Escape cancels
/prompt-jump back	Restore the position before the most recent prompt jump, including follow-end state
/prompt-jump end	Bottom of the conversation; follow new output
/sticky-prompt	On/off menu
/sticky-prompt on / off	Enable the strip or restore the previous layout
/sticky-prompt status	Report preference and whether the strip is actually mounted

Shortcuts depend on your terminal forwarding modified arrow keys. If the terminal or OS intercepts them, use the slash commands. Editor focus is not moved by a strip click.

Compatibility and limits

This is version-specific UI integration, not a stable public transcript-navigation API. It uses public layout/scroll operations but also inspects Pi 1.1.0's mounted root and user/skill component shapes. Other host versions do not mount the strip. Regular terminal mode, RPC, JSON, and print modes do not offer navigation. Settings/status commands remain available.

• Only prompts represented by recognized text/skill components in the currently displayed branch are navigable. Image-only prompts are not indexed.
• The strip is hidden below eight terminal rows.
• Session switches and tree navigation clear the return position and invalidate an open prompt picker.
• Only one return position is stored, not a back-stack. Resizing or changing rendered heights can shift that row-based return position.
• Root replacement by another extension can unmount the strip. Check /sticky-prompt status; /sticky-prompt on attempts to mount again. Cleanup never overwrites a foreign replacement root.
• Collection walks and renders the displayed component tree to calculate positions. In a synthetic benchmark, warm collection medians were about 0.61 ms at 1,000 prompts and 5.6 ms at 5,000 prompts; cold collection/resize reached hundreds of milliseconds at 5,000 prompts. These are local fixture measurements, not complete frame timings or a performance guarantee. See TEST-RESULTS.md.
• Template recognition is conservative and heuristic: it reads registered prompt-template files, ignores short/dynamic-only templates, and matches fixed segments. An unrecognized template shows its first text line instead.

No Pi installation files are patched. No runtime dependencies are bundled; Pi supplies its own host modules.

Local state and privacy

Prompt Jump reads displayed prompt text in memory and registered prompt-template files. It displays first-line labels in the terminal; those labels may appear in screenshots or terminal recordings.

The extension makes no network requests and registers no model tools. Only an on/off preference is persisted, at pi-prompt-jump.json in PI_CODING_AGENT_DIR (normally ~/.pi/agent). This is separate from the original addon's preference file. Session content and navigation bookmarks are not written to that file.

As with every Pi extension, it runs with the host process's permissions; these design limits are not a sandbox.

Tests

Run tests from the source checkout; the distributable package omits the test harness. Tests use an already installed Pi 1.1.0 and its real components/themes, with a simulated fullscreen root/terminal and isolated temporary preferences. No dependency installation or model call is needed.

If Pi is resolvable locally:

npm test

Otherwise supply the installed package directory (the directory containing Pi's package.json and dist/):

npm test -- /path/to/installed/pi-coding-agent

Coverage includes navigation, wrapped/Unicode text, ANSI sanitization, skill anchors, real light/dark/system themes, truecolor/256-color widths, click focus behavior, shortcuts, menu cancellation, preferences, picker invalidation, lifecycle cleanup, layout ownership, and unsupported renderer guards.

Additional source-checkout tests run the actual installed CLI in an isolated POSIX pseudo-terminal and measure rendered-component collection:

npm run test:terminal -- /path/to/installed/pi-coding-agent
npm run test:benchmark -- /path/to/installed/pi-coding-agent
npm run test:package -- /path/to/installed/pi-coding-agent

The package test creates an offline npm archive, checks its exact file list, extracts it, and reruns the terminal suite against the shipped entry without installing dependencies.

The terminal suite requires Python 3 on a POSIX system. It uses temporary HOME/settings/session directories, a local deterministic streaming fixture, and a fail-closed network guard—no real provider credentials or model calls. The fixture/probe is excluded from the extension manifest and npm file list. It verifies actual CLI keyboard/mouse routing, resize, reload, session/tree navigation, and a 1,000-prompt session. It does not prove OS shortcut forwarding, physical trackpad behavior, every terminal application, or third-party extension compatibility.

See TEST-RESULTS.md for observed results and RELEASE-CHECKLIST.md for publication gates.

Distribution

package.json declares a Pi extension entry and the pi-package keyword. According to Pi's package documentation, the keyword makes an npm package eligible for discovery in the official package catalog. A GitHub-only release is installable via Git but is not the documented catalog route.

The manifest declares MIT (see LICENSE). The release includes no runtime dependencies or test-only provider code.