Repository navigation
docs(payer): restart the server after env changes; keep AIFINPAY_HOME on init - #15
Merged
Merged
Conversation
… on init In the second fresh-agent test (MCP 2.11.0) the agent created the wallet, saved the owner's limits into the client config and called agent_reload; payment_setup_status kept answering payments_enabled: false, and the agent stopped at "reload did not pick up the env". The guide said "reconnect" without saying what that is. - Step 4 and "Buy access" step 4: owner limits are read only when the server starts; agent_reload re-reads the keystore and nothing else. The client has to restart the aifinpay MCP server, and until then payments_enabled: false is expected — the agent says so, asks the owner for the restart and stops. - Step 3: run the init command exactly as next_step gives it, keeping the AIFINPAY_HOME prefix when the server has its own wallet directory; a keystore that cannot be opened is never replaced — start a new directory. - Release target MCP 2.11.1; published baseline MCP 2.11.0 / Node 2.8.0. Version 2.10.1 across package, lock, plugin manifests and both skills.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@aifinpay/skill2.10.1 — the two gaps the second fresh-agent test (MCP 2.11.0, 2026-10-19) left in the payer guide.What happened
The agent reached step 4 on its own:
init, keystore, owner limits saved into the client config,agent_reload. Thenpayment_setup_statuskept answeringpayments_enabled: false, and the agent stopped at "reload did not pick up the env". The guide said "reconnect" and did not say what that is or thatagent_reloadis not it.Separately, MCP 2.11.1 (AiFinPay/sdk#119) carries
AIFINPAY_HOMEthroughnext_stepandinit, and refuses to replace a keystore it cannot open; the guide needs to tell the agent to keep that prefix and not improvise around an existing keystore.What changes
agent_reloadre-reads the keystore and nothing else. After the env changes the client has to restart theaifinpayMCP server (restart the client, or disable and re-enable the server). Until thenpayments_enabled: falseis expected, not a refusal: the agent says so, asks the owner for the restart, and stops.next_stepgives it, keeping theAIFINPAY_HOME=…prefix when the server has its own wallet directory. A keystore that exists and cannot be opened is never deleted or replaced; the agent follows init'snext_stepand starts a new wallet directory.package.json, lock, both.claude-pluginmanifests and both skill frontmatters.Nothing about limits, origins, signing or what the owner decides is loosened.
Verification
npm test(validate.mjs + validate.test.mjs): 13 pass, 0 fail.Release order
@aifinpay/skill2.10.1.mcp's@aifinpay/skillto^2.10.1(lock + cohort pins), then@aifinpay/mcp2.11.1 is published with the matching tool wording.Linked surfaces