@remcp/remcp 0.2.21 → 0.2.22

package/README.md

@@ -9,7 +9,7 @@ remcp --version
 remcp status
 ```
 
-Pairing commands are generated in the workspace at <https://remcp.delio24.com/app/connect>. The
+Pairing commands are generated in the workspace at <https://remcp.site/app/connect>. The
 generated command runs `remcp connect --server … --code … --install`, which stores a per-device
 credential under `~/.config/remcp/`, installs the runtime from npm, and registers a user service
 (systemd on Linux, LaunchAgent on macOS, Scheduled Task on Windows).
@@ -34,7 +34,7 @@ and the current usage-metrics state, so a support request can be answered with o
 ## What runs on your computer
 
 - the agent (`remcp start`), which holds the device credential and dials
-  `wss://remcp.delio24.com/agent`;
+  `wss://remcp.site/agent`;
 - [`@remcp/runtime`](https://www.npmjs.com/package/@remcp/runtime), spawned by the agent as an MCP
   stdio server. The runtime executes the tools, opens no network connection, and is supervised: if it
   exits, the agent restarts it with backoff and reports the restart instead of failing silently.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remcp/remcp",
-  "version": "0.2.21",
+  "version": "0.2.22",
   "description": "ReMCP device client: pair a computer with ReMCP and run the outbound-only agent that hosts the local MCP runtime.",
   "type": "module",
   "license": "MIT",

package/src/cli.mjs

@@ -22,7 +22,7 @@ const windowsTaskName = 'ReMCP Agent';
 // How npm is invoked is resolved from the running node when possible: a background service has a
 // minimal PATH, which is why auto-update used to find no npm on macOS. See src/npm.mjs.
 const npm = resolveNpm();
-const officialOrigin = 'https://remcp.delio24.com';
+const officialOrigin = 'https://remcp.site';
 
 function parse(argv) {
   const [command = 'help', ...rest] = argv;