ai-remote 0.4.15 → 0.4.16

package/README.md

@@ -111,6 +111,8 @@ why `npx` is still what the examples here use.
   ai-remote key   <Code>             press keys, e.g. MetaLeft, ControlLeft+KeyA
   ai-remote exec  "cmd"              run a command in the terminal (SSH)
   ai-remote shell                    an interactive terminal
+  ai-remote reconnect                a new terminal: fresh login, fresh PATH
+  ai-remote clipboard [on|off]       share this machine's clipboard both ways
   ai-remote cp <src> <dst>           copy files; a remote path starts with ':'
   ai-remote do    "steps"            several actions in one go
   ai-remote view                     open the window on the session
@@ -214,6 +216,79 @@ npx ai-remote exec "uname -a"
 npx ai-remote shell                                # Ctrl-] to leave
 ```
 
+### The clipboard
+
+Off by default, and turned on either from the **clipboard button in the window's
+toolbar** or from a command line:
+
+```bash
+npx ai-remote clipboard on                    # both directions, until turned off
+npx ai-remote clipboard                       # what it is doing now
+npx ai-remote open 192.168.1.50 -u owner --clipboard
+```
+
+While it is on, text copied on this machine reaches the remote clipboard and text
+copied there reaches this one. Only a desktop carries a clipboard -- RDP
+negotiates a `cliprdr` channel and VNC has cut-text in the protocol -- so a
+terminal-only session has none and the toolbar button does not appear.
+
+**The bridge is the session's, not the page's.** The obvious place to put it
+would be the viewer, using the browser's `navigator.clipboard` -- but a browser
+only grants a page the clipboard while that page is focused, and the moment
+somebody wants the remote clipboard is exactly the moment they have clicked away
+into a local application to paste it. So the session does the copying, on this
+machine, whether or not a window is open; the toolbar button turns it on rather
+than doing it. Two windows on one session are two views of one switch.
+
+Two consequences worth knowing:
+
+- **It polls.** No platform gives Node a clipboard-change event, so the local
+  side is read twice a second while sharing is on. That is why it is a toggle
+  and not always on, and why off is a real off: the timer is not running and the
+  host's clipboard messages are dropped.
+- **Nothing goes round in circles.** Text that arrived from the host is not then
+  noticed by the poller and pushed back to it, and what was already on the
+  clipboard when sharing started is not treated as a change -- so turning
+  sharing on does not send something copied an hour ago.
+
+It uses whatever the platform has: `pbcopy`/`pbpaste` on macOS,
+`Set-Clipboard`/`Get-Clipboard` on Windows, and `wl-clipboard`, `xclip` or
+`xsel` on Linux. A machine with none reports the clipboard as unavailable and
+the button stays hidden rather than offering a switch that cannot work.
+
+Sharing sits behind the same control gate as keyboard and pointer input: a
+watch-only viewer can read the screen and cannot reach either clipboard.
+
+### A new terminal, after installing something
+
+A shell inherits its environment when it signs in, and nothing can change a
+running process's inherited environment from outside it. So a program installed
+a moment ago is simply not on the PATH of the shell that installed it, and
+running the command again will not find it however many times it is tried.
+
+`reconnect` is the fix, and it is the same one a person reaches for -- close the
+terminal, open another:
+
+```bash
+npx ai-remote exec "winget install OpenJS.NodeJS"
+npx ai-remote reconnect
+npx ai-remote exec "node --version"
+
+npx ai-remote exec --reconnect "node --version"   # or both in one call
+```
+
+The session, the desktop and the window stay exactly where they are; only the
+terminal is new. That also means the working directory and any exported
+variables are gone, which is the point -- it is a new login, not a refresh.
+
+On Windows a fresh login can still inherit a stale environment, because sshd
+built its own environment block when the service started. Reading the PATH
+straight out of the registry works regardless:
+
+```bash
+npx ai-remote exec '$env:Path = [Environment]::GetEnvironmentVariable("Path","Machine") + ";" + [Environment]::GetEnvironmentVariable("Path","User")'
+```
+
 ### Copying files
 
 `cp` is `scp` with the session standing in for the host: a remote path starts
@@ -280,6 +355,7 @@ where a decrypted key belongs, and it is offered from there.
 - `-s, --security MODE`: `auto` | `nla` | `tls` | `rdp` (default: `auto`).
 - `-W, --width N` / `-H, --height N`: Desktop resolution (default: 1280x800).
 - `--idle MINUTES`: Close an unused session (default: 0, never).
+- `--clipboard`: Share this machine's clipboard with the desktop, both ways.
 - `--headless` / `--no-view`: Run headless without opening the viewer window.
 - `--no-reuse`: A second session beside one that is already open.
 - `--save`: Keep the password for next time, once it has worked.
@@ -289,6 +365,7 @@ where a decrypted key belongs, and it is offered from there.
 - `--session NAME`: Which session to drive (default: the one opened last).
 - `-o, --out FILE`: Screenshot output file path (default: `screen.png`).
 - `-r, --recursive`: For `cp`, copy a directory.
+- `--reconnect`: For `exec`, open a new terminal first, then run the command.
 - `--max-edge N`: Shrink a screenshot to fit N.
 - `--json`: Output machine-readable JSON results on stdout.
 

package/SKILL.md

@@ -149,6 +149,50 @@ leave) — that one is for a human, not for an agent, because it never returns.
 Reach for the GUI when the task is genuinely graphical. Reach for `exec` for
 anything a shell can do.
 
+**After installing anything, reconnect.** A shell's environment is fixed when it
+signs in, so a `node` installed a moment ago is not on the PATH of the shell that
+installed it, and asking again will never find it:
+
+```bash
+npx ai-remote exec "winget install OpenJS.NodeJS"
+npx ai-remote reconnect                     # a new login, so a new PATH
+npx ai-remote exec "node --version"
+
+npx ai-remote exec --reconnect "node --version"   # or both in one call
+```
+
+The session, the desktop and the window all stay put — only the terminal is new,
+which also means the working directory and any exported variables are gone. On
+Windows, if a fresh login still cannot see it, sshd handed down its own stale
+environment; read the PATH straight out of the registry instead:
+
+```bash
+npx ai-remote exec '$env:Path = [Environment]::GetEnvironmentVariable("Path","Machine") + ";" + [Environment]::GetEnvironmentVariable("Path","User")'
+```
+
+Note `&&` is not valid in PowerShell 5.1 — use `;` to chain, or `if ($?) { ... }`
+when the second command should only run if the first worked.
+
+## The clipboard
+
+Off by default. The **clipboard button in the window's toolbar** turns it on, or
+from a command line:
+
+```bash
+npx ai-remote clipboard on          # both directions, until turned off
+npx ai-remote clipboard             # what it is doing now
+npx ai-remote open HOST -u USER --clipboard    # on from the start
+```
+
+While it is on, text copied on this machine reaches the remote clipboard and
+text copied there reaches this one — so a password, a path or a stack trace
+moves without being typed. Only a desktop has a clipboard: RDP negotiates one
+and VNC has it in the protocol, while an `--ssh` session has none and the button
+does not appear.
+
+Turn it off before copying anything on this machine that the remote end should
+not see. Off is a real off — nothing is read and nothing is written.
+
 ## Copying files
 
 `cp` is scp with the session standing in for the host. A remote path starts with
@@ -370,7 +414,9 @@ npx ai-remote click X,Y [--button right|middle] [--double]
 npx ai-remote type "text"
 npx ai-remote key ControlLeft+KeyA
 npx ai-remote do "key MetaLeft; wait 800; type notepad; shot s.png"
-npx ai-remote exec "command"
+npx ai-remote exec "command" [--reconnect]
+npx ai-remote reconnect                                           # a new login: fresh PATH
+npx ai-remote clipboard [on|off]                                  # share text both ways
 npx ai-remote cp [-r] SRC DST                                     # ':path' is on the session
 npx ai-remote view [--watch-only] [--close]
 npx ai-remote status | list | close [--all]

package/dist/{cli-chunk-RBCU3NX4.mjs → cli-chunk-Q33YGIDO.mjs}

@@ -1,7 +1,7 @@
 import {
   SshSession,
   TcpTransport
-} from "./cli-chunk-EYQCDSPT.mjs";
+} from "./cli-chunk-S2TWL5LF.mjs";
 
 // src/cli/shell.ts
 function bareUsername(username) {

package/dist/{cli-chunk-EYQCDSPT.mjs → cli-chunk-S2TWL5LF.mjs}

@@ -935,6 +935,18 @@ function filterDisplay(session, bytes) {
   }
   return shown ? encodeUtf8(shown) : NO_BYTES;
 }
+function announceCommand(session, command) {
+  const shown = command.replace(/\r?\n/g, " \u23CE ").trimEnd();
+  if (!shown) return;
+  session.dispatchEvent(new CustomEvent("data", {
+    detail: {
+      bytes: NO_BYTES,
+      display: encodeUtf8(`\x1B[1m${shown}\x1B[0m\r
+`),
+      isStderr: false
+    }
+  }));
+}
 function releaseDisplayFilter(session) {
   const filter = session.displayFilter;
   session.displayFilter = null;
@@ -1092,6 +1104,7 @@ var SshSession = class extends EventTarget {
     this.commandInFlight = true;
     const startedAt = Date.now();
     this.displayFilter = { begin, end, stage: "before", pending: "" };
+    announceCommand(this, text);
     this.dispatchEvent(new CustomEvent("command", {
       detail: { phase: "start", id, command: text }
     }));

package/dist/{cli-copy-NRXMTHID.mjs → cli-copy-BOF44DWQ.mjs}

@@ -1,7 +1,7 @@
 import {
   SshSession,
   TcpTransport
-} from "./cli-chunk-EYQCDSPT.mjs";
+} from "./cli-chunk-S2TWL5LF.mjs";
 import {
   SshReader,
   SshWriter