| name | jump |
| description | Drive long-running terminal commands and AI coding agents through jump sessions. Use when the user asks to run a command in the background, send input to a running session, wait for an agent's turn to finish, orchestrate multiple agents in parallel, or capture output from a tmux/screen-style session. |
jump
Primitives
jump --no-attach <cmd>
jump <cmd> < /dev/null
jump --send <id> [text]
jump --wait <id>
jump --tail N <id>
jump --list
jump --kill <id>
--list IDs are 8-character prefixes; pass them directly to --send / --wait / --tail / --kill.
Sequential orchestration
id=$(jump --no-attach pi "implement the feature")
jump --wait $id
jump --send $id < review.txt
jump --wait $id
jump --tail 100 $id
Parallel orchestration
ids=()
for ticket in fa-48 fa-49 fa-52; do
ids+=( "$(jump --no-attach pi "Implement $ticket. Return when done.")" )
done
for id in "${ids[@]}"; do
jump --wait --timeout 600 "$id" || echo "$id failed: $?"
done
for id in "${ids[@]}"; do
echo "=== $id ==="
jump --tail 100 "$id"
done
--wait exit codes
0 agent reached idle2 session died3 --timeout elapsed
--wait only works for agent sessions (claude, codex, pi). For shell commands use the blocking piped flow: jump make build < /dev/null.
Other agents have one-shot modes
Agents stay running by default. To make them exit after one prompt, use the agent's print mode: pi -p, claude -p, codex exec. Pair with the piped flow for fire-and-forget:
jump pi -p "summarize this PR" < /dev/null
Sending control characters
printf '\x03' | jump --send --no-submit $id
Reference
