View run logs with fabro logs
Previously, the only way to follow a workflow’s progress was through the terminal that started it. The newfabro logs command lets you view event logs for any run — active or completed — from any terminal. With --pretty, agent conversations render with formatted messages and tool calls instead of raw JSON.
-f flag follows live events as they happen.
Background workflows with —detach
You can now fork a workflow into a background process withfabro run --detach, then reconnect later with fabro logs -f. This is useful for long-running workflows where you don’t want to keep a terminal open.
Rewind workflow runs
You can now rewind a workflow run to an earlier checkpoint and resume from there. This is useful when a later stage goes off-track and you want to try again from a known-good point without restarting the entire workflow.node@visit for a particular visit count, or @ordinal for a checkpoint index.
More
CLI
CLI
- Added
fabro workflow create <name>subcommand to scaffold new workflows from a template - Added
fabro workflow listcommand showing all available workflows grouped by source - Added
fabro inspectcommand to display detailed JSON data for a workflow run - Added project-level run defaults in
fabro.toml(model, environment, sandbox image, etc.) - Added
~/.fabro/fallback for@file references
Improvements
Improvements
- Default Daytona sandbox now uses the
daytona-mediumsnapshot with standard dev tools pre-installed - Run resolution now matches workflow slugs and display names, not just run IDs
- Routing events now include context about why an edge was selected
Fixes
Fixes
- Fixed
fabro logs --prettywrapping past terminal edge on long assistant messages - Fixed empty
run_idon sandbox events inprogress.jsonl - Fixed credential-embedded GitHub URLs not being parsed correctly
- Fixed logo SVG viewBox clipping the right edge of the O
- Fixed missing
git_commit_shain run branch commit messages