bermudis-pi-goodies

A bundle of small, frequently-used Pi extensions. One entry point, eleven independent features.

| Feature | Command / hook | What it does | | ------------------ | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | copy-with-model | /copy-with-model | Copy last assistant message to the clipboard in a code fence tagged with the model name. | | copy-trajectory | /copy-trajectory [thinking] | Copy the whole conversation (user + assistant text, tool calls stripped) to the clipboard; thinking also includes assistant thinking blocks. | | name-with-ai | /name-with-ai [name] | Generate a short session name from the first user message (or set one manually). | | zed | /z | Open Zed editor on the current working directory. | | prefer-tools | hook (no command) | Nudge toward modern CLIs: rg over grep, fd over find, uv over bare python/pip/pytest/mypy. | | keep-model-on-new | hook (no command) | Keep the active model when /new starts a fresh session instead of reverting to pi's saved default model. | | clean-tui | tool overrides (no command) | Collapse built-in tool output for a cleaner TUI: back-to-back same-tool calls with no prose in between share one block (e.g. read ×2); visible text (assistant prose or a typed user message) always breaks the block, so textless tool-only messages chain. Images stay visible without expanding, expand a row with ctrl+o to see results/diffs. Long bash commands get an AI-generated summary once you pick a model with /goodies summary-model <provider/model> (see "Smart summaries" below). While enabled, also flips @bermudi/pi-codex's apply_patch/web_search into the same burst style. | | review | /review, /end-review | Code review workflow: review uncommitted changes, a branch, a commit, a GitHub PR, or folders. Prioritized findings with actionable follow-ups. | | kilo | provider | Access Kilo Gateway models via /login kilo or KILO_API_KEY. | | provider-balance | footer (no command) | Show remaining Kilo or OpenRouter credits, z.ai token-plan quota, or OpenAI Codex quota on the right side of the working-directory footer line. | | tps | hook (no command) | Notify tokens/sec and in/out/cache token usage at the end of each agent turn. | | goodies | /goodies | Toggle individual features on/off without losing the rest. Also supports /goodies summary-model [provider/model] to pick the model used for AI bash-command summaries. State persists to ~/.pi/agent/goodies.json. |

Install

After publishing the package to npm:

pi install npm:[email protected]

Remove any old bermudis-pi-goodies.ts symlink before reloading Pi. Each feature is independent — use /goodies disable <name> to turn one off without losing the rest (e.g. /goodies disable clean-tui keeps kilo and the balance footer). State persists to ~/.pi/agent/goodies.json. Kilo's provider and its balance footer are bundled here.

Smart summaries for long bash commands

clean-tui can replace long bash command lines with a short plain-English summary (cat >> log << 'EOF' ... → Appends reboot log to migration file). The feature is off by default: it must not cost anything, share your session model's rate limits, or send data anywhere until you ask for it.

To enable it, point it at any model your Pi installation already serves:

/goodies summary-model kilo/xai/grok-4-fast   # or any provider/model you have

The command validates the model against your registry and suggests close matches on typos. Summaries ride your existing auth completely — API keys from the environment or models.json, OAuth token refresh included — there are no extra endpoints or keys to configure. /goodies list shows whether summaries are on or off, and /goodies summary-model off disables them again.

Failures are invisible in the TUI (pi owns the terminal), so each distinct failure is also appended to ~/.pi/agent/goodies.log (capped at 256 KB, oldest lines dropped), along with one clean-tui active; summary-model=… line per load. If summaries silently stop, look there first.

Two practical notes:

• Pick a fast non-thinking model. Summaries get a tiny response budget; models that insist on thinking first spend that budget invisibly and fail, which pauses summaries via backoff. A quick chat-class model works best.
• Privacy: qualifying commands (longer than 80 characters) are sent — first ~2000 characters — to whichever provider hosts the model you chose. That is the same trust decision as running an agent session against that provider, made explicit here because it happens outside normal turns.

Failures degrade gracefully: the raw command stays visible as a heuristic hint, each distinct failure is logged once (naming the model), and repeated failures back off exponentially instead of hammering the provider.

Render-safety rules (why summaries only refresh running rows)

