Who it is forA developer who wants a custom tool or provider available in every rpi session without forking the CLI.
The problemAdding a tool to a coding agent usually means changing its core code and maintaining a separate fork.
The outcomeA compiled plugin library that the global rpi loads alongside the built-in tools.
What you need first
- Rust 1.78 or later, for installing from crates.io
- An ANTHROPIC_API_KEY or OPENAI_API_KEY, or a ~/.rpi/agent/models.json file, for live model calls
- Git, to clone the repository for the offline examples
Steps
- Run
git clone https://github.com/bigfish1913/pi-rust.git - Open examples/plugin-stub and read how it uses rpi-plugin-sdk
- Run
cargo build -p plugin-stubfrom the repository root to build the cdylib (inferred, check the README) - Place the built library where the rpi plugin loader expects it, following docs/agent/project-structure.md
Prompt for your agent
In the bigfish1913/pi-rust repository, copy examples/plugin-stub into <new-plugin-folder>, implement one tool in it, and build it as a cdylib. Expected output: a compiled shared library that rpi can load. Verify that `rpi --version` still runs after the plugin is placed in the loader path.
Caveat. The README does not give the plugin install path or build command, so confirm them in examples/plugin-stub and docs/agent/project-structure.md before copying files.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for bigfish1913/pi-rust and "Build a plugin tool that loads into every rpi session"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer