mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 00:02:23 +00:00
l0ng-ai
9833c772b0
`tty7 run -- /no/such/binary` answered "no such shell on this machine". The check in front of a spawn serves both the configured shell and a command handed to `run`, and its three sentences all said "shell" — so someone who typed `tty7 run -- ./build.sh` was told tty7 had misunderstood what they asked for. They say "program" now, which is true of both callers; the CLI already prefixes "spawning `…`" with the context. The other half is worse and is documented rather than changed: `echo hi | tty7 run -- cat` never returns. The command reads the pane's terminal, which nothing is typing into, so it waits for input that cannot arrive — and there is no error, because an idle terminal is not a failure. Output streams back; input does not go the other way. Measured, after a first attempt sat for ten minutes: a bounded re-run with `head -1` was still running at ten seconds with the pipe unread. For a CLI whose stated audience is agents, `cmd | tty7 run -- …` is a natural thing to try and an unbounded wait is the worst way to answer it. Forwarding stdin would be a new capability; saying so is not, and `sh -c 'cat < input.txt'` gets the input there today.