@firenet-designs/fnd-cli 2.3.2 → 2.3.3

package/README.md

@@ -20,7 +20,7 @@ $ npm install -g @firenet-designs/fnd-cli
 $ fnd COMMAND
 running command...
 $ fnd (--version)
-@firenet-designs/fnd-cli/2.3.2 linux-x64 node-v24.18.0
+@firenet-designs/fnd-cli/2.3.3 linux-x64 node-v24.18.0
 $ fnd --help [COMMAND]
 USAGE
   $ fnd COMMAND
@@ -62,7 +62,7 @@ EXAMPLES
   $ fnd backfill-project my-store "extra hints"
 ```
 
-_See code: [src/commands/backfill-project.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.2/src/commands/backfill-project.ts)_
+_See code: [src/commands/backfill-project.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.3/src/commands/backfill-project.ts)_
 
 ## `fnd create-app`
 
@@ -83,7 +83,7 @@ EXAMPLES
   $ fnd create-app
 ```
 
-_See code: [src/commands/create-app.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.2/src/commands/create-app.ts)_
+_See code: [src/commands/create-app.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.3/src/commands/create-app.ts)_
 
 ## `fnd create-project [SHOP]`
 
@@ -113,7 +113,7 @@ EXAMPLES
   $ fnd create-project my-store "Acme storefront, Klaviyo"
 ```
 
-_See code: [src/commands/create-project.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.2/src/commands/create-project.ts)_
+_See code: [src/commands/create-project.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.3/src/commands/create-project.ts)_
 
 ## `fnd help [COMMAND]`
 
@@ -165,7 +165,7 @@ EXAMPLES
   $ fnd token -s mystore -i <id> -c <secret> --write ./.mcp.json
 ```
 
-_See code: [src/commands/token.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.2/src/commands/token.ts)_
+_See code: [src/commands/token.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.3/src/commands/token.ts)_
 
 ## `fnd workspace`
 
@@ -173,9 +173,11 @@ Open a remote workspace: two-way sync the current directory to a remote Linux bo
 
 ```
 USAGE
-  $ fnd workspace --ssh <value> [--devtools <value>] [--remote-base <value>] [--source remote|local]
+  $ fnd workspace --ssh <value> [--delete-remote-dir] [--devtools <value>] [--remote-base <value>] [--source
+    remote|local]
 
 FLAGS
+  --delete-remote-dir    on exit, delete the remote workspace directory instead of leaving the synced copy in place
   --devtools=<value>     expose your LOCAL browser to Claude on the remote via the chrome-devtools MCP. Value is "port"
                          (same port both ends) or "remote:local" (local = this machine, where the browser runs). Your
                          browser must already be listening with --remote-debugging-port=<local>.
@@ -206,9 +208,11 @@ EXAMPLES
   $ fnd workspace --ssh user@host --devtools 9222
 
   $ fnd workspace --ssh user@host --devtools 9333:9222
+
+  $ fnd workspace --ssh user@host --delete-remote-dir
 ```
 
-_See code: [src/commands/workspace/index.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.2/src/commands/workspace/index.ts)_
+_See code: [src/commands/workspace/index.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.3/src/commands/workspace/index.ts)_
 
 ## `fnd workspace cleanup`
 
@@ -216,9 +220,13 @@ Tear down a leftover workspace — use this if a `workspace` session dropped bef
 
 ```
 USAGE
-  $ fnd workspace cleanup --ssh <value> [--remote-base <value>] [--remote-dir <value>]
+  $ fnd workspace cleanup --ssh <value> [--delete-remote-dir] [--devtools] [--remote-base <value>] [--remote-dir
+    <value>]
 
 FLAGS
+  --delete-remote-dir    also delete the remote workspace directory (by default the synced files are left in place)
+  --devtools             also strip the chrome-devtools MCP entry from the remote (only if the dropped session used
+                         --devtools)
   --remote-base=<value>  [default: /home/fnd] base dir on the remote, used to derive the default remote directory path
   --remote-dir=<value>   exact remote directory to target (defaults to the current dir mapping)
   --ssh=<value>          (required) remote to connect to, as user@host
@@ -226,15 +234,20 @@ FLAGS
 DESCRIPTION
   Tear down a leftover workspace — use this if a `workspace` session dropped before it could clean up after itself.
 
-  Terminates any Mutagen sync sessions this machine started for the directory and strips the matching chrome-devtools
-  MCP entry from the remote. With no --remote-dir, it targets the same path `workspace` would use for the current
-  directory. The synced files themselves are left in place.
+  Terminates any Mutagen sync sessions this machine started for the directory. Pass --devtools to also strip the
+  matching chrome-devtools MCP entry from the remote (only do this if the dropped session used --devtools). With no
+  --remote-dir, it targets the same path `workspace` would use for the current directory. The synced files themselves
+  are left in place unless you pass --delete-remote-dir.
 
 EXAMPLES
   $ fnd workspace cleanup --ssh user@host
 
   $ fnd workspace cleanup --ssh user@host --remote-dir /home/fnd/cole/fnd-cli
+
+  $ fnd workspace cleanup --ssh user@host --devtools
+
+  $ fnd workspace cleanup --ssh user@host --delete-remote-dir
 ```
 
