session-debugginglisted

# Debugging live sessions (snapshot / send / exec) ## Overview You have no TTY, so `session attach` is not for you (it splices a real local terminal to the remote PTY). The non-TTY trio gives you eyes and hands on any live interactive session: ```bash harness-cli session snapshot <id> # SEE the current screen (read-only) harness-cli session send -enter <id> <text> # TYPE keystrokes (co-write, no takeover) harness-cli session exec <id> <cmd>... # RUN one shell cmd, wait, get output + exit code harness-cli session resize --size 40x150 <id> # SIZE the PTY (no takeover) ``` All three authenticate with your task ticket — no operator PSK — but they do **not** need the same capability, because they are not the same power: | tool | attach mode | capability | |------|-------------|------------| | `snapshot` | `view` | `exec_view` | | `send` / `exec` | `cowrite` | `exec_cowrite` | | `resize` | `view` | `exec_view` **+ `exec_resize`** | `snapshot` is a read-only attach and never disturbs whoever is driving; `send`/`exec` co-write into the live PTY without taking over the human controller and without resizing. The human may be attached in parallel — that is expected. The caps are checked with implication (each accepts itself or anything stronger), so `exec_cowrite` alone covers all three and `exec_control` covers everything. If you were granted only `exec_view` you can look but not type — that is a deliberate grant, not a misconfiguration: ask your spawner for `