jb

Background job managers persist command output and survive session disconnects. jb starts jobs with immediate IDs, stores logs locally, and lets you retrieve output anytime via jb logs <id>, so builds, tests, and deployments continue even if your connection drops.

Yes. jb assigns unique IDs to each job, tracks status via jb status <id>, and supports named references for easy tracking. You can start multiple parallel tasks—tests, builds, deployments—and check their progress or tail live logs with jb logs <id> --follow.

jb implements timeouts and retry logic natively. Set execution constraints when starting jobs, gracefully stop tasks with jb stop, and retry failed commands without manual reexecution. Idempotent keys prevent duplicate work across retries.

jb detaches jobs from your session and stores state in ~/.jb. Start a job with jb run, receive an ID immediately, close your terminal, and reconnect later to check status or stream logs. Jobs persist independently of your shell session.

No prerequisites or external dependencies required. jb is a lightweight CLI tool that works with any long-running command—migrations, server startup, CI/CD pipelines. Store and manage everything locally under ~/.jb without additional configuration.

Yes. Use jb logs <id> --follow to stream output in real time as your command executes, or retrieve complete logs after the job finishes. Named job references make it easy to tail specific tasks without remembering numeric IDs.