Overnight runs
Start long jobs before you leave and pick them up later. Every tab is a detached helper process, so agents keep running after the TUI quits.
Start a named session
Keep long-running work in its own session:
beswarm session start --name nightlyStart the agents with clear stopping points and a report to write:
beswarm agent start --name migrate --agent claude --group nightly \
--prompt "Migrate the remaining modules to the new logger. Run the tests after each module. Write a summary to reports/migrate.md."Walk away
Quitting the TUI doesn't stop agents, but the machine has to stay awake: a laptop that sleeps pauses them.
If you want to check in from a shell later, leave the TUI open on the session instead of quitting it. agent, workspace, worktree and terminal commands talk to a running TUI; with none open they fail with "no beswarm is running".
note
beswarm server stop does stop agents — don't run it unless you want the work to end.
Check in from anywhere
With the TUI still open on the machine, from another shell there or over SSH from your phone (see Work from your phone):
beswarm agent list --session nightly
beswarm agent read --session nightly --name migrate --source recent-unwrapped --lines 40Pick it up
beswarm session attach --name nightlyEvery agent is where you left it. If you quit the TUI earlier, this is also how to get the CLI working again. Read the reports with beswarm artifact list.