FLUJO

Name: FLUJO
Author: mario-andreschak

Warning

Multi-Agent + Automation: Workflows, Automation, Self-Improving Agents

613stars

86forks

TypeScript

Installation

# Add to your Claude Code skills
git clone https://github.com/mario-andreschak/FLUJO

Getting Started

Guides for using ai agents skills like FLUJO.

Caveman: Cut Claude Token Use by 65%
How agent-side prompt compression works, when to use it, and when not to.
What is an AI Skills Marketplace?
Definitions, how marketplaces work, and how to choose between them in 2026.
Getting Started with AI Skills

Security ReportWarning

Last scanned: 8/23/2026

{
  "issues": [
    {
      "type": "npm-audit",
      "message": "hono: Hono: ReDoS in CORS middleware via Access-Control-Request-Headers",
      "severity": "medium"
    },
    {
      "type": "npm-audit",
      "message": "nanoid: nanoid: custom generators can loop indefinitely when size is zero",
      "severity": "high"
    },
    {
      "file": "README.md",
      "line": 42,
      "type": "remote-install",
      "message": "Install command (remote install script piped to a shell — review the source before running): \"curl -fsSL https://raw.githubusercontent.com/mario-andreschak/FLUJO/main/scripts\"",
      "severity": "low"
    }
  ],
  "status": "WARNING",
  "scannedAt": "2026-08-23T04:35:15.112Z",
  "npmAuditRan": true,
  "pipAuditRan": true,
  "promptInjectionRan": true
}

README.md

Frequently Asked Questions

What is FLUJO?

FLUJO is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by mario-andreschak. Multi-Agent + Automation: Workflows, Automation, Self-Improving Agents. It has 613 GitHub stars.

Is FLUJO safe to use?

FLUJO returned warnings in SkillsLLM's automated security scan. It has no critical vulnerabilities, but review the flagged issues in the Security Report section before adding it to your workflow.

How do I install FLUJO?

Clone the repository with "git clone https://github.com/mario-andreschak/FLUJO" and add it to your Claude Code skills directory (see the Installation section above).

What programming language is FLUJO written in?

FLUJO is primarily written in TypeScript. It is open-source under mario-andreschak on GitHub, so you can review or fork the full source.

Are there alternatives to FLUJO?

Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh FLUJO against similar tools.

Agentic AI for Beginners

Build your first AI agent from scratch - tool use, ReAct pattern, memory, deployment

41 minBeginner

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

ECC

by affaan-m

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

242,219

ai-hedge-fund-crypto soul.md

⚠️ Third-Party Software Notice

This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.

Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.

Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.

Read the Terms of Service

FLUJO

Build private AI agents visually. Run them your way.

Connect your AIs and apps, build an agent, then talk to it, automate it, or call it from other software.

FLUJO is open-source and local-first. Start with the guided setup, build agents as simple step-by-step recipes or expert visual flows, inspect every run, and expose the same agents through OpenAI-compatible and MCP endpoints — while your keys and data stay under your control.

Simple + visual builders · MCP-native · Multi-model · Built-in debugger · Automation

Visit flujo.com.co → · Watch the 2:28 product film → · Install FLUJO ↓ · Explore features ↓ · Try FLUJO online →

⚡ Quick Install (recommended)

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):

npx flujo-ai

Prefer to set it up manually? See Getting Started. To remove FLUJO later, see Uninstalling.

[!TIP] Stuck on MCP installation, the app, or anything else? Open a GitHub issue or join the Discord. I read every message and will do my best to get back to you within a day.

FLUJO Overview

FLUJO is powered by the PocketFlow Framework and built with Cline, Claude Code, and a lot of love.

🌟 Key Features

🔐 Local-first Security & Workspace Controls

Local-first by default: keep FLUJO on localhost, allow devices on your private network, or configure it for a public deployment
Encrypted at rest: API keys and other secrets are encrypted in local storage, with an optional custom encryption password for extra protection
Never sent to the browser: secrets stay server-side — the frontend only ever sees a masked placeholder, even in your own DevTools
Reusable global variables: define a key once and bind it into any AI or connected-app configuration instead of pasting it repeatedly
Backup & restore your encrypted workspace from Settings

