You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sidebar ⊕ → Add Remote Repository…: server, optional user/port, and an
absolute path, validated before anything is saved — reachability under
BatchMode (key auth or fail fast), the path being a git repository, and
zmx being installed there — so each failure names itself in the sheet
instead of surfacing later as a loop that silently does nothing.
A remote project's identity is the URI ssh://user@host[:port]/path,
following the precedent the global graph set: the daemon keys its graph
by it, nothing collides with a local checkout, and everything that
treats a path as a directory branches on RemoteProjectLocation.parse.
The daemon stays local — starting an unattended loop wraps the same zmx
argv in ssh with a remote login shell and a cd into the repository, and
the app's surfaces attach with ssh -t, plain-shell tabs included. The
opening prompt can't ride the local environment through sshd, so it is
assigned inside the quoted remote command and expanded by the same
"$GRAPHCODE_TRIGGER_PROMPT" the local path uses.
V1 limitations, stated in docs/09 and the README: kill/message/usage
stay local-only (their closures don't carry the project path yet), no
briefing or worktrees remotely, and a sleeping Mac fires no edges.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments