docs: add MnemoPay extension tutorial#8306
docs: add MnemoPay extension tutorial#8306t49qnsx7qt-kpanks wants to merge 2 commits intoblock:mainfrom
Conversation
t49qnsx7qt-kpanks
requested review from
DOsinga,
angiejones and
blackgirlbytes
as code owners
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1f2e9c6d04
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| <TabItem value="cli" label="Goose CLI" default> | ||
|
|
||
| ```sh | ||
| goose configure extensions --add mnemopay -- npx -y @mnemopay/sdk |
There was a problem hiding this comment.
goose configure extensions --add command
The one-line setup command uses goose configure extensions --add ..., but the CLI defines configure as a standalone command with no extensions subcommand (crates/goose-cli/src/cli.rs shows Configure {} at lines 701-705). Users following this tutorial will get a CLI parse error before they can install the extension, which blocks the primary setup path.
Useful? React with 👍 / 👎.
| MnemoPay includes a pre-configured recipe: | ||
|
|
||
| ```sh | ||
| goose session --recipe https://raw.githubusercontent.com/mnemopay/mnemopay-sdk/master/integrations/goose/recipe.yaml |
There was a problem hiding this comment.
session --recipe to run --recipe
This command uses goose session --recipe ..., but --recipe is only part of InputOptions on Command::Run (crates/goose-cli/src/cli.rs lines 181-217 and 808-813); Command::Session does not accept recipe input flags (lines 760-798). As written, the Recipe section’s command will fail for readers trying to run the provided recipe URL.
Useful? React with 👍 / 👎.
| @@ -0,0 +1,166 @@ | |||
| --- | |||
| title: MnemoPay Extension | |||
| description: Add MnemoPay MCP Server as a Goose Extension for persistent memory, micropayments, and fraud-aware trust scoring | |||
There was a problem hiding this comment.
goose in this tutorial
The new documentation repeatedly uses Goose with an uppercase G, which violates the documentation branding rule requiring lowercase goose for all docs content under documentation/ (documentation/AGENTS.md lines 5-10). Keeping this capitalization introduces a direct style-policy regression in the added tutorial.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5d0756007f
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| MnemoPay includes a pre-configured recipe: | ||
|
|
||
| ```sh | ||
| goose run --recipe https://raw.githubusercontent.com/mnemopay/mnemopay-sdk/master/integrations/goose/recipe.yaml |
There was a problem hiding this comment.
run --recipe example with supported input
This command documents goose run --recipe with a https://raw.githubusercontent.com/... URL, but the CLI only accepts a recipe name or filesystem path (InputOptions::recipe in crates/goose-cli/src/cli.rs) and resolves it via load_recipe_file (crates/goose-cli/src/recipes/search_recipe.rs), which calls local file loading first. A raw HTTP URL is treated as a path and fails to load, so users following this section will hit an error instead of running the recipe.
Useful? React with 👍 / 👎.
| lightning: | ||
| type: stdio | ||
| cmd: npx | ||
| args: ["-y", "@lightninglabs/lightning-mcp-server"] |
There was a problem hiding this comment.
enabled field to lightning extension config
The YAML block under pairing omits enabled for extension entries, but config parsing expects each extension to deserialize into ExtensionEntry { enabled: bool, ... } (crates/goose/src/config/extensions.rs), and malformed entries are skipped. If users copy this snippet into config.yaml, the lightning extension will not be loaded, so the documented pairing flow will not work.
Useful? React with 👍 / 👎.
Add tutorial for MnemoPay MCP Server — persistent memory, micropayments, and fraud-aware trust scoring for Goose agents. 13 MCP tools (memory, payments, observability) with a unique payment-memory feedback loop where successful settlements reinforce agent memories. npm: @mnemopay/sdk GitHub: https://github.com/mnemopay/mnemopay-sdk Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Jerry Omiagbo <jeremiah@getbizsuite.com>
- Replace `goose configure extensions --add` with `goose session --with-extension` - Replace `goose session --recipe` with `goose run --recipe` - Lowercase "Goose" to "goose" per documentation branding rules Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Jerry Omiagbo <jeremiah@getbizsuite.com>
t49qnsx7qt-kpanks
force-pushed
the
add-mnemopay-extension
branch
from
5d07560 to
8792ff7
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8792ff77a6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| mnemopay: | ||
| type: stdio | ||
| cmd: npx | ||
| args: ["-y", "@mnemopay/sdk"] |
There was a problem hiding this comment.
name fields in pairing config entries
In the pairing YAML, the stdio extension objects omit name, but ExtensionConfig::Stdio requires name during deserialization (crates/goose/src/agents/extension.rs), and malformed entries are skipped in get_extensions_map_with_config (crates/goose/src/config/extensions.rs). As written, users copying this block will not load these extensions from config.yaml, so the documented MnemoPay+Lightning pairing flow will fail.
Useful? React with 👍 / 👎.
| cmd: npx | ||
| args: ["-y", "@mnemopay/sdk"] | ||
| enabled: true | ||
| env: |
There was a problem hiding this comment.
envs key for extension environment variables
This config example uses env, but stdio extension config expects envs (ExtensionConfig::Stdio in crates/goose/src/agents/extension.rs). Because unknown fields are not consumed into the extension env map, MNEMOPAY_AGENT_ID from this snippet will not be applied, which breaks the tutorial’s stated behavior of setting a unique agent identity via config.
Useful? React with 👍 / 👎.
1 participant
Summary
Adds a tutorial for MnemoPay — the first MCP extension that combines persistent memory, micropayments, and fraud-aware trust scoring for Goose agents.
@mnemopay/sdkv0.5.0Setup
One line:
Tutorial includes
🤖 Generated with Claude Code