gob

You can manage long-running background processes by using a unified CLI to start, monitor, and stream logs from jobs. This allows development tasks like background servers and file watchers to run concurrently without blocking your active workflow.

To start a background server, use the add command with your desired script to immediately get a job ID running in the background. You can then stream its logs by passing the job ID to the stdout command to monitor real-time output.

The best way to run concurrent jobs is using a CLI that applies per-directory scoping to isolate tasks. It provides deterministic command semantics to add, run, and await multiple background processes concurrently within your specific project directories.

Yes, you can stop or restart a background job without losing state because the CLI manages the complete job lifecycle. It supports stopping, restarting, and removing jobs by their specific job IDs while maintaining your per-directory scoping.

Background job management works with file watchers and concurrent agent activity by applying deterministic command semantics to development workflows. It orchestrates long-running processes, streaming logs and managing lifecycles so tasks run concurrently without blocking agents.

To wait for a command to finish, use the run command to execute it and stream output directly until completion. This ensures you capture the full process logs synchronously while the task completes its execution lifecycle.