From d6c75a57aa6484ee1f5f171facdcdf8f406744f0 Mon Sep 17 00:00:00 2001 From: EthanHuo Date: Fri, 13 Nov 2026 00:35:38 +0800 Subject: [PATCH] docs(agents): update the user's local mcpx after every change A change is done when the user's installed mcpx runs it, not when it merges: agents run update-local-tool and report before -> after. --- AGENTS.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index d557d35..e7b3bcc 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -13,3 +13,19 @@ Use the canonical triage labels defined in `docs/agents/triage-labels.md`. ### Domain docs This is a single-context repository. Read `GLOSSARY.md` and relevant ADRs under `docs/adr/`. See `docs/agents/domain.md`. + +## Local install after every change + +On the user's machines `mcpx` is the release bundle in `~/.local/bin`, +installed by the workspace `update-local-tool` skill. A change is not done when +it merges or releases. It is done when the user's local `mcpx` runs it. The +user does not watch for this, so do it without being asked: + +1. After the release workflow for your change succeeds, check whether the tool is + installed: `command -v mcpx`. If it is not, stop here. +2. Run `bash ~/workspace/.agents/skills/update-local-tool/update.sh mcpx`. It prints `before -> after`. +3. Check your change with the installed binary, for example `mcpx @schema` or the + command you changed. +4. Put the `before -> after` line in your final report. + +If the release failed, report that. Don't install a local build in its place.