These rules apply to pi's regular TUI mode (tuiMode: "regular", the default — TuiMainScreen, the scrolling scrollback renderer). Pi also has a fullscreen mode (TuiAltScreen): no scrollback, a fixed height-line slice of the transcript diffed row-by-row, full clears only on first render/resize/image redraws. Neither escalation below exists there — a summary arrival re-rendering an old row is either invisible (scrolled off the slice) or a one-line rewrite. Check ~/.pi/agent/settings.json tuiMode before reasoning about render escalation.

Pi's regular-mode diff renderer answers two situations with fullRender(true) — clear screen, wipe scrollback, repaint everything — which reads as a full-screen flash:

1. total rendered height dropping below the session high-water mark (clearOnShrink), and
2. any content change to a line above the scrolled viewport (firstChanged < prevViewportTop — width-independent; on a long transcript this is any row more than a screenful above the input box).

clean-tui therefore follows two rules in its render paths:

• Height-neutral swaps: text that may be replaced by a summary later is capped at the same width as summaries (BASH_BULLET_WIDTH), so an arriving summary never collapses a wrapped line (rule 1).
• Pending-only refresh: when a summary lands, only rows whose tool is still executing are re-rendered — those sit at the transcript tail, inside the viewport, so the swap is a cheap differential update. Finished rows (including replayed ones from before a /resume) keep the raw command text for the rest of the session; the summary stays cached, and future rows of the same command render it from the start (rule 2).

To catch a flash red-handed, run PI_DEBUG_REDRAW=1 pi, reproduce, then grep fullRender ~/.pi/agent/pi-debug.log — every line is one screen wipe with its reason (clearOnShrink, firstChanged < viewportTop, resize, …). Note the log is append-only across sessions; check timestamps.

Per-model thinking levels (retired in favor of Pi 0.84.3)

This package previously shipped a model-thinking module with a /levels command and an extension-owned sidecar at ~/.pi/agent/data/bermudis-pi-goodies/thinking-levels.json. It existed because Pi's /scoped-models screen rewrote enabledModels with bare model ids (wiping any :level suffix) and because every setThinkingLevel() call persisted as the global default.

Pi 0.84.3 fixed both: in-session model and thinking changes are now ephemeral by default (persist only via /settings or Ctrl+S, #5263), and Pi added a native per-model thinking-level override keyed by provider/modelId, stored in settings.json modelThinkingLevels and edited via /settings → "Default thinking level per model". That is exactly what model-thinking provided, so the module is retired.

If you had levels in the old sidecar (~/.pi/agent/data/bermudis-pi-goodies/thinking-levels.json), re-enter them via /settings → "Default thinking level per model".

Provider and balance details

Kilo registration is network-free: it starts with kilo-auto/free, restores an authenticated catalog from Pi's model store, and normally revalidates that catalog no more than every four hours. Balance and quota requests run in the background so they never delay session startup, model selection, or post-run input readiness. The footer also reads OpenRouter remaining credits for openrouter, z.ai GLM Coding Plan token quota for zai (Global) and zai-coding-cn (BigModel China), and OpenAI Codex's ChatGPT subscription quota when using openai-codex OAuth; it skips platform API-key auth because that has no ChatGPT subscription quota. OpenRouter uses GET /api/v1/credits; z.ai uses GET /api/monitor/usage/quota/limit; Codex uses GET /wham/usage. z.ai and Codex show both each quota's window length and its nextResetTime/reset_at countdown (when supplied), and CODEX_API_URL or CHATGPT_BASE_URL can override the Codex base URL.

All providers share one renderer: every balance is projected to a list of segments and formatted the same way. Credits render as $1.5k; each usage window renders as [label ]<window> <remaining>%[ ↻<countdown>], e.g. 7d 72% ↻4d4h (↻ = resets in). Multiple windows are joined with ·, and named extra limits like Codex Spark get a label: 7d 72% ↻4d4h · Spark 7d 74% ↻5d4h. The footer refreshes on session start, model switch, and after each completed run (agent_settled), so it tracks both consumption and external tier changes for whatever provider is active — providers without a balance adapter are skipped, so this costs nothing for unrelated sessions. Do not also load the standalone kilo.ts or provider-balance.ts entries once this bundle is installed. If you previously symlinked the standalone provider-balance.ts, remove that link — the feature now ships in this bundle.