add 'diwan remote <machine>' to open the diwan workspace on a saved herdr machine

Threads an optional machine= kwarg through herdr_json/
herdr_diwan_workspace_id (default None, fully backward compatible),
reusing the exact focus-then-attach pattern cmd_bare already uses
locally, just against --machine <label> for the scripted focus call
and --remote <machine> for the actual interactive attach.

Verified: argparse wiring, the no-herdr-on-PATH dry-run path, and that
a bogus --machine label fails fast and cleanly (not a hang) rather than
attempting a real network connection -- confirms the warning-then-exec
fallback in cmd_remote is safe. Did not test an actual real remote
attach (no SSH path to any herdr server from this sandbox).
This commit is contained in:
marc committed 2026-11-09 18:43:08 +01:00
1 parent c7859400a1
commit 43215d6e0a
2 files changed
+38 -7

No files matched your search

+2
View File
@@ -122,6 +122,8 @@ Sessions are herdr (https://herdr.dev) terminals, not a diwan-invented session s
To resume a `DIWAN_ID`, `diwan` first checks whether its agent is still alive (`herdr agent get <id>`) and just prompts it if so; if the process has exited (normal between ticks), it finds the tab by label and starts a fresh agent in the same pane, in the same working directory — the heading's own content is what carries continuity, not agent conversation history. `diwan` shells out to the real `herdr` CLI (the `diwan` CLI has the exact calls, verified live against herdr 0.9.5; run `herdr --skill` to check this hasn't drifted on a newer version). When `herdr` isn't on PATH, every call prints what it would have run instead of failing, so the pipeline stays testable without herdr installed.
Bare `diwan` (no subcommand) focuses the local `diwan` workspace and attaches you to it interactively. `diwan remote <machine>` does the same against a herdr machine saved via `herdr machine add <ssh-target>` (see herdr's own `--help`/`--skill` for setting one up) — it focuses that machine's `diwan` workspace over the scripted `--machine` API, then execs `herdr --remote <machine>` to open an interactive attach into it. This relies on `<machine>` being usable both as a saved machine label (for the focus step) and as a raw `--remote` SSH target (for the attach) — true by default, since `herdr machine add` labels a profile after its SSH target unless `--label` overrides it.
## The harness is `pi`
diwan dispatches `pi`, and only `pi` — not a pluggable choice. It's the only herdr-supported agent kind diwan has ever needed that runs real work fully unattended: it has no per-tool-call approval gate at all (unlike e.g. Claude Code, which otherwise prompts before every edit/bash call and would defeat the "act first, report passively" model), so no permission-mode flag or similar is needed to let it act freely. The one thing that can still block a dispatch is pi's one-time project-trust decision for protected `.pi/*` resources, if a content repo ever has any — `--approve` (always passed, see the `diwan` CLI) makes that a one-shot yes instead of a hang; override with `DIWAN_PI_APPROVE` if a different flag is ever needed. `TICK.md` and `DO.md` are still plain-language procedures with nothing pi-specific baked into their wording — that's just good practice, not a promise of swapping in a different harness later.