From 3d3a0fb125701ec3d03e73034d0070bae4402702 Mon Sep 17 00:00:00 2001 From: Joakim Persson Date: Tue, 5 May 2026 17:14:32 +0200 Subject: [PATCH] docs(pi): add opencode-toolkit pointer in deploy recipe step 6 Cross-reference the newly-extracted opencode-toolkit repo, which owns ~/.config/opencode/.env loading. The recipe now distinguishes between registering mempalace in opencode.json (still this repo's concern) and ensuring opencode's own env loader is in place (opencode-toolkit's). --- extensions/pi/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/extensions/pi/README.md b/extensions/pi/README.md index 49fad52..7aff90d 100644 --- a/extensions/pi/README.md +++ b/extensions/pi/README.md @@ -116,8 +116,10 @@ If vars are empty, check that `~/.config/pi/.env` decrypted ### 6. Register mempalace MCP with opencode (if using opencode too) -Skip if this box is pi-only. Otherwise see -[root README § Registering mempalace with opencode](../../README.md#registering-mempalace-with-opencode-or-other-mcp-clients). +Skip if this box is pi-only. Otherwise: + +- Install [`opencode-toolkit`](https://gitea.jordbo.se/joakimp/opencode-toolkit) so `~/.config/opencode/.env` is sourced into every shell (GitHub / Gitea / other MCP server tokens). +- Register the mempalace MCP server in `~/.config/opencode/opencode.json` — see [root README § Registering mempalace with opencode](../../README.md#registering-mempalace-with-opencode-or-other-mcp-clients). ### 7. First run