Add Pi coding agent to dev VMs #4

New issue

Closed

opened 2026-07-15 05:09:37 +01:00 by allod-agent · 0 comments

allod-agent commented

2026-07-15 05:09:37 +01:00

Member

Roll the packaged Pi coding agent (pkgs.pi-coding-agent from nixpkgs-unstable, meta.mainProgram pi) into the dev-VM profile so an operator can run pi or yolo pi from ~/work with provider API keys supplied at invocation time.

In scope: add a public adapters/pi/AGENTS.md to allod/memory and the matching private adapter to agent-memory; generate ~/.pi/agent/AGENTS.md from memoryCheckouts in profiles/modules/ai-agents.nix (one pointer line per checkout, in the same order as the Claude and Codex pointers, written atomically); add a pi shell alias that starts in ~/work; add pi to the yolo wrapper using only Pi's project-local resource trust override; install pkgs-unstable.pi-coding-agent in hosts/dev/allod-dev/home.nix; and add flake checks over the generated Home Manager activation text and package list.

Out of scope: storing API keys, OAuth data, Pi auth.json/settings.json, model or provider defaults, or any provider-specific configuration in any repo; age secrets or password-manager integration; pinning a Pi model or provider; host rebuild execution.

Dev plan: allod/strategy/dev-plans/add-pi-adapter.md.

PR chain: the allod/memory and agent-memory adapter PRs carry Refs; the allod/profiles integration PR carries the closing keyword.

Roll the packaged Pi coding agent (`pkgs.pi-coding-agent` from `nixpkgs-unstable`, `meta.mainProgram` `pi`) into the dev-VM profile so an operator can run `pi` or `yolo pi` from `~/work` with provider API keys supplied at invocation time. In scope: add a public `adapters/pi/AGENTS.md` to `allod/memory` and the matching private adapter to `agent-memory`; generate `~/.pi/agent/AGENTS.md` from `memoryCheckouts` in `profiles/modules/ai-agents.nix` (one pointer line per checkout, in the same order as the Claude and Codex pointers, written atomically); add a `pi` shell alias that starts in `~/work`; add `pi` to the `yolo` wrapper using only Pi's project-local resource trust override; install `pkgs-unstable.pi-coding-agent` in `hosts/dev/allod-dev/home.nix`; and add flake checks over the generated Home Manager activation text and package list. Out of scope: storing API keys, OAuth data, Pi `auth.json`/`settings.json`, model or provider defaults, or any provider-specific configuration in any repo; age secrets or password-manager integration; pinning a Pi model or provider; host rebuild execution. Dev plan: `allod/strategy/dev-plans/add-pi-adapter.md`. PR chain: the `allod/memory` and `agent-memory` adapter PRs carry `Refs`; the `allod/profiles` integration PR carries the closing keyword.