joakimp/mempalace-toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(pi): add opencode-toolkit pointer in deploy recipe step 6

Browse Source 
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).
This commit is contained in:
Joakim Persson
2026-05-05 17:14:32 +02:00
parent 118bd20fec
commit 3d3a0fb125
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
extensions/pi/README.md
+4 -2
View File
@@ -116,8 +116,10 @@ If vars are empty, check that `~/.config/pi/.env` decrypted
### 6. Register mempalace MCP with opencode (if using opencode too) ### 6. Register mempalace MCP with opencode (if using opencode too)
Skip if this box is pi-only. Otherwise see Skip if this box is pi-only. Otherwise:
[root README § Registering mempalace with opencode](../../README.md#registering-mempalace-with-opencode-or-other-mcp-clients).
- 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 ### 7. First run