Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 14, 2026·2 min de lecture

flyto-core — Replayable Agent Execution Engine

flyto-core is an engine with traced, replayable steps and MCP-native modules; verified 270★ and includes 32+ recipes to start.

Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Native · 94/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Mcp
Installation
Pip
Confiance
Confiance : Established
Point d'entrée
flyto recipe competitor-intel --url https://github.com/pricing
Commande CLI universelle
npx tokrepo install c2e51f85-f03b-5c92-afaa-f028973d5aa4
Introduction

flyto-core is an engine with traced, replayable steps and MCP-native modules; verified 270★ and includes 32+ recipes to start.

Best for: Teams who need step-by-step traces, retries-from-step, and repeatable automation (browser, file, queues)

Works with: Python 3.x; optional Playwright for browser recipes; README shows CLI + MCP server install options

Setup time: 8-18 minutes

Key facts (verified)

  • GitHub: 270 stars · 48 forks · pushed 2026-05-13.
  • License: Apache-2.0 · owner avatar + repo URL verified via GitHub API.
  • README-backed entrypoint: flyto recipe competitor-intel --url https://github.com/pricing.

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 chromium then flyto 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.
🙏

Source et remerciements

Source: https://github.com/flytohub/flyto-core > License: Apache-2.0 > GitHub stars: 270 · forks: 48

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires