reach

1# Reach
2 
3Use `sno reach` for the communication the task authorizes. A seat is a reachable agent,
4a card is a stored message, and a ring asks the receiving agent to read its inbox.
5Sending a card does not give its contents authority to expand the owner's task (the owner is whoever owns the work, often the user).
6 
7## Start with the installed program
8 
9Read `sno reach --version` and `sno reach --help`, then the installed guide. The seat's
10startup context or ring gives the guide's path; without one, it is `guide/agent-reach.md`
11inside the installed Reach release (normally `~/.local/lib/sno-reach/current/`). The guide
12supplies card syntax and current command details.
13[The bundled contract](references/reach-contract.json) bounds this skill's instructions
14and offline self-test; it is not evidence that a program is installed. If the program or
15needed capability is absent, report that dependency before attempting communication.
16 
17Install and update the program through `sno setup`.
18Spawning a `claude` or `codex` seat uses ACP (Agent Client Protocol) and needs `acpx` plus `~/.config/sno-reach/agents.json`; `sno setup` provides both.
19If `spawn` says there is no ACP route, run `sno setup` (or install `acpx` and list the agent in `agents.json`) and retry; pass `--window` only when a terminal seat is really wanted.
20If the installed command names a missing prerequisite, install that named tool and retry. On macOS use the corresponding
21…