-_See code: [src/commands/workspace/cleanup.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.2/src/commands/workspace/cleanup.ts)_
+_See code: [src/commands/workspace/cleanup.ts](https://github.com/FireNet-Designs/fnd-cli/blob/v2.3.3/src/commands/workspace/cleanup.ts)_
 <!-- commandsstop -->

package/dist/commands/workspace/cleanup.d.ts

@@ -3,6 +3,8 @@ export default class WorkspaceCleanup extends Command {
     static description: string;
     static examples: string[];
     static flags: {
+        'delete-remote-dir': import("@oclif/core/interfaces").BooleanFlag<boolean>;
+        devtools: import("@oclif/core/interfaces").BooleanFlag<boolean>;
         'remote-base': import("@oclif/core/interfaces").OptionFlag<string, import("@oclif/core/interfaces").CustomOptions>;
         'remote-dir': import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
         ssh: import("@oclif/core/interfaces").OptionFlag<string, import("@oclif/core/interfaces").CustomOptions>;

package/dist/commands/workspace/cleanup.js

@@ -3,12 +3,22 @@ import chalk from 'chalk';
 import { basename } from 'node:path';
 import { buildContext, buildMutagenTerminateSelectorArgs, DEFAULT_MOUNT_BASE, hasMutagen, hasSshClient, parseSshTarget, runMutagen, runRemoteCleanup, slugify, } from '../../lib/workspace.js';
 export default class WorkspaceCleanup extends Command {
-    static description = 'Tear down a leftover workspace — use this if a `workspace` session dropped before it could clean up after itself.\n\nTerminates any Mutagen sync sessions this machine started for the directory and strips the matching chrome-devtools MCP entry from the remote. With no --remote-dir, it targets the same path `workspace` would use for the current directory. The synced files themselves are left in place.';
+    static description = 'Tear down a leftover workspace — use this if a `workspace` session dropped before it could clean up after itself.\n\nTerminates any Mutagen sync sessions this machine started for the directory. Pass --devtools to also strip the matching chrome-devtools MCP entry from the remote (only do this if the dropped session used --devtools). With no --remote-dir, it targets the same path `workspace` would use for the current directory. The synced files themselves are left in place unless you pass --delete-remote-dir.';
     static examples = [
         '<%= config.bin %> <%= command.id %> --ssh user@host',
         '<%= config.bin %> <%= command.id %> --ssh user@host --remote-dir /home/fnd/cole/fnd-cli',
+        '<%= config.bin %> <%= command.id %> --ssh user@host --devtools',
+        '<%= config.bin %> <%= command.id %> --ssh user@host --delete-remote-dir',
     ];
     static flags = {
+        'delete-remote-dir': Flags.boolean({
+            default: false,
+            description: 'also delete the remote workspace directory (by default the synced files are left in place)',
+        }),
+        devtools: Flags.boolean({
+            default: false,
+            description: 'also strip the chrome-devtools MCP entry from the remote (only if the dropped session used --devtools)',
+        }),
         'remote-base': Flags.string({
             default: DEFAULT_MOUNT_BASE,
             description: 'base dir on the remote, used to derive the default remote directory path',
@@ -43,9 +53,18 @@ export default class WorkspaceCleanup extends Command {
         else {
             this.log(chalk.yellow('Mutagen CLI not found on PATH — skipping sync termination.'));
         }
-        // Strip any chrome-devtools MCP config this workspace left on the remote.
-        this.log(chalk.dim('Removing any leftover chrome-devtools MCP config on the remote…'));
-        const code = await runRemoteCleanup(target2, remoteDir);
+        // Strip any chrome-devtools MCP config this workspace left on the remote
+        // (only when asked), and optionally delete the synced directory itself.
+        if (flags.devtools) {
+            this.log(chalk.dim('Removing any leftover chrome-devtools MCP config on the remote…'));
+        }
+        if (flags['delete-remote-dir']) {
+            this.log(chalk.dim('Deleting the remote workspace directory…'));
+        }
+        const code = await runRemoteCleanup(target2, remoteDir, {
+            deleteRemoteDir: flags['delete-remote-dir'],
+            removeDevtoolsMcp: flags.devtools,
+        });
         if (code === 0) {
             this.log(chalk.green('✓ Done.'));
         }

package/dist/commands/workspace/index.d.ts

@@ -3,6 +3,7 @@ export default class Workspace extends Command {
     static description: string;
     static examples: string[];
     static flags: {
+        'delete-remote-dir': import("@oclif/core/interfaces").BooleanFlag<boolean>;
         devtools: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
         'remote-base': import("@oclif/core/interfaces").OptionFlag<string, import("@oclif/core/interfaces").CustomOptions>;
         source: import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;

package/dist/commands/workspace/index.js

@@ -10,8 +10,13 @@ export default class Workspace extends Command {
         '<%= config.bin %> <%= command.id %> --ssh user@host --remote-base /home/fnd',
         '<%= config.bin %> <%= command.id %> --ssh user@host --devtools 9222',
         '<%= config.bin %> <%= command.id %> --ssh user@host --devtools 9333:9222',
+        '<%= config.bin %> <%= command.id %> --ssh user@host --delete-remote-dir',
     ];
     static flags = {
+        'delete-remote-dir': Flags.boolean({
+            default: false,
+            description: 'on exit, delete the remote workspace directory instead of leaving the synced copy in place',
+        }),
         devtools: Flags.string({
             description: 'expose your LOCAL browser to Claude on the remote via the chrome-devtools MCP. Value is "port" (same port both ends) or "remote:local" (local = this machine, where the browser runs). Your browser must already be listening with --remote-debugging-port=<local>.',
         }),
@@ -47,6 +52,7 @@ export default class Workspace extends Command {
         if (createCode !== 0) {
             this.error(`mutagen sync create failed (exit ${createCode}). Check that the remote is reachable over SSH and try again.`, { code: '1' });
         }
+        const deleteRemoteDir = flags['delete-remote-dir'];
         let code;
         try {
             // Block until the first full sync lands so the files exist before the shell opens.
@@ -64,20 +70,30 @@ export default class Workspace extends Command {
             this.log(chalk.dim('Flushing final changes and stopping the sync…'));
             await runMutagen(buildMutagenFlushArgs(ctx.syncName)).catch(() => 1);
             await runMutagen(buildMutagenTerminateArgs(ctx.syncName)).catch(() => 1);
-            // Only reach back to the remote if we put a devtools MCP config there to remove.
-            if (ctx.devtools) {
-                this.log(chalk.dim('Removing the remote chrome-devtools MCP config…'));
+            // Reach back to the remote if we left a devtools MCP config there to remove,
+            // or if we were asked to delete the synced directory.
+            if (ctx.devtools || deleteRemoteDir) {
+                const actions = [
+                    ctx.devtools ? 'removing the remote chrome-devtools MCP config' : undefined,
+                    deleteRemoteDir ? 'deleting the remote dir' : undefined,
+                ].filter(Boolean);
+                this.log(chalk.dim(`${actions.join(' and ')}…`.replace(/^./, (c) => c.toUpperCase())));
                 try {
-                    await runRemoteCleanup(target2, ctx.remoteDir);
+                    await runRemoteCleanup(target2, ctx.remoteDir, {
+                        deleteRemoteDir,
+                        removeDevtoolsMcp: Boolean(ctx.devtools),
+                    });
                 }
                 catch (error) {
-                    this.log(chalk.yellow(`Could not reach the remote to remove the devtools config (${error.message}).`));
+                    this.log(chalk.yellow(`Could not reach the remote to clean up (${error.message}).`));
                 }
             }
         }
         this.log('');
         this.log(code === 0
-            ? chalk.green('✓ Workspace closed. Sync stopped; the remote copy is left in place.')
+            ? chalk.green(deleteRemoteDir
+                ? '✓ Workspace closed. Sync stopped; the remote dir was deleted.'
+                : '✓ Workspace closed. Sync stopped; the remote copy is left in place.')
             : chalk.yellow(`Session ended with exit code ${code}. Cleanup attempted above.`));
     }
     /** Verify this machine can drive the sync before we connect. */

package/dist/lib/workspace.d.ts

@@ -92,15 +92,25 @@ export declare const shQuote: (value: string) => string;
  * optionally wires up the chrome-devtools MCP, and drops into a login shell.
  */
 export declare const buildRemoteScript: (ctx: WorkspaceContext) => string;
-/** Run the remote-side teardown (strip this project's chrome-devtools MCP) over a fresh ssh connection. */
-export declare const runRemoteCleanup: (target: string, remoteDir: string) => Promise<number>;
+/** Options controlling what the remote-side teardown does. */
+export interface RemoteCleanupOptions {
+    /** Delete the workspace dir after cleanup; by default the synced copy is left in place. */
+    deleteRemoteDir?: boolean;
+    /** Strip this project's chrome-devtools MCP entry — only when the workspace registered one (--devtools). */
+    removeDevtoolsMcp?: boolean;
+}
+/** Run the remote-side teardown over a fresh ssh connection. */
+export declare const runRemoteCleanup: (target: string, remoteDir: string, opts?: RemoteCleanupOptions) => Promise<number>;
 /**
- * The remote-side teardown script: strip this project's chrome-devtools MCP via
- * the `claude` CLI. Runs from inside the workspace dir so local scope resolves to
- * the right project. A no-op if there is nothing to undo. The synced files
- * themselves are left in place — they are a real copy, not a mount.
+ * The remote-side teardown script. Runs from inside the workspace dir so the
+ * `claude` CLI's local scope resolves to the right project. The chrome-devtools
+ * MCP entry is stripped only when `removeDevtoolsMcp` is set — i.e. when the
+ * workspace registered one via --devtools; without it we never touch the user's
+ * MCP config. The synced files themselves are left in place — they are a real
+ * copy, not a mount — unless `deleteRemoteDir` is set, in which case the
+ * workspace dir is removed after any MCP config is stripped.
  */
-export declare const buildCleanupScript: (remoteDir: string) => string;
+export declare const buildCleanupScript: (remoteDir: string, opts?: RemoteCleanupOptions) => string;
 /** True if an `ssh` client is on PATH (works on Windows, macOS, Linux). */
 export declare const hasSshClient: () => boolean;
 /** True if the Mutagen CLI is on PATH and runnable. */

package/dist/lib/workspace.js

@@ -124,22 +124,33 @@ export const buildRemoteScript = (ctx) => {
         '"${SHELL:-bash}" -l',
     ].join('\n');
 };
-/** Run the remote-side teardown (strip this project's chrome-devtools MCP) over a fresh ssh connection. */
-export const runRemoteCleanup = (target, remoteDir) => new Promise((resolve, reject) => {
-    const child = spawn('ssh', [target, buildCleanupScript(remoteDir)], { stdio: 'inherit' });
+/** Run the remote-side teardown over a fresh ssh connection. */
+export const runRemoteCleanup = (target, remoteDir, opts = {}) => new Promise((resolve, reject) => {
+    const child = spawn('ssh', [target, buildCleanupScript(remoteDir, opts)], { stdio: 'inherit' });
     child.once('error', reject);
     child.once('close', (code) => resolve(code ?? 0));
 });
 /**
- * The remote-side teardown script: strip this project's chrome-devtools MCP via
- * the `claude` CLI. Runs from inside the workspace dir so local scope resolves to
- * the right project. A no-op if there is nothing to undo. The synced files
- * themselves are left in place — they are a real copy, not a mount.
+ * The remote-side teardown script. Runs from inside the workspace dir so the
+ * `claude` CLI's local scope resolves to the right project. The chrome-devtools
+ * MCP entry is stripped only when `removeDevtoolsMcp` is set — i.e. when the
+ * workspace registered one via --devtools; without it we never touch the user's
+ * MCP config. The synced files themselves are left in place — they are a real
+ * copy, not a mount — unless `deleteRemoteDir` is set, in which case the
+ * workspace dir is removed after any MCP config is stripped.
  */
-export const buildCleanupScript = (remoteDir) => [
+export const buildCleanupScript = (remoteDir, opts = {}) => [
     `DIR=${shQuote(remoteDir)}`,
     'cd "$DIR" 2>/dev/null || { echo "Nothing to clean up: $DIR is gone." >&2; exit 0; }',
-    ...claudeDevtoolsRemoveScript(),
+    ...(opts.removeDevtoolsMcp ? claudeDevtoolsRemoveScript() : []),
+    // Remove the workspace dir last: cd out first so we don't rm the cwd out from
+    // under the shell, then delete it. Only when explicitly requested.
+    ...(opts.deleteRemoteDir
+        ? [
+            'cd / || exit 1',
+            'rm -rf "$DIR" && echo "Removed remote dir $DIR." || { echo "ERROR: could not remove $DIR" >&2; exit 1; }',
+        ]
+        : []),
 ].join('\n');
 /** True if an `ssh` client is on PATH (works on Windows, macOS, Linux). */
 export const hasSshClient = () => {

package/oclif.manifest.json

@@ -186,12 +186,26 @@
     "workspace:cleanup": {
       "aliases": [],
       "args": {},
-      "description": "Tear down a leftover workspace — use this if a `workspace` session dropped before it could clean up after itself.\n\nTerminates any Mutagen sync sessions this machine started for the directory and strips the matching chrome-devtools MCP entry from the remote. With no --remote-dir, it targets the same path `workspace` would use for the current directory. The synced files themselves are left in place.",
+      "description": "Tear down a leftover workspace — use this if a `workspace` session dropped before it could clean up after itself.\n\nTerminates any Mutagen sync sessions this machine started for the directory. Pass --devtools to also strip the matching chrome-devtools MCP entry from the remote (only do this if the dropped session used --devtools). With no --remote-dir, it targets the same path `workspace` would use for the current directory. The synced files themselves are left in place unless you pass --delete-remote-dir.",
       "examples": [
         "<%= config.bin %> <%= command.id %> --ssh user@host",
-        "<%= config.bin %> <%= command.id %> --ssh user@host --remote-dir /home/fnd/cole/fnd-cli"
+        "<%= config.bin %> <%= command.id %> --ssh user@host --remote-dir /home/fnd/cole/fnd-cli",
+        "<%= config.bin %> <%= command.id %> --ssh user@host --devtools",
+        "<%= config.bin %> <%= command.id %> --ssh user@host --delete-remote-dir"
       ],
       "flags": {
+        "delete-remote-dir": {
+          "description": "also delete the remote workspace directory (by default the synced files are left in place)",
+          "name": "delete-remote-dir",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "devtools": {
+          "description": "also strip the chrome-devtools MCP entry from the remote (only if the dropped session used --devtools)",
+          "name": "devtools",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "remote-base": {
           "description": "base dir on the remote, used to derive the default remote directory path",
           "name": "remote-base",
@@ -241,9 +255,16 @@
         "<%= config.bin %> <%= command.id %> --ssh user@host --source local",
         "<%= config.bin %> <%= command.id %> --ssh user@host --remote-base /home/fnd",
         "<%= config.bin %> <%= command.id %> --ssh user@host --devtools 9222",
-        "<%= config.bin %> <%= command.id %> --ssh user@host --devtools 9333:9222"
+        "<%= config.bin %> <%= command.id %> --ssh user@host --devtools 9333:9222",
+        "<%= config.bin %> <%= command.id %> --ssh user@host --delete-remote-dir"
       ],
       "flags": {
+        "delete-remote-dir": {
+          "description": "on exit, delete the remote workspace directory instead of leaving the synced copy in place",
+          "name": "delete-remote-dir",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "devtools": {
           "description": "expose your LOCAL browser to Claude on the remote via the chrome-devtools MCP. Value is \"port\" (same port both ends) or \"remote:local\" (local = this machine, where the browser runs). Your browser must already be listening with --remote-debugging-port=<local>.",
           "name": "devtools",
@@ -296,5 +317,5 @@
       ]
     }
   },
-  "version": "2.3.2"
+  "version": "2.3.3"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@firenet-designs/fnd-cli",
   "description": "A new CLI generated with oclif",
-  "version": "2.3.2",
+  "version": "2.3.3",
   "author": "Cole Denslow",
   "contributors": [
     "Justin Schellenberg"