pitboss 0.1.0

CLI that orchestrates coding agents (Claude Code and others) through a phased implementation plan, with automatic test/commit loops and a TUI dashboard
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

//! `pitboss resume` — pick up a halted run from `.pitboss/state.json`.
//!
//! Resume reuses the runner driver from [`crate::cli::run::execute`] with
//! [`StartMode::Resume`], so the only behavioral delta from `pitboss run` is
//! that a missing or empty `state.json` is an error: there is nothing to
//! resume. The per-run branch is checked out, [`crate::runner::Runner`] is
//! constructed against the loaded plan / deferred / state, and execution
//! continues from `plan.current_phase` — which the runner advanced to the next
//! phase the last time it persisted state.

use std::path::PathBuf;

use anyhow::Result;

use super::run::{execute, StartMode};

/// Top-level entry point for the `resume` subcommand. `tui` toggles the
/// `ratatui` dashboard the same way [`crate::cli::run::run`] does. `pr` opts
/// the resumed run into the post-run `gh pr create` step (see
/// [`crate::cli::run::run`]). `dry_run` mirrors `pitboss run --dry-run`:
/// the configured agent is swapped for a no-op so the resumed run can be
/// exercised end-to-end without spending tokens.
pub async fn run(workspace: PathBuf, tui: bool, pr: bool, dry_run: bool) -> Result<()> {
    execute(workspace, tui, pr, dry_run, StartMode::Resume).await
}