Settings — Network Access

🤖 AI Setup

Multiple providers: OpenAI, Azure OpenAI, Anthropic (native or OpenAI-compatible), Google Gemini, X.ai (Grok), OpenRouter, Codex, and local models via Ollama
Guided or expert setup: choose a gentle walkthrough, a faster guided path, or the complete configuration form
Claude Subscription: use your Claude Pro/Max plan directly (via the Claude Agent SDK) instead of a metered API key
Reusable connections: organize configured AIs into folders, mark favorites, and reuse them across agents and conversations

AI Setup — Configured AI Connections AI Setup — Guided Connection Wizard

🔌 Connected Apps (MCP)

Guided connection: let FLUJO research an app, choose from curated options, or enter a remote URL, GitHub repository, or local command yourself
Install from anywhere: search the official MCP Registry, use curated servers verified with FLUJO, or install manually from a GitHub repo / local folder
Full MCP capability support: tools, resources, prompts, roots (workspace folders), and sampling (let a server borrow one of your models under a trust policy you control)
Tool inspection & testing: browse and call a server's tools, resources, and prompts straight from its detail view
FLUJO as an MCP proxy: re-expose any server you've configured in FLUJO to other MCP clients (Claude Desktop, Cursor, Cline, …) over Streamable HTTP — configure a server once, use it everywhere

Connected Apps — Guided Setup

Configuring a server is a guided, three-step form (define it → install & build → define how to run it) with a one-click connection test before you save:

MCP Server Configuration

Every connected server gets a detail view to browse and test its tools, resources, and prompts directly:

MCP Tool Tester

🧩 Agent Builder

Simple mode: build an agent like a recipe, one plain-language step at a time, without touching a diagram
Expert visual mode: connect Start, AI, connected-app, subflow, and Finish nodes in a drag-and-drop graph
Branching & handoff: let a model hand off to another node/agent based on the conversation, build loops, or fan out into multiple specialists
Subflows: call another flow as a single step, with its own isolated state — reuse a flow like a function
Per-node tool & prompt scoping: decide exactly which tools, resources, and system-prompt fragments each node can see

Agent Builder — Simple Setup Agent Builder — Expert Visual Mode

Branching & handoff

Connect one node to several successors, then tell the model when to use each handoff tool from the "Agent Tools" tab of its Process Node:

Branching Branching handoff tools

Loops

Connect a node back to a previous one the same way to build a loop:

Loops

Orchestration & Subflows

Combine multiple handoffs and loops to build an orchestrator, or drop in a Subflow node to run another flow as a single, reusable step with its own isolated state:

Orchestration Subflow configuration

💬 Talk

One place to talk to every agent: select an agent and start a conversation from the Talk page
Live execution view: watch a run progress step-by-step in real time, with token usage and a context-window meter per conversation
Visual debugger: set breakpoints, step through a run node-by-node, and inspect state before/after each step
Human-in-the-loop tool approval: optionally require approval before any tool call executes, for any provider (including Claude Subscription's agentic tool use)
File & audio attachments, message editing, and conversation branching

Talk Interface

Step through a run node-by-node with the visual debugger, inspecting prep/exec state at every stop:

Visual Debugger

⏱️ Automations — Triggers

Run your flows automatically — on a schedule or when something happens — without opening the chat. FLUJO just needs to be running for triggers to fire.

Schedule: cron-style recurring runs (with second-level precision and catch-up for missed runs)
Webhook: trigger a flow via an authenticated HTTP call
File watch: fire when files change under a folder
MCP tool polling: periodically call a tool and fire on change, on new items, or let a model/checker-flow decide
URL watch: fire when a fetched page's content changes

Automation Triggers New Automation Trigger — Schedule, Webhook, File, Tool, Website, or Flow

Run history is kept per trigger, with the full output of every run one click away:

Automation Trigger Run Detail

As an example, a "watch a tool" trigger polling a WhatsApp MCP server can turn FLUJO into an autonomous auto-responder:

Meetings

Put multiple Agents into a shared conversation, so they can work on a task together

<img width="1798" height="982" alt="image" src="https://github.com/user-attachments/assets/b70cf527-743