@remcp/runtime 0.2.30 → 0.2.31

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,34 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.30
4
+
5
+ - **Unrestricted mode.** `REMCP_RUNTIME_UNRESTRICTED=1` (or `"unrestricted": true` in `runtime.json`,
6
+ or `remcp godmode on`) lifts the access roots, the configured command blocklist and the
7
+ catastrophic-command guardrail for this computer. It is not settable through MCP: `set_config_value`
8
+ still accepts only the four preferences it lists, so a model cannot widen its own reach.
9
+ `get_runtime_info` reports `policy.unrestricted` and says how to turn it off. Size limits
10
+ (`maxWriteBytes`, `maxOutputBytes`, line limits) are unchanged, and commands still run as the user
11
+ the agent runs as.
12
+
13
+ ## 0.2.29
14
+
15
+ - Screenshot failures on GNOME Wayland name the tool that works (`gnome-screenshot`); previously the
16
+ message suggested `grim`, which cannot read a GNOME session at all.
17
+
18
+ ## 0.2.26
19
+
20
+ - Screenshot failures explain the platform's own gate: Screen Recording on macOS, an interactive
21
+ session on Windows, `grim`/`gnome-screenshot` on Wayland, and "no graphical session" on a server.
22
+ - A PNG above the inline limit is saved on the computer and the result says how to fetch it in
23
+ chunks, instead of failing the call.
24
+
25
+ ## 0.2.25
26
+
27
+ - `EACCES`/`EPERM`/`EROFS`/`ENOSPC`/`EBUSY` from the file system are explained instead of printed
28
+ raw: macOS privacy folders (Full Disk Access for the exact `node` binary), Windows Controlled
29
+ folder access, Linux ownership, read-only mounts and full disks. Every filesystem failure in the
30
+ runtime goes through it.
31
+
3
32
  ## 0.2.20
4
33
 
5
34
  - `set_config_value`: a model may change this runtime’s own preferences (telemetry opt-out, read
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remcp/runtime",
3
- "version": "0.2.30",
3
+ "version": "0.2.31",
4
4
  "description": "First-party ReMCP local device runtime: file, search, terminal and process tools over MCP for computers paired with ReMCP.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -17,7 +17,7 @@ export async function getRuntimeInfoTool() {
17
17
  // Reported first because it changes how everything below should be read.
18
18
  unrestricted: runtimeConfig.unrestricted,
19
19
  ...(runtimeConfig.unrestricted
20
- ? { unrestrictedNote: 'Unrestricted mode is on for this computer: any path and any command is allowed, and commands run as the user the agent runs as. Turn it off with `remcp godmode off` (or REMCP_RUNTIME_UNRESTRICTED=0) and restart the agent.' }
20
+ ? { unrestrictedNote: 'Unrestricted mode is on for this computer: any path and any command is allowed, and commands still run as the user the agent runs as, so sudo needs your own sudoers rules. Turn it off with `remcp godmode off` (or REMCP_RUNTIME_UNRESTRICTED=0) and restart the agent.' }
21
21
  : {}),
22
22
  allowedRoots: [...runtimeConfig.allowedRoots],
23
23
  blockedCommands: [...runtimeConfig.blockedCommands],