patchxnote-agent 0.2.16 → 0.2.17

package/README.md

@@ -1,12 +1,14 @@
 # PatchX Freenote Agent npm wrapper
 
+> Version 0.2.17 supports account-wide mobile/desktop/web reads on GoServer Scheme B (0.20.85). Existing explicit mobile/desktop calls and valid authorization remain compatible. Discover the connected MCP tool schema before using optional platform parameters.
+
 [English README](https://github.com/ZsTs119/patchx-freenote-agent#readme) | [简体中文说明](https://github.com/ZsTs119/patchx-freenote-agent/blob/main/README.zh-CN.md) | [飞书公开使用指南](https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd)
 
 This npm package is the installer and thin launcher wrapper for PatchX Freenote Agent. It downloads or verifies the matching native `patchxnote` CLI binary from GitHub Releases, verifies `checksums.txt`, and installs it into a user-writable directory before delegating runtime commands to that binary.
 
 PatchX Freenote Agent is the local AI assistant connector for PatchX Freenote. It lets an MCP-capable AI assistant find PatchX Freenote records, inspect AI-generated results, create Markdown drafts, and manually send user-approved messages to Feishu, DingTalk, or another webhook.
 
-Version `0.2.16` defaults to the production API at `https://freenote.patch-x.cn`. When upgrading from test, update or remove explicit server-address overrides in your CLI and MCP host configuration, then run `mcp login` in the same runtime and profile that launches MCP. Test credentials and records do not migrate to production.
+Version `0.2.17` defaults to the production API at `https://freenote.patch-x.cn`. When upgrading from test, update or remove explicit server-address overrides in your CLI and MCP host configuration, then run `mcp login` in the same runtime and profile that launches MCP. Test credentials and records do not migrate to production.
 
 This release supports the WorkBuddy connector's CLI authorization flow. Temporary token-refresh failures preserve the login session and return a retryable error; rejected refresh credentials require authorization again. WorkBuddy's connector update and official client verification are tracked separately.
 
@@ -15,7 +17,7 @@ Production service: [https://freenote.patch-x.cn/](https://freenote.patch-x.cn/)
 Give this one-line prompt to an AI assistant:
 
 ```text
-Help me connect PatchX Freenote MCP and install the PatchX Freenote MCP Skill when the client supports Agent Skills. Use the production service at https://freenote.patch-x.cn/ and the setup page at https://freenote.patch-x.cn/mcp/setup/; if existing configuration explicitly points to the old test service, update the server address used for this connection to production first. First, if this is a local command-capable environment, run npx -y patchxnote-agent@latest skill install on this machine so future or long sessions remember the PatchX Freenote SOP; if the current client does not support Skill installation, do not treat that as a connection blocker and continue with MCP setup according to the client's capabilities. Identify the MCP client you are running in: if this is a local MCP client such as Codex, Cursor, VS Code, Claude Desktop, Claude Code, or Windsurf, run npx -y patchxnote-agent@latest setup --client <client-id> on this machine in the same OS/runtime that will later launch the MCP server. If this is an AI client or cloud platform that cannot run local commands but supports Remote MCP, custom connectors, custom MCP services, or tool plugins, create a custom MCP connector named PatchX Freenote MCP and connect it with this PatchX Freenote Remote MCP URL: https://freenote.patch-x.cn/mcp. If you are not sure which client ID or config format to use, local clients should first run npx -y patchxnote-agent@latest mcp config and use the printed generic stdio config, while remote clients should look for a Remote MCP Server URL, MCP Server URL, or Custom Connector setup entry. For login, open the browser and let me complete PatchX Freenote phone-code authorization there; do not ask me to paste OTP codes, OAuth codes, authorization codes, access tokens, refresh tokens, or webhook secrets into chat. After setup, call patchxnote_get_current_user and patchxnote_list_memories with {"platform":"mobile","limit":5} to verify it works. References: https://github.com/ZsTs119/patchx-freenote-agent and https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd
+Help me connect PatchX Freenote MCP and install the PatchX Freenote MCP Skill when the client supports Agent Skills. Use the production service at https://freenote.patch-x.cn/ and the setup page at https://freenote.patch-x.cn/mcp/setup/; if existing configuration explicitly points to the old test service, update the server address used for this connection to production first. First, if this is a local command-capable environment, run npx -y patchxnote-agent@latest skill install on this machine so future or long sessions remember the PatchX Freenote SOP; if the current client does not support Skill installation, do not treat that as a connection blocker and continue with MCP setup according to the client's capabilities. Identify the MCP client you are running in: if this is a local MCP client such as Codex, Cursor, VS Code, Claude Desktop, Claude Code, or Windsurf, run npx -y patchxnote-agent@latest setup --client <client-id> on this machine in the same OS/runtime that will later launch the MCP server. If this is an AI client or cloud platform that cannot run local commands but supports Remote MCP, custom connectors, custom MCP services, or tool plugins, create a custom MCP connector named PatchX Freenote MCP and connect it with this PatchX Freenote Remote MCP URL: https://freenote.patch-x.cn/mcp. If you are not sure which client ID or config format to use, local clients should first run npx -y patchxnote-agent@latest mcp config and use the printed generic stdio config, while remote clients should look for a Remote MCP Server URL, MCP Server URL, or Custom Connector setup entry. For login, open the browser and let me complete PatchX Freenote phone-code authorization there; do not ask me to paste OTP codes, OAuth codes, authorization codes, access tokens, refresh tokens, or webhook secrets into chat. After setup, call patchxnote_get_current_user and patchxnote_list_memories with {"limit":5} when the discovered schema makes platform optional; otherwise retain {"platform":"mobile","limit":5} for the older installed schema. Verify the returned records and sources. References: https://github.com/ZsTs119/patchx-freenote-agent and https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd
 ```
 
 The npm package includes an Agent Skills package at `skills/patchxnote-mcp/`. Compatible agents can install or refresh it with:
@@ -100,6 +102,8 @@ npx -y patchxnote-agent@latest install --print-config
 Common CLI examples:
 
 ```sh
+patchxnote model-io list
+patchxnote model-io list --platform web
 patchxnote model-io list --platform mobile
 patchxnote model-io packaged-result --request-id <request_id> --platform mobile --out ./packaged-result.json
 patchxnote model-io provider-response --request-id <request_id> --platform mobile --out ./provider-response.json

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchxnote-agent",
-  "version": "0.2.16",
+  "version": "0.2.17",
   "mcpName": "io.github.ZsTs119/patchxnote-agent",
   "description": "Installer wrapper for the PatchX Freenote Agent CLI, local MCP server, and PatchX Freenote MCP Skill.",
   "repository": {

package/skills/patchxnote-mcp/SKILL.md

@@ -69,7 +69,9 @@ npx -y patchxnote-agent@latest mcp status --verify
 Then call the MCP tools `patchxnote_get_current_user` and `patchxnote_list_memories` with:
 
 ```json
-{"platform":"mobile","limit":5}
+{"limit":5}
 ```
 
+Inspect `tools/list` first: Scheme B tools make platform optional and support mobile/desktop/web. Use the default above for all account sources, or `{"platform":"web","limit":5}` to filter Web. If an older installed tool still requires platform, use its explicit mobile/desktop schema until upgrading. Existing valid authorization remains usable.
+
 Report only the evidence actually obtained: configured, authenticated, tools listed, real tool called, published, indexed, or platform accepted.

package/skills/patchxnote-mcp/references/onboarding.md

@@ -7,13 +7,13 @@ Use this reference when installing, repairing, or verifying PatchX Freenote MCP
 Chinese:
 
 ```text
-请帮我接入 PatchX Freenote MCP，并在客户端支持 Agent Skills 时安装 PatchX Freenote MCP Skill。请使用生产服务地址 https://freenote.patch-x.cn/，接入页面为 https://freenote.patch-x.cn/mcp/setup/；如现有配置显式指定了旧测试地址，请先将本次接入使用的服务地址调整为上述生产地址。首先，如果当前是支持本地命令执行的环境，请在本机执行 npx -y patchxnote-agent@latest skill install，让后续新会话或长上下文能记住 PatchX Freenote SOP；如果当前客户端不支持 Skill 安装，不要判定为不能接入，请继续按客户端能力完成 MCP 接入。请识别你所在的 MCP 客户端：如果是 Codex、Cursor、VS Code、Claude Desktop、Claude Code、Windsurf 等本地 MCP 客户端，请在当前本机、并且在后续会启动 MCP 服务的同一个运行时执行 npx -y patchxnote-agent@latest setup --client <client-id>；如果是不支持本机命令但支持 Remote MCP、自定义连接器、自定义 MCP 服务或工具插件的 AI 客户端/云平台，请创建名为 PatchX Freenote MCP 的自定义 MCP 连接器，并使用这个 PatchX Freenote Remote MCP URL 完成接入：https://freenote.patch-x.cn/mcp。如果不确定客户端 ID 或配置格式，本地客户端先执行 npx -y patchxnote-agent@latest mcp config 并使用打印出的通用 stdio 配置，远程客户端则优先寻找 Remote MCP Server URL / MCP Server URL / Custom Connector 配置入口。登录时请打开浏览器让我完成 PatchX Freenote 手机号验证码授权，不要让我把验证码、OAuth code、授权码、access token、refresh token 或 webhook secret 粘贴到聊天里。完成后请调用 patchxnote_get_current_user 和 patchxnote_list_memories，参数 {"platform":"mobile","limit":5} 验证可用。参考资料：https://github.com/ZsTs119/patchx-freenote-agent 和 https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd。
+请帮我接入 PatchX Freenote MCP，并在客户端支持 Agent Skills 时安装 PatchX Freenote MCP Skill。请使用生产服务地址 https://freenote.patch-x.cn/，接入页面为 https://freenote.patch-x.cn/mcp/setup/；如现有配置显式指定了旧测试地址，请先将本次接入使用的服务地址调整为上述生产地址。首先，如果当前是支持本地命令执行的环境，请在本机执行 npx -y patchxnote-agent@latest skill install，让后续新会话或长上下文能记住 PatchX Freenote SOP；如果当前客户端不支持 Skill 安装，不要判定为不能接入，请继续按客户端能力完成 MCP 接入。请识别你所在的 MCP 客户端：如果是 Codex、Cursor、VS Code、Claude Desktop、Claude Code、Windsurf 等本地 MCP 客户端，请在当前本机、并且在后续会启动 MCP 服务的同一个运行时执行 npx -y patchxnote-agent@latest setup --client <client-id>；如果是不支持本机命令但支持 Remote MCP、自定义连接器、自定义 MCP 服务或工具插件的 AI 客户端/云平台，请创建名为 PatchX Freenote MCP 的自定义 MCP 连接器，并使用这个 PatchX Freenote Remote MCP URL 完成接入：https://freenote.patch-x.cn/mcp。如果不确定客户端 ID 或配置格式，本地客户端先执行 npx -y patchxnote-agent@latest mcp config 并使用打印出的通用 stdio 配置，远程客户端则优先寻找 Remote MCP Server URL / MCP Server URL / Custom Connector 配置入口。登录时请打开浏览器让我完成 PatchX Freenote 手机号验证码授权，不要让我把验证码、OAuth code、授权码、access token、refresh token 或 webhook secret 粘贴到聊天里。完成后请调用 patchxnote_get_current_user 和 patchxnote_list_memories，如果发现的工具Schema允许省略platform，使用参数 {"limit":5} 默认读取本人全部来源；旧版Schema仍要求平台时使用 {"platform":"mobile","limit":5}，核对返回记录及来源。参考资料：https://github.com/ZsTs119/patchx-freenote-agent 和 https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd。
 ```
 
 English:
 
 ```text
-Help me connect PatchX Freenote MCP and install the PatchX Freenote MCP Skill when the client supports Agent Skills. Use the production service at https://freenote.patch-x.cn/ and the setup page at https://freenote.patch-x.cn/mcp/setup/; if existing configuration explicitly points to the old test service, update the server address used for this connection to production first. First, if this is a local command-capable environment, run npx -y patchxnote-agent@latest skill install on this machine so future or long sessions remember the PatchX Freenote SOP; if the current client does not support Skill installation, do not treat that as a connection blocker and continue with MCP setup according to the client's capabilities. Identify the MCP client you are running in: if this is a local MCP client such as Codex, Cursor, VS Code, Claude Desktop, Claude Code, or Windsurf, run npx -y patchxnote-agent@latest setup --client <client-id> on this machine in the same OS/runtime that will later launch the MCP server. If this is an AI client or cloud platform that cannot run local commands but supports Remote MCP, custom connectors, custom MCP services, or tool plugins, create a custom MCP connector named PatchX Freenote MCP and connect it with this PatchX Freenote Remote MCP URL: https://freenote.patch-x.cn/mcp. If you are not sure which client ID or config format to use, local clients should first run npx -y patchxnote-agent@latest mcp config and use the printed generic stdio config, while remote clients should look for a Remote MCP Server URL, MCP Server URL, or Custom Connector setup entry. For login, open the browser and let me complete PatchX Freenote phone-code authorization there; do not ask me to paste OTP codes, OAuth codes, authorization codes, access tokens, refresh tokens, or webhook secrets into chat. After setup, call patchxnote_get_current_user and patchxnote_list_memories with {"platform":"mobile","limit":5} to verify it works. References: https://github.com/ZsTs119/patchx-freenote-agent and https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd
+Help me connect PatchX Freenote MCP and install the PatchX Freenote MCP Skill when the client supports Agent Skills. Use the production service at https://freenote.patch-x.cn/ and the setup page at https://freenote.patch-x.cn/mcp/setup/; if existing configuration explicitly points to the old test service, update the server address used for this connection to production first. First, if this is a local command-capable environment, run npx -y patchxnote-agent@latest skill install on this machine so future or long sessions remember the PatchX Freenote SOP; if the current client does not support Skill installation, do not treat that as a connection blocker and continue with MCP setup according to the client's capabilities. Identify the MCP client you are running in: if this is a local MCP client such as Codex, Cursor, VS Code, Claude Desktop, Claude Code, or Windsurf, run npx -y patchxnote-agent@latest setup --client <client-id> on this machine in the same OS/runtime that will later launch the MCP server. If this is an AI client or cloud platform that cannot run local commands but supports Remote MCP, custom connectors, custom MCP services, or tool plugins, create a custom MCP connector named PatchX Freenote MCP and connect it with this PatchX Freenote Remote MCP URL: https://freenote.patch-x.cn/mcp. If you are not sure which client ID or config format to use, local clients should first run npx -y patchxnote-agent@latest mcp config and use the printed generic stdio config, while remote clients should look for a Remote MCP Server URL, MCP Server URL, or Custom Connector setup entry. For login, open the browser and let me complete PatchX Freenote phone-code authorization there; do not ask me to paste OTP codes, OAuth codes, authorization codes, access tokens, refresh tokens, or webhook secrets into chat. After setup, call patchxnote_get_current_user and patchxnote_list_memories with {"limit":5} when the discovered schema makes platform optional; otherwise retain {"platform":"mobile","limit":5} for the older installed schema. Verify the returned records and sources. References: https://github.com/ZsTs119/patchx-freenote-agent and https://patchx2025.feishu.cn/wiki/PnVRwYT7IirFPckairGcWPnHnCd
 ```
 
 ## Client Detection
@@ -91,7 +91,7 @@ Then verify real MCP capability:
 1. `initialize`
 2. `tools/list`
 3. `tools/call patchxnote_get_current_user`
-4. `tools/call patchxnote_list_memories` with `{"platform":"mobile","limit":5}`
+4. Discover the content schema, then call `patchxnote_list_memories` with `{"limit":5}` for Scheme B or explicit `{"platform":"mobile","limit":5}` if the installed older schema requires it. Web filter: `{"platform":"web","limit":5}` when advertised.
 
 If the client asks for a current tool count, answer from `tools/list`, not from this skill file or memory.
 

package/skills/patchxnote-mcp/references/troubleshooting.md

@@ -87,12 +87,12 @@ Run both commands in the same runtime that launches MCP. Do not remove mobile/de
 
 Check:
 
-- Did the user select `mobile` or `desktop`?
+- Is a source filter applied? Scheme B defaults to all sources and accepts mobile/desktop/web. Older installed tool schemas may still require explicit mobile/desktop.
 - Is the account authenticated in this runtime?
 - Is `patchxnote_search_memories` searching only current-session cache?
 - Does `patchxnote_list_memories` need pagination?
 
-Do not infer that no PatchX Freenote data exists across every platform unless both platforms were queried and accepted by the user.
+Do not infer that the whole account has no data from one source or one cached page. Check the default account query and its pagination; local cache search only covers loaded metadata.
 
 ## Tool Count Drift
 

package/skills/patchxnote-mcp/references/workflows.md

@@ -4,13 +4,13 @@ Use this reference when the user wants to use PatchX Freenote data after MCP set
 
 ## Common Read Workflows
 
-Recent mobile memories:
+Recent memories across the current account (Scheme B):
 
 ```json
-{"platform":"mobile","limit":5}
+{"limit":5}
 ```
 
-Use `patchxnote_list_memories` for list entry points. Every content request must include `platform` as `mobile` or `desktop`. Do not merge platforms unless a future server contract explicitly adds that behavior.
+Use `patchxnote_list_memories` for list entry points. With Scheme B, omit `platform` for all account sources, or filter by `mobile`, `desktop`, or `web` (for example `{"platform":"web","limit":5}`). Retain each item platform and pass server cursors unchanged. Discover the connected tool schema first; older installed tools may still require mobile/desktop until upgraded.
 
 Current user:
 
@@ -20,12 +20,12 @@ Current user:
 
 Record detail:
 
-- Use `patchxnote_get_memory` with the returned `id` and explicit `platform`.
+- Use `patchxnote_get_memory` with the returned `id` and its `platform`. Platform may be omitted for a unique account record; if the server reports an ambiguous ID, specify its source.
 - Treat metadata titles and snippets as record labels, not guaranteed original filenames.
 
 Search:
 
-- Use `patchxnote_search_memories` only for data already cached in the current authorized MCP session.
+- In the local-tool branch, `patchxnote_search_memories` searches only metadata already loaded in the current account session. Omit platform to search all loaded sources, or filter Web/App/PC. The OAuth proxy uses the server tool description and does not share this local cache.
 - If search results are missing, list first, then search again if appropriate.
 
 ## Counting Summary Records
@@ -35,7 +35,7 @@ For "which files did I summarize" or "how many summaries":
 1. Inspect live tool availability if the available tools are uncertain.
 2. Page `patchxnote_list_memories` with `limit` up to 50 and the returned cursor.
 3. Keep `event_summary` separate from `daily_digest`.
-4. If counting source objects rather than rows, deduplicate `event_summary` records by `client_object_id`.
+4. If counting source objects rather than rows, deduplicate `event_summary` records within the current account by (`platform`, `client_object_id`), preserving different origins.
 5. State whether the count is complete, page-limited, filtered by platform, or based on currently returned records only.
 
 Do not claim metadata titles are original local filenames.