∞skylakegrep

release notes · v0.7.2

skylakegrep 0.7.2 — Pi coding agent integration

0.7.2 is a small additive release. skygrep setup now detects and registers with Pi (pi-coding-agent), so a Pi session receives the same "prefer skygrep over raw rg" guidance the other supported CLIs already get.

What changed

  • Pi joins the setup catalogue. Pi loads ~/.pi/agent/AGENTS.md as its global instructions file — the same convention Codex and OpenCode follow. skygrep setup writes the managed guidance block there when ~/.pi or a pi binary is found. The catalogue order is now Claude Code, Codex, OpenCode, Gemini CLI, Pi, Cursor; Cursor stays last because it is the only project-scoped target.
  • CLI help, README, and the docs site list Pi with the other supported agents.

Compatibility

  • Existing indexes are untouched; no rebuild is required.
  • Machines without Pi see no change. Re-running skygrep setup on a machine with Pi adds one managed block to ~/.pi/agent/AGENTS.md and leaves the other agents' files as they are.
  • skygrep setup --uninstall removes the Pi block like any other.

Verification

  • tests/test_integrations.py gains three tests: catalogue order, Pi's config and detection paths, and a register → registered → unregister round-trip under a temporary HOME.
  • CI passed on Python 3.9, 3.10, 3.11, and 3.12 (pull request #13).
  • On a machine with Pi installed, skygrep setup --list shows Pi detected with the expected path before registration and [current] after.

Privacy

The change set was scanned for absolute user paths, usernames, email addresses, IP addresses, credentials, and temporary-directory paths before publication; none are present. The Pi block contains only the generic guidance snippet already shipped for the other agents. No network, telemetry, or model-routing behaviour changed.

Known follow-ups

  • Pi reads AGENTS.md at startup, so a running Pi session picks the guidance up on its next launch.