Browse documentation
Docs target stable release v0.15.0; v0.16.2 on main is unreleased.Stable vs main checked 2026-10-30

Git-shaped agent workflows

Plain show, diff, tag, and log prefer a repository when one is found. An existing file path or legacy run ID still selects portable-file behavior; --legacy forces it. Existing repo-* commands remain available.

Terminal
tine log
tine blame src/main.py:42 --git
tine git log --commit HEAD
tine branch --help
tine bisect --help

Git trailers and notes link commits to recorded runs. tine git install-hook can append Tine-Run trailers without replacing an existing hook; installing a hook changes local git behavior and is an explicit operator action. Blame matches recorded writes to files or lines; bisect uses evaluator exit codes or recorded scores.

Parallel experiments and worktrees

fan-out prepares forks from one point; run --parallel repeats capture across members and variations. Jobs, timeouts, cost budgets, environment allowlists, and resumable member state bound execution. Members run as argument arrays in owned process trees. Keys are passed only when named with --env; parallel mode refuses one shared save/autosave destination.

Terminal
tine worktree list
tine fan-out --help
tine run --help
tine fleet --help

Worktrees isolate branch directories and can attach detached git worktrees. Multi-ref moves are compare-and-swap transactions with crash recovery. Rebase and cherry-pick refuse an existing target ref without an explicit force operation.

Imports, fleets, and integrations

import --fleet turns Claude Code subagents into linked child runs while counting shared cost once. OpenCode, ATIF, and Hermes trajectories join session imports; Hermes trajectories without usage remain unpriced. fleet up/status/stop/cost operates a declared manifest only after its exact bytes are trusted.

plugin export produces a Claude Code hook/skill/MCP bundle with read-only MCP tools. It is machine-local and embeds absolute interpreter and repository paths. Third-party AdapterSpec entry points must be installed and allowlisted in user configuration before loading.

Repository aliases, hooks, agent pin files, and fleet manifests are inert until explicitly trusted on the current machine; edits revoke trust. See the tagged changelog for exact commands and limitations.