Use when running commands expected to take several minutes or more (dev servers, large builds, full test suites).
jb run for tasks expected to take several minutes or more (dev servers, full builds, exhaustive test suites). When in doubt, run directly.jb logs --follow or jb wait to track progress without losing context.jb clean to keep the workspace responsive.| Task | Command | Strategy |
|---|---|---|
| Start Job | jb run "command" | Run in background immediately. |
| Named Job | jb run -n "build" "..." | Use names for easier tracking. |
| Wait & Finish | jb wait <id> | Block only when necessary for next steps. |
| Check Logs | jb logs <id> --tail 50 | Verify output without full context dump. |
uv sync calls).-k <key> for jobs that should not overlap (e.g., continuous build watchers).-t <duration> for exploratory tasks that might hang.jb ls: Regularly check for orphaned or failed jobs.jb status: Detailed state of the job engine.jb retry <id>: Quick recovery for transient failures.| Excuse | Reality |
|---|---|
| "It'll be fast" | It rarely is. Don't block your context on IO or compute. |
| "I'll just wait" | While waiting, you're costing tokens and time. Use jb. |
| "I'll check later" | Without jb, checking later means guessing if it finished. |