ai-remote 0.4.13 → 0.4.14

package/SKILL.md

@@ -117,7 +117,9 @@ npx ai-remote exec "hostname"
 npx ai-remote exec "dir C:\\Users"
 ```
 
-`exec` reuses the session's own account and password, so it needs no flags. Its
+`exec` reuses the session's own account and password, so it needs no flags —
+give `open` `--ssh-user NAME` or `--ssh-port N` only when the terminal signs in
+as somebody else, or on a port other than 22. Its
 stdout is the command's output, and it exits 0 when the command did and 1 when
 it did not — the command's own status is in `exitStatus` under `--json` if you
 need the number. `ai-remote shell` opens an interactive terminal (Ctrl-] to
@@ -141,7 +143,8 @@ npx ai-remote click 640,400
 
 A session that is already open gets a screen with `ai-remote vnc`, which takes
 no host because the session already knows the machine. That is the way to give a
-terminal session a desktop without closing it.
+terminal session a desktop without closing it; `--vnc-port N` if the screen is
+not on 5900.
 
 ## A host with no desktop
 
@@ -168,6 +171,35 @@ variable at all. `-i FILE` names a key instead, and repeats. A key with a
 passphrase is never read off disk: `ssh-add` it, and it is offered from the
 agent.
 
+## Passwords, and not typing them twice
+
+A desktop always wants one; a terminal usually does not, because of the keys
+above. Three places are tried, in this order:
+
+1. `AI_REMOTE_PASSWORD` in this shell, or `REMOTECTL_PASSWORD` under the other
+   name.
+2. Whatever `--save` kept for that machine.
+3. You, at the terminal — only when one is attached, and only after the first
+   two have come up empty.
+
+This shell wins, so a password exported deliberately is never quietly overridden
+by one saved months ago. There is no `--password` flag and there will not be: a
+command line is visible to every process on the machine.
+
+```bash
+npx ai-remote open 192.168.1.20 -u owner --save   # keep it, once it has worked
+npx ai-remote saved                               # what is kept, and where
+npx ai-remote forget 192.168.1.20                 # one machine; --all for every one
+```
+
+`--save` writes to the system keystore — the login keychain on macOS, the desktop
+keyring on Linux — and where there is neither, to an encrypted file under
+`~/.config/ai-remote`; the command says which it got. That file is proof against
+a glance, not against somebody who can read your home directory.
+
+`--no-prompt` (or `--batch`) turns a missing password into an immediate failure
+instead of a question. Use it in anything unattended, where a prompt is a hang.
+
 ## Sessions
 
 The session opened last is the one commands drive. With several open, name them:
@@ -181,9 +213,14 @@ npx ai-remote shot --session desk   # a name, a host, or host:port
 npx ai-remote close --all           # or `close` for the current one
 ```
 
-Nothing times out and nothing closes itself — a session that an agent left
-mid-task is a feature, not a leak — so **close what you open** when the task is
-done, or tell the user it is still running.
+`open` on a machine that already has a session attaches to that one instead of
+building a second; `--no-reuse` is how you get two on purpose.
+
+Nothing times out and nothing closes itself by default — a session that an agent
+left mid-task is a feature, not a leak — so **close what you open** when the task
+is done, or tell the user it is still running. `--idle MINUTES` at `open` time
+sets one to close itself after that long unused, for when nobody will be back to
+do it.
 
 ## Watching
 
@@ -206,6 +243,9 @@ fresh `shot` rather than trusting one from before you paused.
   SSH terminal docked on the right; its 420 pixels are removed from RDP width.
 - `ai-remote view` adds a window to a headless session later (`view --watch-only`
   for an observer one); `view --close` takes it away without ending the session.
+- `--view-port N` moves the window's local server off 7373, which matters only
+  when two sessions want it at once. `--no-open` keeps the window but does not
+  launch a browser at it.
 
 ## Reading results
 
@@ -242,6 +282,9 @@ the other half of the answer is a key: `ssh-add ~/.ssh/id_ed25519`, or
 `-i FILE`. The session's log names every key it offered and every key it passed
 over, and why.
 
+`-s nla | tls | rdp` pins the RDP security layer when `auto` picks one the host
+will not finish; it makes no difference over VNC or SSH.
+
 **Unreachable (10).** — `ai-remote probe <host>` is the one command besides
 `open` that still takes an address: it answers whether anything is listening
 before you spend a handshake finding out.
@@ -261,9 +304,10 @@ what `status` reports rather than what you asked for.
 ```bash
 export AI_REMOTE_PASSWORD=...
 npx ai-remote open HOST[:PORT] -u USER [-d DOMAIN] [--session NAME] [--fullscreen] [--side-panel]
+                               [-W 1920 -H 1080] [-s auto|nla|tls|rdp] [--save] [--idle N]
 npx ai-remote open HOST --ssh -u USER [-i ~/.ssh/id_ed25519]      # a terminal, no desktop
 npx ai-remote open HOST --vnc -u USER                             # a screen over VNC
-npx ai-remote vnc                                                 # ...or add one to this session
+npx ai-remote vnc [--vnc-port N]                                  # ...or add one to this session
 npx ai-remote shot [-o FILE] [--max-edge N] [--json]
 npx ai-remote click X,Y [--button right|middle] [--double]
 npx ai-remote type "text"
@@ -272,6 +316,7 @@ npx ai-remote do "key MetaLeft; wait 800; type notepad; shot s.png"
 npx ai-remote exec "command"
 npx ai-remote view [--watch-only] [--close]
 npx ai-remote status | list | close [--all]
+npx ai-remote saved | forget [HOST[:PORT]] [--all]
 npx ai-remote probe [HOST[:PORT]]
 ```