Main
Model automations as explicit steps so you can trace timing, capture artifacts, and replay only the failing segment.
Prefer recipes for onboarding: run a built-in recipe before authoring custom pipelines, and keep success criteria explicit.
Persist artifacts as contracts: save screenshots/reports deterministically so runs can be reviewed like CI logs.
Source-backed notes
- README quickstart shows
pip install flyto-core[browser] && playwright install chromiumthenflyto recipe .... - README shows replaying from a specific step:
flyto replay --from-step 8. - Repo description mentions 412 modules and MCP-native execution with triggers/queue/versioning/metering (verified).
FAQ
- Is this just a set of scripts?: No — it’s an engine with tracing and replay, not ad-hoc shell scripts.
- Do I need Playwright?: Only for browser recipes; core engine can run non-browser steps too.
- How do I keep runs reproducible?: Pin versions, keep inputs explicit, and persist artifacts + traces per run.