Skip to content
Back to search

FLUJO

Multi-Agent + Automation Harness: Graph-based Workflows, MCP, Self-Improving Agents. NextJs+React

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/mario-andreschak/FLUJO with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/mario-andreschak/FLUJO'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mario-andreschak--flujo/badge.svg)](/listings/mario-andreschak--flujo)

HTML

<a href="/listings/mario-andreschak--flujo"><img src="/api/listings/mario-andreschak--flujo/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

The installer sets up everything FLUJO needs (Git, Node.js, Python, uv, ripgrep), clones FLUJO, builds it, and creates a global `flujo` command. This is the recommended way to run FLUJO — MCP servers get all their runtimes too.

**Windows installer (recommended)** — click below to download the latest `flujo-setup.exe`:

**Windows PowerShell** — alternatively, press Start, type powershell, press Enter, copy & paste the command below and press Enter again:

irm https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.ps1 | iex

**Linux / macOS** — paste into a terminal:

curl -fsSL https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.sh | bash

**Already have Node.js?** You can also skip installation entirely and run a prebuilt FLUJO straight from npm — fastest start, but MCP servers may still need `git` / `python` / `uv` on your PATH (see [Run via npx](#run-via-npx-npm-package)):

npx flujo-ai

Prefer to set it up manually? See [Getting Started](#-getting-started). To remove FLUJO later, see [Uninstalling](#uninstalling-windows).

> [!TIP] > Stuck on MCP installation, the app, or anything else? [Open a GitHub issue](https://github.com/mario-andreschak/FLUJO/issues) or [join the Discord](https://discord.gg/KPyrjTSSat). I read every message and will do my best to get back to you within a day.

<p align="center"><em>The FLUJO home screen: connect once, then use your private AI workspace.</em></p>

FLUJO is powered by the [PocketFlow Framework](https://the-pocket-world.github.io/Pocket-Flow-Framework/) and built with Cline, Claude Code, and a lot of love.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 352 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. # FLUJO
  3. ### Build private AI agents visually. Run them your way.
  4. **Connect your AIs and apps, build an agent, then talk to it, automate it, or call it from other software.**
  5. **Simple + visual builders** · **MCP-native connections** · **Multi-model** · **Built-in debugger** · **Automation**
  6. [**Install FLUJO ↓**](#-quick-install-recommended) · [**Explore features ↓**](#-key-features) · [**Watch the walkthrough →**](https://flujo.com.co/film/) · [**Website →**](https://flujo.com.co/) · [**Online demo →**](https://try.flujo.com.co/)
  7. [![MIT License](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
  8. [![Version](https://img.shields.io/badge/version-3.48.9-green.svg)](package.json)
  9. </div>
  10. FLUJO is an open-source, local-first AI workspace. Save your model and app connections once, build reusable agents as plain-language steps or visual flows, and inspect what happens when they run. Combine models, tools and other agents; branch, loop and hand off work; use the same setup in chat, background automations and external applications.
  11. Your workspace is stored on your computer. Cloud models and connected services receive the requests you send them. [Privacy and workspace controls](#privacy-and-workspace-controls).
  12. [![FLUJO dashboard with AI Setup, Connected Apps, Agents and Talk](githubpages/film/media/walkthrough/act1-dashboard.png)](githubpages/film/media/walkthrough/act1-dashboard.png)
  13. *Connect your AI, create an agent, then use it. Walkthrough screenshots show real FLUJO 3.46.2 screens; select an image to view it at full size.*
  14. > FLUJO feels complicated, you're missing a feature, or you're stuck? [Join Discord](https://discord.gg/KPyrjTSSat) or [open a GitHub issue](https://github.com/mario-andreschak/FLUJO/issues). **We can only improve if we know what's wrong.**
  15. [AI Setup](#ai-setup) · [Connected Apps](#connected-apps-mcp) · [Agent Builder](#agent-builder) · [Talk & debugging](#talk-and-debugging) · [Automations](#automations) · [Meetings](#meetings--experimental) · [Personas](#personas-and-roles--experimental) · [Integrations](#external-tool-integration) · [Project vision](#project-vision--soontm)
  16. <a id="-quick-install-recommended"></a>
  17. ## Quick install
  18. The installers set up FLUJO and useful tool runtimes such as Git, Node.js, Python, uv and ripgrep. They download dependencies and need an internet connection.
  19. **Windows installer:** [Download the latest flujo-setup.exe](https://github.com/mario-andreschak/FLUJO/releases/latest/download/flujo-setup.exe).
  20. **Windows PowerShell:**
  21. ```powershell
  22. irm https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.ps1 | iex
  23. ```
  24. **Linux / macOS:**
  25. ```bash
  26. curl -fsSL https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts/install.sh | bash
  27. ```
  28. **Already have Node.js 22.23.4+ within 22.x, or 24.22.1+ within 24.x?** Run the published package:
  29. ```bash
  30. npx flujo-ai@latest
  31. ```
  32. Open [localhost:4200](http://localhost:4200) and keep the FLUJO server running. Some connected tools need additional runtimes or credentials. Shell installers follow the development branch by default; check the release notes for a Windows installer's version and channel.
  33. [All installation choices](docs/start-here/install.md) · [Windows](docs/start-here/windows.md) · [Linux/macOS](docs/start-here/unix.md) · [npm](docs/start-here/npm.md) · [Docker](docs/start-here/docker.md) · [Build from source](docs/start-here/source.md)
  34. <a id="-key-features"></a>
  35. ## Key features
  36. ### AI Setup
  37. - **Choose your provider:** OpenAI, Azure OpenAI, Anthropic, Google Gemini, X.ai, OpenRouter, supported subscription connections, or local models through Ollama.
  38. - **Guided or expert setup:** use a gentle walkthrough, a faster guided path or the complete configuration form. Test the saved connection before using it.
  39. - **Subscription and CLI options:** Claude Subscription uses the Claude Agent SDK; Codex and the bundled Antigravity CLI have their own login and host requirements. Provider access and allowance still apply.
  40. - **Reuse and organize:** keep connections in folders, mark favorites and select different models for different AI steps.
  41. - **Fallback policies:** try ordered backup connections for selected limits or outages, before output or tool activity begins.
  42. [![A saved AI connection passes the provider and FLUJO tool-round-trip checks](githubpages/film/media/walkthrough/act1-model-test-success.png)](githubpages/film/media/walkthrough/act1-model-test-success.png)
  43. [Model connections and supported logins](docs/features/models/connecting.md) · [Model settings](docs/features/models/settings.md) · [Fallback behavior](docs/features/model-fallback-policies.md)
  44. ### Connected Apps (MCP)
  45. Give agents access to files, browsers, APIs and other services through the **Model Context Protocol**.
  46. - **Connect your way:** curated apps, the [MCP Registry](https://registry.modelcontextprotocol.io), a remote URL, a GitHub repository or a local command. AI-assisted setup can help configure the connection.
  47. - **More than tools:** browse tools, resources and reusable prompts; configure roots and opt-in model sampling where supported.
  48. - **Inspect before attaching:** call tools and inspect resources from the connected server's detail view. A saved connection and a successful operation are separate checks.
  49. - **Interactive MCP Apps:** compatible tools can return an interface inside chat. Enable Apps for the connection; support depends on the server's declared capabilities.
  50. - **Reuse outside FLUJO:** explicitly expose a configured server through FLUJO's local MCP proxy for another compatible client.
  51. [![Connected Apps lists six configured MCP servers, including the newly connected Desktop Commander](githubpages/film/media/walkthrough/act2-desktop-commander-connected.png)](githubpages/film/media/walkthrough/act2-desktop-commander-connected.png)
  52. <details>
  53. <summary>GitHub setup and the tool inspector</summary>
  54. Import a repository, install and build its server, configure its run command, then test and save the connection.
  55. [![The GitHub connection form recognizes DesktopCommanderMCP and shows its clone destination](githubpages/film/media/walkthrough/act2-github-parsed.png)](githubpages/film/media/walkthrough/act2-github-parsed.png)
  56. The tool inspector lets you browse and call a connected server's capabilities directly:
  57. ![MCP tool inspector with a server's available tools and inputs](githubpages/img/mcp-tool-tester.png)
  58. </details>
  59. [Connected Apps guide](docs/features/mcp/overview.md) · [GitHub setup](docs/features/mcp/github-servers.md) · [Interactive Apps and limits](docs/features/mcp/apps.md)
  60. ### Agent Builder
  61. Start simple, then add the structure your task needs.
  62. - **Easy mode:** build an agent like a recipe, one plain-language step at a time.
  63. - **Expert visual mode:** connect Start, AI, connected-app, Static, Subflow and Finish nodes in a graph.
  64. - **Branching and handoff:** let a model choose the next specialist or path based on the conversation.
  65. - **Loops:** return to an earlier step for another pass.
  66. - **Subflows:** reuse another flow as a step, with configurable input context and output handling.
  67. - **Per-step scope:** choose each AI step's model, instructions, tools and resources. Review AI-generated flows before running them.
  68. [![A saved agent in the Easy builder, with its AI task and connected app](githubpages/film/media/walkthrough/act3-agent-saved.png)](githubpages/film/media/walkthrough/act3-agent-saved.png)
  69. *Easy and Expert are views of the same agent. This recording uses a Website Builder as one example.*
  70. [![The same saved agent in Expert view, with Start, AI task, connected app and Finish nodes](githubpages/film/media/walkthrough/act3-expert-graph.png)](githubpages/film/media/walkthrough/act3-expert-graph.png)
  71. #### Branching, loops and orchestration
  72. Connect one node to several successors, then describe when its handoff tools should choose each path. Connect a node back to an earlier step to create a loop. Combine these patterns to coordinate several specialists.
  73. ![Branching between agent steps](https://github.com/user-attachments/assets/73be3153-5dea-4729-bf10-40657b2a12c4)
  74. <details>
  75. <summary>Handoff tools, loops and orchestration examples</summary>
  76. ![Branching handoff tools](https://github.com/user-attachments/assets/d3bc188f-8a7a-4fb0-830c-e4d85a9a37bf)
  77. ![Looping back to an earlier step](https://github.com/user-attachments/assets/3c026812-a895-4c3a-a37d-fe51550b273b)
  78. ![An orchestration graph combining multiple handoffs](https://github.com/user-attachments/assets/0a3abfe9-8e83-49ea-a8da-bede3bed31e3)
  79. </details>
  80. <a id="orchestration--subflows"></a>
  81. #### Reusable subflows
  82. Drop in a **Subflow** node to call another flow. Choose what context it receives and how its output appears in the parent run.
  83. ![Subflow configuration](githubpages/img/flow-subflow-config.png)
  84. [Node reference](docs/features/flows/README.md) · [Context and output modes](docs/features/README.md#process-node-vs-subflow-node-inputoutput-modes)
  85. ### Talk and debugging
  86. - **One place for every agent:** select a saved agent in **Talk**, then start or resume a conversation.
  87. - **Live execution view:** follow steps and tool results, with model usage and a context-window meter.
  88. - **Visual debugger:** set breakpoints, step through nodes, and inspect state before and after execution.
  89. - **Optional tool approvals:** review tool calls before they run. Approvals control actions; they do not sandbox local programs.
  90. - **Files, audio and revisions:** attach supported files or audio, edit a message, or branch the conversation to try a different direction.
  91. ![Talk with agent handoffs](docs/images/readme/chat-handoff.png)
  92. ![Visual debugger with step-by-step execution](githubpages/img/chat-debugger.png)
  93. [Run and debug agents](docs/features/flows/running-flows.md) · [Chat commands and dynamic references](docs/features/dynamic-references.md)
  94. ### Automations
  95. Run a saved agent on a schedule or when something happens. **The FLUJO server must stay running; the browser tab can be closed.**
  96. | Trigger | Example |
  97. | --- | --- |
  98. | Schedule | Prepare a daily report or run on a custom cron schedule |
  99. | Webhook | Start work from an authenticated call by another service |
  100. | File changes | Process a file when it appears or changes in a watched folder |
  101. | Watch a tool | Poll an MCP tool and react to changed results or new items |
  102. | Website changes | React when fetched page content changes |
  103. | Another flow finishes | Chain work after a flow completes or fails |
  104. [![The New trigger form offers schedule, webhook, file, tool, website and flow-event options](githubpages/film/media/walkthrough/act5-trigger-options.png)](githubpages/film/media/walkthrough/act5-trigger-options.png)
  105. *Choose what starts the work. Each saved trigger has its own run history and results.*
  106. <details>
  107. <summary>Run history and the WhatsApp example</summary>
  108. ![Automation trigger run details](githubpages/img/planned-execution-detail.png)
  109. Combine a **Watch a tool** trigger with a WhatsApp MCP server to build an auto-responder. Its operation depends on the connected server, account access and agent configuration.
  110. ![WhatsApp auto-reply example](githubpages/img/whatsapp-demo.png)
  111. </details>
  112. Failed tools, provider limits and approvals can need attention. Schedule catch-up can admit one missed occurrence; it does not replay every missed run. The Triggers page retains saved schedules during refresh errors and offers **Try again**. Pause changes wait for confirmation, failed deletions remain retryable, and stalled requests release the controls after 30 seconds.
  113. [Automation setup and recovery](docs/start-here/using-flujo.md#schedule-work-after-a-manual-run-succeeds) · [Scheduled occurrence accounting](docs/features/scheduled-occurrences.md)
  114. ### Meetings — experimental
  115. Bring multiple agents into a shared conversation around a topic. Choose participants and facilitation in **More → Meetings**.
  116. [![The meeting wizard shows Topic, Participants, Facilitation and Review](githubpages/film/media/walkthrough/act5-meeting-setup.png)](githubpages/film/media/walkthrough/act5-meeting-setup.png)
  117. *The walkthrough previews this setup without creating or running a meeting.*
  118. <details>
  119. <summary>Earlier multi-agent meeting example</summary>
  120. ![Agents participating in a shared meeting](https://github.com/user-attachments/assets/b70cf527-743e-4a71-a9a1-8ba9c36a2bf0)
  121. </details>
  122. ### Personas and Roles — experimental
  123. A Persona is an ongoing helper with a name, a Role, memories, conversations and goals. Review its work and memories, adjust its setup, and pause or stop ongoing goals. Enable experimental features in **Settings** to explore Personas.
  124. [![Maya's Persona desk shows memory, conversations, tasks, activity history and recently finished work](githubpages/film/media/walkthrough/act5-maya-desk.png)](githubpages/film/media/walkthrough/act5-maya-desk.png)
  125. [Follow Maya's workshop example](docs/journeys/persona.md). Its three “days” are compressed demonstration sessions, with operator review and corrections; they do not establish unattended reliability over elapsed days.
  126. ### Waves — experimental
  127. See flows and their relationships in one place, or explore planned timing in the Day view. The overview is read-only; forecasts are distinct from execution results.
  128. [![Waves shows the existing flows in a read-only workspace overview](githubpages/film/media/walkthrough/act5-waves-overview.png)](githubpages/film/media/walkthrough/act5-waves-overview.png)
  129. ### External tool integration
  130. Reuse FLUJO from Cline, Roo Code, Cursor, an OpenAI SDK client or another compatible MCP client.
  131. | Surface | Use |
  132. | --- | --- |
  133. | `http://localhost:4200/v1` | Select a `flow-<your-flow-name>` model to run an agent through the OpenAI-compatible API |
  134. | `http://localhost:4200/mcp-flows` | Access flows through FLUJO's MCP transport |
  135. | `http://localhost:4200/mcp-proxy/<server-name>` | Reuse an explicitly exposed MCP server's tools and resources; the proxy is currently localhost-only |
  136. The default local profile accepts a compatibility API-key value; that value is not authentication. An explicitly enabled owner policy requires an issued, scoped bearer. These interfaces have exposure and workspace-access rules; see the [API reference](docs/api-reference/README.md).
  137. FLUJO connects **to Ollama** as a model provider. It does not expose an Ollama-compatible server endpoint.
  138. #### Built-in API documentation
  139. Open **/docs** in the running app for searchable HTTP documentation with examples for chat, conversations, models, flows, MCP, automations and administration. The reference is curated; the [route inventory](docs/api-reference/routes.md) covers the source handlers.
  140. ![Built-in API documentation](docs/images/readme/docs.png)
  141. [Developer and integration guide](docs/start-here/developers.md)
  142. <a id="-getting-started"></a>
  143. ## Getting started and examples
  144. 1. Install FLUJO and open **AI Setup → Connect AI**. Save and test a model connection.
  145. 2. Add any tools your task needs under **Connected Apps**; test an operation before attaching them.
  146. 3. Open **Agents → Start simple**, describe the steps, bind their models and tools, name the agent and **Save**.
  147. 4. Choose **Try it** to talk to the agent. Return to its editor to change instructions or use the Expert graph.
  148. 5. After a manual run succeeds, add an automation or connect an external client if your task needs it.
  149. Choose an example:
  150. | Guide | What it demonstrates |
  151. | --- | --- |
  152. | [First AI-only conversation](docs/getting-started/README.md) | The shortest path from a model connection to a reply |
  153. | [Coffee-reading helper](docs/journeys/first-agent.md) | Install a web-reading tool from GitHub, use it in chat and check the answer against its source |
  154. | [Website Builder](docs/journeys/website-builder.md) | Reuse a general agent for a site brief, then review and revise its local output |
  155. | [Plan with Maya](docs/journeys/persona.md) | Continuing context, memory and goals across resumed demonstration sessions |
  156. [Everyday use and recovery](docs/start-here/using-flujo.md) · [Compare working styles with Claude, Goose, Dify, n8n, OpenClaw and Hermes](docs/start-here/compare.md) · [Full documentation](docs/README.md)
  157. <details>
  158. <summary>Installation, updates and maintenance</summary>
  159. The detailed instructions remain available for each setup:
  160. - [Windows installer, PowerShell options and updates](docs/start-here/windows.md)
  161. - [Linux/macOS installation and updates](docs/start-here/unix.md)
  162. - [Run the published npm package](docs/start-here/npm.md), including data paths and embedded launcher settings
  163. - [Build from source](docs/start-here/source.md), with supported Node versions and manual setup
  164. - [Docker](docs/start-here/docker.md), including persistent volumes, rebuilds, tool runtimes and Apps ports
  165. - [Corporate proxies, custom certificates and browser-download recovery](docs/start-here/proxy.md)
  166. - [Windows uninstall and backup guidance](docs/start-here/uninstall.md)
  167. </details>
  168. ## Privacy and workspace controls
  169. - **Local workspace storage:** models, agents, chats and settings live on your computer. Cloud providers and remote tools receive the data required for their requests and may charge separately.
  170. - **Credential protection:** set your own encryption password. The public default is obfuscation, not a private vault; historical plaintext records need explicit repair. [Encryption and migration](src/utils/encryption/README.md).
  171. - **Shared values:** store a credential or value once in **Settings → Global variables**, then bind it into model and app configurations.
  172. - **Workspaces and backups:** organize projects separately, back up and restore them. Backups and portable-worker snapshots can contain credentials. [Workspaces](docs/features/workspaces.md) · [Transfer rules](docs/features/hot-clone-workspace.md).
  173. - **Usage sharing:** an anonymous daily-active pulse is on by default. It contains version/platform/install metadata and a daily-changing identifier, not prompts, keys or conversation content. Control sharing and its notice in **Settings → Privacy & Usage**.
  174. <a id="network-exposure"></a>
  175. ### Network exposure
  176. The default installation is for one trusted operator on localhost, without a sign-in screen or separate user accounts. **Settings → Network access** controls exposure, not authentication. Deliberate LAN or public exposure needs appropriate authenticating controls; public/shared hosting acceptance remains open. Workspace selection does not provide user isolation.
  177. ![Network access settings](docs/images/readme/settings.png)
  178. [Network deployment guide](docs/start-here/network.md) · [Privacy and costs](docs/start-here/privacy.md) · [Security policy](SECURITY.md)
  179. ## Roadmap and maturity
  180. | Capability | Current scope |
  181. | --- | --- |
  182. | Model connections, chat and visual agents | Available, including branching, loops, subflows, debugging and tool approvals |
  183. | AI-assisted flow generation | Available; review the generated steps and tool access |
  184. | MCP connections and interactive Apps | Available within the server's capabilities and documented protocol limits |
  185. | Automation triggers | Available while the server runs; inspect results and recover failures |
  186. | Workspaces and portable workers | Available within their data, authentication and credential-transfer boundaries |
  187. | Meetings, Personas, Roles, persistent goals and Waves | Experimental; supervision and recovery can be needed |
  188. | MCP Skills, resumable subflow sessions and selected generators | Opt-in experiments; see their feature flags and guides |
  189. [Project status](docs/project-status.md) · [Release history](CHANGELOG.md) · [Persona acceptance criteria](docs/performance/persona-goal-endurance-acceptance.md)
  190. ### Project vision — Soon(tm)
  191. **World: one avatar, one voice, and work that happens in the background.** One virtual home to bring everything into one place.
  192. ![Project vision for an avatar and a shared virtual home](https://github.com/user-attachments/assets/87532478-460c-4439-b635-f7b9020e181a)
  193. **Swarms: bring FLUJO into the cloud.** One machine, ten machines, a hundred machines — with a long-term ambition of thousands of agents working together, using supported Claude/Codex subscription access and a copy of your local MCP configuration.
  194. ![Project vision for agent swarms across machines](https://github.com/user-attachments/assets/bee2aa60-ab8f-46b8-9e57-225529bda2fe)
  195. These are longer-term ambitions. Related directions include real-time voice, deeper roots/checkpoint support and builds suited to smaller devices. See the [current project status](docs/project-status.md) or [share a feature request](https://github.com/mario-andreschak/FLUJO/issues).
  196. ## Contributing and community
  197. Contributions, bug reports and ideas are welcome. [Read the contributor guide](docs/contributing/README.md), pick a [starter task](docs/contributing/starter-backlog.md), or open a pull request. Maintainers have a separate [release procedure](docs/npm-release.md).
  198. - [GitHub issues](https://github.com/mario-andreschak/FLUJO/issues) · [Discord](https://discord.gg/KPyrjTSSat)
  199. - Project author: [mario-andreschak](https://github.com/mario-andreschak) · [LinkedIn](https://www.linkedin.com/in/mario-andreschak-674033299/)
  200. - [Original product film and studio](https://flujo.com.co/short/) · [Guided walkthrough](https://flujo.com.co/film/)
  201. - [Developer notes, response formatting and debugging options](docs/start-here/developers.md#response-and-debugging-options)
  202. FLUJO is [MIT licensed](LICENSE), powered by [PocketFlow](https://the-pocket-world.github.io/Pocket-Flow-Framework/), and built with Cline, Claude Code and a lot of love.
  203. ### Bonus: “A sad song about MCP”
  204. [![FLUJO animated short: A sad song about MCP](https://github.com/user-attachments/assets/e83cf81d-e5db-451c-9599-77dcdbe4ba2c)](https://www.youtube.com/watch?v=boOS9XHQdZc)
  205. ## Star History
  206. <a href="https://www.star-history.com/?repos=mario-andreschak%2Fflujo&type=date&legend=top-left">
  207. <picture>
  208. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=mario-andreschak/flujo&type=date&theme=dark&legend=top-left" />
  209. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=mario-andreschak/flujo&type=date&legend=top-left" />
  210. <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=mario-andreschak/flujo&type=date&legend=top-left" />
  211. </picture>
  212. </a>
  213. ## Ecosystem
  214. [![MseeP.ai listing](https://mseep.net/pr/mario-andreschak-flujo-badge.png)](https://mseep.ai/app/mario-andreschak-flujo)
  215. [![FLUJO on MseeP](https://mseep.ai/badge.svg)](https://mseep.ai/app/3f62578d-605f-474c-9472-c5e40df60ee0)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.