# AI use cases for Pi Bolt (opensec-git/Pi-Bolt) Repo: [opensec-git/Pi-Bolt](https://github.com/opensec-git/Pi-Bolt) | Use cases: 4 | Page: https://dedupedai.com/use-cases/opensec-git-pi-bolt/ Pi-Bolt is a compiled-ahead-of-time build of the Pi coding agent that starts faster and uses less CPU than Pi on Bun or Node. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Start the Pi coding agent faster on your machine: https://dedupedai.com/use-cases/opensec-git-pi-bolt/start-pi-coding-agent-faster/ - Compile your daily Pi extensions into Pi Bolt: https://dedupedai.com/use-cases/opensec-git-pi-bolt/compile-your-pi-extensions-into-pi-bolt/ - Run Pi Bolt in your editor's agent panel: https://dedupedai.com/use-cases/opensec-git-pi-bolt/run-pi-bolt-inside-your-code-editor/ - Let Claude Code hand coding tasks to Pi Bolt: https://dedupedai.com/use-cases/opensec-git-pi-bolt/let-claude-code-delegate-tasks-to-pi-bolt/ ## How to start the Pi coding agent faster on your machine with Pi Bolt Repo: [opensec-git/Pi-Bolt](https://github.com/opensec-git/Pi-Bolt) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Install a compiled Pi build that is ready to type sooner and uses less CPU. **Who it is for:** A developer who already uses Pi and wants a quicker start and lower CPU use during long coding sessions. **The problem:** Pi on Bun or Node takes a noticeable time to become ready and uses more CPU over a session. **The outcome:** Pi Bolt runs with the same commands, sessions, settings, providers and extensions as Pi, starting from a compiled executable. ### Steps 1. Run `curl -fsSL https://pi-bolt.opensec.in/install.sh | sh` on Linux, macOS or Termux, or run `irm https://pi-bolt.opensec.in/install.ps1 | iex` in PowerShell on Windows. 2. Open a terminal in your project folder and run `pi-bolt`. 3. If you are new to Pi, run `/login` inside Pi Bolt to connect a provider. 4. Run `pi-bolt --version` to confirm the install. ### Prompt to paste into your agent ```text In the repo opensec-git/Pi-Bolt, install Pi-Bolt on this machine using the installer for this operating system, then run with pi-bolt. Report the output of pi-bolt --version. Verify that your Pi configuration in ~/.pi/agent is used as is. ``` ### Caveat Pi Bolt is an independent fork of Pi and is not affiliated with Pi's authors or with Oven. Risk, remote script: The install command pipes a script from pi-bolt.opensec.in straight into sh or PowerShell, so read it first if you want to check it before running. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/opensec-git-pi-bolt/start-pi-coding-agent-faster/ ## How to compile your daily Pi extensions into Pi Bolt with Pi Bolt Repo: [opensec-git/Pi-Bolt](https://github.com/opensec-git/Pi-Bolt) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Turn installed extensions into machine code so they run without interpretation. **Who it is for:** A Pi Bolt user who relies on heavy extensions and wants them to run as compiled code. **The problem:** On the default build, extensions loaded at run time are interpreted, which can slow down heavy work such as search or parsing. **The outcome:** The extensions installed on this machine are compiled into Pi Bolt and run as machine code, and new releases recompile them on update. ### Steps 1. Install Pi Bolt with the installer and confirm it runs with `pi-bolt`. 2. Install the extensions you use every day with `pi-bolt install `. (inferred, check the README) 3. Run `pi-bolt compile` to compile the installed extensions into Pi Bolt (Linux and macOS). 4. Run `pi-bolt update` later, which compiles the extensions into each new release. ### Prompt to paste into your agent ```text In the repo opensec-git/Pi-Bolt, run pi-bolt compile on this Linux or macOS machine and report which extensions were compiled. Verify by running pi-bolt doctor and checking that the compiled extensions are listed. ``` ### Caveat pi-bolt compile is listed for Linux and macOS only, and the default build's JIT-free mode means extensions that need bun:ffi require the separate JIT build. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/opensec-git-pi-bolt/compile-your-pi-extensions-into-pi-bolt/ ## How to run Pi Bolt in your editor's agent panel with Pi Bolt Repo: [opensec-git/Pi-Bolt](https://github.com/opensec-git/Pi-Bolt) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use Pi Bolt through the Agent Client Protocol in Zed, JetBrains, VS Code or Neovim. **Who it is for:** A developer who works in an ACP-compatible editor and wants Pi's settings, extensions, skills and sessions in the agent panel. **The problem:** Switching between an editor and a separate terminal agent breaks the flow of editing code with an AI agent. **The outcome:** The editor's agent panel runs Pi Bolt with your existing Pi settings, extensions, skills and sessions. ### Steps 1. Install Pi Bolt and find the full path to the executable, for example with `which pi-bolt` on Linux or macOS. (inferred, check the README) 2. Open Zed's settings.json and add an agent_servers entry with the command set to that path and args set to ["--acp"]. 3. Open the agent panel in Zed and choose Pi Bolt. 4. For other editors, follow the setup in docs/ACP.md. ### Prompt to paste into your agent ```text In the repo opensec-git/Pi-Bolt, add a Pi-Bolt agent_servers entry for Zed that runs the full path of pi-bolt with the argument --acp. Report the settings.json change. Verify that the Pi-Bolt agent appears in the Zed agent panel and can answer a short prompt. ``` ### Caveat The README gives the Zed configuration in full, and other editors are covered only by a link to docs/ACP.md. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/opensec-git-pi-bolt/run-pi-bolt-inside-your-code-editor/ ## How to let Claude Code hand coding tasks to Pi Bolt with Pi Bolt Repo: [opensec-git/Pi-Bolt](https://github.com/opensec-git/Pi-Bolt) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Register Pi Bolt as an MCP server so Claude Code can send it prompts. **Who it is for:** A Claude Code user who wants a second coding agent to take on tasks and keep a session going across calls. **The problem:** A single agent session cannot easily offload a separate task to another agent and then pick up that conversation later. **The outcome:** Claude Code gives Pi Bolt a task through its prompt tool and continues the same session in later calls. ### Steps 1. Install Pi Bolt and find the full path to the executable. 2. Run `claude mcp add pi-bolt -- /full/path/to/pi-bolt --mcp` in a terminal. 3. Start Claude Code and ask it to use the pi-bolt prompt tool for a task in your project. 4. Ask a follow-up in a later call to confirm the session continues. ### Prompt to paste into your agent ```text In the repo opensec-material opensec-git/Pi-Bolt, register pi-bolt as a Claude Code MCP server with the full executable path and the --mcp argument. Send a short task through the prompt tool and report the reply. Verify that a second prompt call continues the same session. ``` ### Caveat The README gives only the Claude Code setup command, and other MCP clients are covered by a link to docs/MCP.md. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/opensec-git-pi-bolt/let-claude-code-delegate-tasks-to-pi-bolt/