registry: add pi.dev coding agent

[dector]

Adding https://pi.dev/ agent.

Currently I install it as:

$ mise u -g github:badlogic/pi-mono
$ pi --version
0.59.0

Tar from releases:

$ tar --list -f pi-linux-x64.tar.gz | grep pi/pi
pi/pi

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request expands the available coding agents by integrating the pi.dev agent into the system's registry. This addition provides users with a new minimal terminal coding harness, broadening the suite of development tools accessible.

Highlights

• New Agent Added: The pi.dev coding agent has been added to the registry, providing a new tool for terminal-based coding.

Changelog

• registry/pi.toml
  • Added a new configuration file for the pi.dev coding agent.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds the pi coding agent to the mise registry. The configuration specifies both a GitHub and an npm backend. However, the default GitHub backend is configured incorrectly, as it will install a binary named pi-mono while the test command expects pi. I've suggested a fix to rename the binary upon installation.

[gemini-code-assist]

The github:badlogic/pi-mono backend provides a binary named pi-mono (e.g., pi-mono-linux-amd64), but the test command expects pi. This will cause the test to fail when using the GitHub backend, which is the default. You should use the exe option to rename the binary to pi upon installation.

Suggested change

	backends = ["github:badlogic/pi-mono", "npm:@mariozechner/pi-coding-agent"]
	backends = [{ full = "github:badlogic/pi-mono", options = { exe = "pi" } }, "npm:@mariozechner/pi-coding-agent"]

[greptile-apps]

Greptile Summary

This PR adds a registry entry for pi, a minimal terminal coding agent CLI distributed as @mariozechner/pi-coding-agent on npm from the badlogic/pi-mono monorepo. The change is a single new file following the established registry TOML convention.

• The npm:@mariozechner/pi-coding-agent backend is correct — it is the official and only published distribution channel for this tool.
• The github:badlogic/pi-mono backend listed first is likely problematic: pi-mono is a TypeScript monorepo and its GitHub releases are npm version tags, not standalone binary artifacts. The mise github: backend resolves installable assets from GitHub Release attachments; since pi-mono doesn't ship such binaries, this backend will silently fail or produce an error for users. Comparable coding-agent entries (amp, claude, codex, code) either use npm: alone or aqua: + npm:, not github: + npm:.
• The description and test fields follow registry conventions correctly.

Confidence Score: 3/5

• Safe to merge with the github:badlogic/pi-mono backend concern resolved; the npm backend alone is functional.
• The core npm backend is valid and matches the canonical install method. The only meaningful issue is that the github: backend is almost certainly non-functional for this TypeScript npm package, which could confuse users or silently fall back. Once that is addressed (either by confirming binary assets exist, or by removing the github: entry), the PR is straightforward.
• registry/pi.toml — specifically the github:badlogic/pi-mono backend entry.

Important Files Changed

Filename	Overview
registry/pi.toml	Adds pi coding agent to the registry. The github:badlogic/pi-mono backend is likely non-functional as the project distributes via npm rather than GitHub Release binaries; the npm backend is correct. The format and description otherwise match the registry convention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[mise install pi] --> B{Try backends in order}
    B --> C[github backend - badlogic/pi-mono]
    C --> D{Binary release assets exist?}
    D -- Yes --> E[Install binary - success]
    D -- No --> F[Backend fails]
    F --> G[npm backend - mariozechner/pi-coding-agent]
    G --> H[npm global install - success]

Loading

_{Last reviewed commit: 5285a37}

[greptile-apps]

github: backend likely non-functional for this TypeScript npm package

badlogic/pi-mono is a TypeScript monorepo whose distribution method is npm install -g @mariozechner/pi-coding-agent. The github: backend in mise attempts to download pre-compiled binary release assets from GitHub Releases. Since pi-mono does not appear to publish standalone binary artifacts in its GitHub releases (only npm version tags like v0.59.0), the github:badlogic/pi-mono backend will fail at install time for users who rely on it.

The canonical install path for other npm-distributed coding agents in this registry (e.g. amp.toml, codex.toml) is either npm: alone or aqua: + npm: (when an aqua manifest exists). If pi-mono does ship platform binaries as GitHub release assets this is fine — but if not, the entry should be:

Suggested change

	backends = ["github:badlogic/pi-mono", "npm:@mariozechner/pi-coding-agent"]
	backends = ["npm:@mariozechner/pi-coding-agent"]

[dector]

--version runs but prompting is broken in the latest version. Checking 👀

[risu729]

Monorepo but 25.6k stars. https://github.com/badlogic/pi-mono