A debuggable automation engine. Trace every step. Replay from any point.
flyto-core
A debuggable automation engine. Trace every step. Replay from any point.
Try in 30 seconds
pip install flyto-core[browser] && playwright install chromium
flyto recipe competitor-intel --url https://github.com/pricing
Step 1/12 browser.launch ✓ 420ms
Step 2/12 browser.goto ✓ 1,203ms
Step 3/12 browser.evaluate ✓ 89ms
Step 4/12 browser.screenshot ✓ 1,847ms → saved intel-desktop.png
Step 5/12 browser.viewport ✓ 12ms → 390×844
Step 6/12 browser.screenshot ✓ 1,621ms → saved intel-mobile.png
Step 7/12 browser.viewport ✓ 8ms → 1280×720
Step 8/12 browser.performance ✓ 5,012ms → Web Vitals captured
Step 9/12 browser.evaluate ✓ 45ms
Step 10/12 browser.evaluate ✓ 11ms
Step 11/12 file.write ✓ 3ms → saved intel-report.json
Step 12/12 browser.close ✓ 67ms
✓ Done in 10.3s — 12/12 steps passed
Screenshots captured. Performance metrics extracted. JSON report saved. Every step traced.
What happens when step 8 fails?
With a shell script you re-run the whole thing. With flyto-core:
flyto replay --from-step 8
Steps 1–7 are instant. Only step 8 re-executes. Full context preserved.
3 recipes to try now
# Competitive pricing: screenshots + Web Vitals + JSON report
flyto recipe competitor-intel --url https://competitor.com/pricing
# Full site audit: SEO + accessibility + performance
flyto recipe full-audit --url https://your-site.com
# Web scraping → CSV export
flyto recipe scrape-to-csv --url https://news.ycombinator.com --selector ".titleline a"
Every recipe is traced. Every run is replayable. See all 32 recipes →
Install
pip install flyto-core # Core engine + CLI + MCP server
pip install flyto-core[browser] # + browser automation (Playwright)
playwright install chromium # one-time browser setup
The 85-line problem
Here's what competitive pricing analysis looks like in Python:
|
Python — 85 lines
|
flyto-core — 12 steps
Tools (6)browser.launchLaunches a browser instance for automation tasks.browser.gotoNavigates the browser to a specified URL.browser.evaluateExecutes JavaScript code within the browser context.browser.screenshotCaptures a screenshot of the current page.browser.viewportSets the browser viewport dimensions.file.writeWrites data to a local file.Configurationclaude_desktop_config.json {"mcpServers": {"flyto-core": {"command": "python", "args": ["-m", "flyto_core.mcp"]}}}Try it→Launch a browser, navigate to https://github.com/pricing, and take a full-page screenshot. →Perform a full site audit on https://your-site.com including SEO and performance metrics. →Scrape the titles from https://news.ycombinator.com and save them to a CSV file. →Replay the last failed automation step starting from step 8. Frequently Asked QuestionsWhat are the key features of Flyto Core?Deterministic execution engine for AI agents. Full execution tracing with evidence snapshots. Replay capability from any specific step. Supports browser automation via Playwright. Includes 412 modules across 78 categories. What can I use Flyto Core for?Automated competitive pricing analysis and reporting. Full website SEO and accessibility auditing. Web scraping tasks with structured data export. Debugging complex agent workflows through step-by-step replay. How do I install Flyto Core? Install Flyto Core by running: What MCP clients work with Flyto Core?Flyto Core works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support. Turn this server into reusable contextKeep Flyto Core docs, env vars, and workflow notes in Conare so your agent carries them across sessions. Need the old visual installer? Open Conare IDE. |