@thinremote/thinr-cli 1.3.4 → 1.3.5

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## [1.3.5] - 2026-09-24
+
+### Fixed
+
+- `thinr_ls` describes what "/" actually resolves to: the agent process's
+  working directory, which is normally the filesystem root. 1.3.4 said it was
+  a base directory "usually /var/log", which was a stale service definition on
+  one device rather than how installs behave.
+
 ## [1.3.4] - 2026-09-24
 
 ### Fixed

package/lib/mcp/tools-filesystem.js

@@ -27,16 +27,17 @@ async function toolLs(args) {
     const requested = args.path || '/';
     const entries = await api.listDir(requested, args.include_hidden || false);
 
-    // "/" is the agent's base directory, not the filesystem root, while every
-    // other absolute path is literal. Listing "/" on an agent based in
-    // /var/log and reading it as the root is an easy and wrong conclusion to
-    // draw, so say which directory these entries actually came from.
+    // "/" resolves through the agent process's working directory, normally
+    // the filesystem root, while every other absolute path is literal. An
+    // agent started elsewhere answers "/" with that directory instead, which
+    // reads as the device's root and is not, so name the directory these
+    // entries actually came from.
     let header = '';
     if (requested === '/') {
         try {
             const root = await api.info('/');
             if (root?.path && root.path !== '/') {
-                header = `listing ${root.path} (the agent's base directory, which "/" resolves to)\n`;
+                header = `listing ${root.path} (the agent's working directory, which "/" resolves to)\n`;
             }
         } catch {
             // Labelling is a convenience; a listing without it still stands.
@@ -163,14 +164,14 @@ export const tools = [
     },
     {
         name: 'thinr_ls',
-        description: `List directory contents on a remote device. Paths are absolute on the device filesystem (e.g., "/etc", "/var/log"), with one exception: "/" on its own resolves to the agent's base directory (\`fs_base_path\` in thinr_device_info), which for a system install is usually /var/log. The listing says which directory it came from when the two differ. Nothing is confined to that directory — "/etc" reads the real /etc — so do not read a "/" listing as the root filesystem. Subject to the OS user the agent runs as; check whoami (or thinr_device_info) before assuming write access to system paths. Use include_hidden to see dotfiles.`,
+        description: `List directory contents on a remote device. Paths are absolute on the device filesystem (e.g., "/etc", "/var/log"), with one exception: "/" on its own resolves to the agent process's working directory, normally the filesystem root, reported as \`fs_base_path\` by thinr_device_info. When it is not the root — an agent started from elsewhere — the listing says which directory it came from. Nothing is confined to it: "/etc" reads the real /etc. Subject to the OS user the agent runs as; check whoami (or thinr_device_info) before assuming write access to system paths. Use include_hidden to see dotfiles.`,
         inputSchema: {
             type: 'object',
             properties: {
                 path: {
                     type: 'string',
                     description:
-                        'Directory path. Absolute and literal, except "/", which means the agent\'s base directory (default: "/").',
+                        'Directory path. Absolute and literal, except "/", which means the agent\'s working directory, normally the filesystem root (default: "/").',
                 },
                 include_hidden: {
                     type: 'boolean',

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@thinremote/thinr-cli",
-    "version": "1.3.4",
+    "version": "1.3.5",
     "description": "CLI for ThinRemote — remote management for IoT devices, with an MCP server for AI clients",
     "main": "bin/thinr.js",
     "bin": {