Flyto Core

Flyto2

Yep, it talks to a real robot.
It also opens websites, calls APIs, works with files, and runs the steps in between.

English · 日本語 · 한국어 · 简体中文 · Español · Português (BR)

[PyPI] [Apache-2.0] [Python 3.10+]

Try something.

Say you want to check a website, grab screenshots, collect some data, and save a report.

Run this:

pip install "flyto-core[browser]"playwright install chromiumflyto recipe competitor-intel --url https://github.com/pricing

That's a real workflow. No agent prompt needed. It opens a browser, runs the steps, and saves the results.

Want to poke around?

flyto recipes                 # see the built-in workflowsflyto modules                 # browse the toolsflyto run your-workflow.yaml  # run your own

There are 482 registered modules and 41 built-in recipes in the current Core inventory. Browser stuff, APIs, files, data, tests, and plenty more. Use what you need.

And about that robot…

We're already connecting Flyto2 to a real TurtleBot3 using ROS 2.

The robot runs its normal ROS 2 / Nav2 stack. A separate adapter talks to it. Flyto2 handles the software steps and their execution records.

No custom Flyto2 firmware on the robot. No motor drivers crammed into this repo.

This isn't a claim that every robot is plug-and-play. The current combined setup still needs its full end-to-end hardware sign-off. But the ROS 2 adapter and real-robot development are already here.

So what's in this repo?

This is flyto-core, the Python execution engine behind Flyto2.

You can call it from Python, run YAML workflows, use its local HTTP API, or hook it into an AI client through MCP.

pip install flyto-corepython -m core.mcp_server

Your agent gets access to Core's tools. Moving a physical device still requires a trusted host to approve the action.

Different device software stack? Different pack. That's how ROS 2 and other integrations stay separate without turning Core into a giant pile of device drivers.

How do I know what actually happened?

This part matters.

When a workflow runs, Flyto2 keeps a record of each step. If something fails, you can inspect the run and use checkpoints or replay where it's safe to do so.

And if a tool says “done”? Core can check the evidence it reports against the action's contract. It doesn't just throw away the trail once the command returns.

That's it. Run something, see what happened, build the next thing.

Website · Documentation · PyPI · YouTube · Issues

_{Flyto2 is the product. flyto-core is the Python package. Licensed under Apache 2.0. Security reports: GitHub advisories.}