hive.terminal-tools-job-control
Use when launching anything that runs longer than a minute, anything that streams logs, anything you want to keep running while doing other work — or when terminal_exec auto-backgrounded on you and returned a job_id. Teaches the start→poll→wait pattern with terminal_job_logs offset bookkeeping, the `wait_until_exit=True` blocking-poll idiom, the truncated_bytes_dropped resumption signal, the merge_stderr decision, the SIGINT→SIGTERM→SIGKILL escalation ladder via terminal_job_manage, and the hard rule that jobs die when the terminal-tools server restarts. Read before calling terminal_job_start,
npx skills add aden-hive/hive --skill terminal-tools-job-control --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Background job control Background jobs are how you do things that take time without blocking your conversation. Three tools cover the surface: `terminal_job_start`, `terminal_job_logs`, `terminal_job_manage`. ## When to use a job - Builds, deploys, long tests - Processes you want to monitor (streaming a log file, a dev server) - Anything that auto-backgrounded from `terminal_exec` (you have a `job_id`; pivot to this skill's idioms) For one-shot work expected to finish quickly, `terminal_exec` is simpler. The auto-promotion mechanic in `terminal_exec` is your safety net — start with `terminal_exec`, take over with this skill if needed. ## Lifecycle ``` terminal_job_start(command, ...) → { job_id, pid, started_at } terminal_job_logs(job_id, since_offset=0, max_bytes=64000) → { data, offset, next_offset, status: "running"|"exited", exit_code, ... } # Repeat with since_offset = previous next_offset until status == "exited" # Or block once with wait_until_exit=True: terminal_job_logs(job_id, since_offset=N, wait_until_exit=True, wait_timeout_sec=60) → blocks server-side until exit or timeout ``` After exit, the job is retained for inspection (`terminal_job_manage(action="list")`) unti
- When to use a job
- Lifecycle
- Offset bookkeeping — the only rule that matters
- mergestderr — interleaved or separate
- Signal escalation
- Stdin
- Take-over: when terminalexec auto-backgrounds
- Hard rules
What does the hive.terminal-tools-job-control skill do?
Use when launching anything that runs longer than a minute, anything that streams logs, anything you want to keep running while doing other work — or when terminal_exec auto-backgrounded on you and returned a job_id. Teaches the start→poll→wait pattern with terminal_job_logs offset bookkeeping, the `wait_until_exit=True` blocking-poll idiom, the truncated_bytes_dropped resumption signal, the merge_stderr decision, the SIGINT→SIGTERM→SIGKILL escalation ladder via terminal_job_manage, and the hard rule that jobs die when the terminal-tools server restarts. Read before calling terminal_job_start,
How do I install it?
Run `npx skills add aden-hive/hive --skill terminal-tools-job-control --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aden-hive/hive, a repository with 10,850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.