tine fork

tine fork creates a new run containing the selected step and its ancestors. The new graph records fork metadata and starts with status: running.

Usage

tine fork <run_id_or_path> --from-step <index_or_id_prefix> [--save <path>] [--force]

Arguments

• <run_id_or_path> accepts a direct file path or a prefix found in .tine_runs/.
• --from-step accepts a traversal index, full step ID, or unique step ID prefix.
• --save chooses the output path. Without it, the CLI writes to .tine_runs/.
• --force allows overwriting an existing --save path.

Basic Example

tine fork failed.tine --from-step 5
tine fork failed.tine --from-step 6d4a0b270a5f --save experiments/retry.tine

# Forked a3f8c1d2e9f0 -> b7e2f4a1c033 from 6d4a0b270a5f
Saved: experiments/retry.tine

Fork Into a Harness

Add harness options to continue the fork immediately through an external CLI. The harness receives run context and opentine records the new branch.

tine fork failed.tine \
  --from-step 5 \
  --harness codex \
  --prompt "Retry from the fork context using a smaller change." \
  --save experiments/retry_codex.tine

Follow-Up

Use tine show to inspect the fork and tine diff to compare it with the source run.