walnut-peer-sessions

# Peer Sessions (`walnut peers`) The `walnut` CLI talks to the user's OTHER sessions. It needs zero configuration: - Inside a session Walnut launched, it is already on the PATH and uses the injected `WALNUT_AGENT_SOCKET` + `WALNUT_SESSION_ID`. - Started by hand (a plain terminal, an agent you launched yourself), it falls back to this host's own daemon socket and identifies as an external caller. Same commands, same capabilities; only the sender label differs, because there is no session to name. If `walnut` is not on your PATH, the daemon also installs it at `~/.local/bin/walnut`. ## Commands ```bash walnut peers list # table of the user's sessions across all hosts walnut peers list --json # machine-readable walnut peers send <target> <text...> # deliver a short text note to a peer ``` `<target>` is a session id, a unique id prefix (>= 4 chars), or a unique case-insensitive title substring. If the target is ambiguous, `walnut` exits with code 3 and prints the candidates. ## When to use it - Hand off findings: you finished an investigation another session needs. - Notify: a shared build/branch/file the other session is waiting on is ready. - Coordinate: avoid two sessions editing the same area at the same time. Keep messages short and factual (what changed, where, what the peer should do). The message appears in the peer session as a clearly-labeled peer-to-peer note. ## Safety semantics (IMPORTANT) - A peer message does **NOT** carry user ...