@remcp/runtime 0.2.107 → 0.2.109

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 0.2.109 — 2026-09-25
+
+- Linux file reads and recursive permission changes retain descriptor-bound parent traversal for the full operation; proc-fd anchored captures remain readable without reopening the path lexically.
+- Linux directory walks, listings, and search sessions pin allowed roots and parent descriptors, including bulk reads and edits, so ancestor swaps cannot redirect traversal.
+- `record_screen` publishes from private staging and anchors Linux destination parents; XDG portal screenshots use no-follow copying, reject symlink source/destination paths, and no longer delete an untrusted portal-returned URI.
+- Production CDP sessions reject dead sockets, recursively guard child targets and evict failed guarded new-tab sessions. Runtime tool names and schemas are unchanged.
+
+## 0.2.108 — 2026-09-25
+
+- Standalone production runtimes keep browser control disabled unless explicitly enabled; the authenticated paired agent enables its owned local runtime. IP-literal production allowlisting and persistent CDP guards cover page and worker sessions, delayed navigation, redirects, and subresources.
+- Archive and document operations use descriptor-bound Linux traversal where available; macOS/Windows preserve bounded source snapshots, canonical confinement, link/special-file rejection, and atomic staging through portable filesystem APIs instead of losing document/archive tools.
+- Linux semantic scroll/drag targets refresh accessibility geometry, and empty AT-SPI snapshots retry once before using the conservative depth fallback. Runtime tool names and schemas are unchanged.
+
 ## 0.2.106 — 2026-09-22
 
 - Wayland EIS records the emulated device used for each button press and sends the matching release through that same device, preventing cross-region/device drags from losing `pointerup`.

package/README.md

@@ -143,6 +143,12 @@ in `~/.config/remcp/runtime.json`. `--describe` always reports the current state
   agent. Browser control accepts only loopback CDP endpoints. The explicit `network` diagnostic can
   open a bounded TCP connection to a host/port, and shell/browser actions can reach the network when
   the requested operation itself requires it.
+- **Remote browser safety.** A standalone production runtime keeps browser control disabled unless
+  `REMCP_BROWSER_REMOTE_ENABLED=1`; the authenticated ReMCP device agent explicitly enables it for the local
+  runtime it owns. Production navigation requires an explicit `REMCP_BROWSER_ALLOWED_HOSTS` allowlist of IP
+  literals. Hostname navigation is refused unless `REMCP_BROWSER_ALLOW_DNS_REBIND=1` is set behind an external
+  DNS/egress boundary. Local navigation requires a separate `REMCP_BROWSER_ALLOW_LOCAL_NAVIGATION=1` opt-in,
+  and CDP request guards reject private, file, and WebSocket destinations.
 - **Optional confinement.** `allowedRoots` is empty by default. When you set it, it is enforced
   against the resolved real path of the deepest existing ancestor rather than the lexical string, so
   `<allowed>/link -> /etc` cannot be used to read or write outside the allowed directories.
@@ -159,6 +165,10 @@ in `~/.config/remcp/runtime.json`. `--describe` always reports the current state
   transport limit), writes are capped (`maxWriteBytes`), buffered session output is capped by both
   line count and total characters - a stream with no newlines cannot grow without limit - and reads
   are paged or chunked.
+- **Filesystem structural safety.** Archive and document snapshot/publication operations use
+  descriptor-bound directory traversal on Linux. macOS and Windows preserve the same bounded snapshot,
+  link/special-file rejection, canonical root confinement and atomic staging semantics, while using their
+  portable path APIs where Node does not expose directory-fd-relative open/rename/unlink primitives.
 - **Crash-resistant sessions.** A bogus shell, a closed stdin, or a dead parent cannot take the
   runtime down; sessions run in their own process group so `force_terminate` stops a whole pipeline;
   the agent restarts the runtime if it ever exits, so a device recovers instead of going silently
@@ -195,8 +205,10 @@ Optional settings live in `~/.config/remcp/runtime.json` (override the directory
 Every value can also be set with an environment variable: `REMCP_RUNTIME_ALLOWED_ROOTS`,
 `REMCP_RUNTIME_BLOCKED_COMMANDS`, `REMCP_RUNTIME_DANGEROUS_COMMANDS`, `REMCP_RUNTIME_TELEMETRY`,
 `REMCP_RUNTIME_DISABLE_TELEMETRY`, `REMCP_RUNTIME_MAX_OUTPUT_BYTES`, `REMCP_RUNTIME_MAX_READ_LINES`,
-`REMCP_RUNTIME_MAX_BUFFERED_LINES`, `REMCP_RUNTIME_MAX_WRITE_BYTES`, `REMCP_RUNTIME_SHELL`,
-`REMCP_RUNTIME_NAME`.
+  `REMCP_RUNTIME_MAX_BUFFERED_LINES`, `REMCP_RUNTIME_MAX_WRITE_BYTES`, `REMCP_RUNTIME_SHELL`,
+  `REMCP_RUNTIME_NAME`, `REMCP_BROWSER_REMOTE_ENABLED`, `REMCP_BROWSER_ALLOWED_HOSTS`,
+  `REMCP_BROWSER_ALLOW_LOCAL_NAVIGATION`, `REMCP_BROWSER_ALLOW_DNS_REBIND`.
+
 
 `allowedRoots` is empty by default, which means the paired device can reach anything the operating
 system user running the agent can reach. Set it when you want the device to be scoped to specific

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remcp/runtime",
-  "version": "0.2.107",
+  "version": "0.2.109",
   "description": "First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.",
   "type": "module",
   "license": "MIT",
@@ -21,7 +21,7 @@
   "scripts": {
     "start": "node src/index.mjs",
     "check": "node scripts/check.mjs",
-    "test": "node --test test/*.test.mjs"
+    "test": "node --import ./test/setup.mjs --test test/*.test.mjs"
   },
   "dependencies": {
     "@jellybrick/dbus-next": "^0.11.3",

package/src/catalog.mjs

@@ -830,6 +830,14 @@ export const toolDefinitions = [
   },
 ];
 
+export function coreToolSupported(definition) {
+  return !['create_archive', 'extract_archive'].includes(definition.name) || process.platform === 'linux';
+}
+
+export function supportedCoreTools() {
+  return toolDefinitions.filter(coreToolSupported);
+}
+
 export function advertisedTools() {
   return toolDefinitions.map(({ name, title, description, inputSchema, annotations, outputSchema }) => ({
     name,

package/src/compact-catalog.mjs

@@ -1,4 +1,4 @@
-import { TEXT_OUTPUT_SCHEMA, toolDefinitions } from './catalog.mjs';
+import { TEXT_OUTPUT_SCHEMA, supportedCoreTools, toolDefinitions } from './catalog.mjs';
 import { advertisedExtendedTools, extendedToolDefinitions } from './extended/catalog.mjs';
 
 export const compactRuntimeGroups = Object.freeze({
@@ -127,7 +127,7 @@ function groupedDefinition(name, members) {
 export async function supportedRuntimeOperationNames() {
   const supportedExtended = new Set((await advertisedExtendedTools()).map(tool => tool.name));
   return new Set([
-    ...toolDefinitions.map(tool => tool.name),
+    ...supportedCoreTools().map(tool => tool.name),
     ...extendedToolDefinitions.filter(tool => supportedExtended.has(tool.name)).map(tool => tool.name),
   ]);
 }