session-resume

To resume an agent session after a long pause, run the session-resume command to automatically synchronize state, relaunch monitors, and retrieve the next action for smooth work continuation.

The best way to reinitialize a worktree agent and pick up in-progress tasks is using session resumption procedures that shell to session pickup, report state, and reconnect to live dispatches without manual intervention.

Session state reporting for recovering multi-agent environments works by checking dispatch drift, unread dispatches, agent health, and progress to ensure agents are up-to-date before resuming work.

You do not need to manually relaunch monitors when restarting an agent after an idle period; the session resumption process automatically reactivates monitors and handles state consistency checks.

If there is dispatch drift when you resume your agent session, the skill's state reporting mechanism detects the drift along with unread dispatches and agent health issues to prevent restart errors.

Yes, you can use session startup procedures for multi-agent environments as they meet the requirements for automated startup, error handling, and state consistency checks during long-term activity cycles.