voxcasterlisted

# Voxcaster — persistent interactive PTY sessions Voxcaster gives you **real pseudo-terminal sessions** that outlive a single tool call. Unlike the `Bash` tool — which blocks for the lifetime of the command, gives no interactive stdin, and offers no TTY — a Voxcaster session keeps running in the background. You spawn it, then read its output, send it input, wait for it to finish, or kill it, across many turns. ## When to reach for Voxcaster (and when not to) Use Voxcaster when a process **lives over time**: - Dev servers (`npm run dev`, `cargo run`, `flask run`, `vite`) you want up while you keep working - Watchers (`cargo watch`, `jest --watch`, `tsc -w`, `nodemon`) - Long builds/tests where you want to do other things and be told when they exit - Interactive programs that need stdin: REPLs (`python`, `node`, `irb`), `ssh`, `psql`, `gdb`, anything with a prompt - Anything that emits a TTY-only experience (progress bars, colored output, paging) - Any command you'd otherwise background with `&` and then poll with `sleep` + re-check — Voxcaster replaces that anti-pattern Keep using the plain `Bash` tool for **quick, one-shot** commands that return promptly (`ls`, `git status`, `grep`, a fast build). Voxcaster's value is persistence and interactivity; don't add its overhead to a command that finishes in a second. ## The tools | Tool | Use it for | |------|-----------| | `pty_spawn` | Start a process. `command` + `args` array (never a shell string). Returns a `pty_<id>`. |