Skip to main content
Glama

agent-flow

Let your AI agent maintain a living flowchart of the project โ€” so you never read 10,000-word status docs again.

License: MIT MCP Node PRs Welcome

๐ŸŽฎ Live Demo ยท ไธญๆ–‡ๆ–‡ๆกฃ ยท Report Issue


The Problem

If you build projects with AI agents (Trae, Cursor, Claude Code, ...), you know this loop:

  • The agent writes 10,000-word Markdown progress docs โ€” nobody reads them

  • Half the terms it uses you don't understand, so trust erodes

  • Weeks in, the project has drifted far from the original plan and nobody knows what's done, what's broken, and what's waiting on you

agent-flow flips this: the agent maintains a single flowchart (flow.json) as it works. You open one HTML file and see everything:

  • How the project is decomposed and what connects to what

  • Which features are done, in progress, or just planned โ€” 7 color-coded states

  • Where the bugs are and which nodes are waiting for your decision

No more reading. Just look.

Related MCP server: Overboard Studio

How It Works

You โ”€โ”€talkโ”€โ”€> AI agent โ”€โ”€calls 14 MCP toolsโ”€โ”€> .flow/flow.json (single source of truth)
                                                    โ”‚
              You <โ”€โ”€open in browserโ”€โ”€ .flow/flow.html (auto-rendered, zero deps)
  1. Install once, register the MCP server in your AI tool

  2. Talk normally: "add a payment module", "we shipped the login API" โ€” the agent records it into the graph

  3. Open flow.html anytime: zoom, drag, click nodes for details, double-click modules to drill into subgraphs

Live demo (no install): wysdshg.github.io/agent-flow/demo.html โ€” drag nodes, click for details, double-click a module to enter its subgraph.

Quick Start

npm i -g agent-flow-mcp       # install the CLI + MCP server globally
npx agent-flow init           # inside YOUR project: creates .flow/ and prints MCP config
git clone https://github.com/wysdshg/agent-flow.git
cd agent-flow && npm install && npm run build && npm link

Then add the MCP server to your AI tool (Trae / Claude Desktop / Cursor / any MCP client):

{
  "mcpServers": {
    "agent-flow": {
      "command": "agent-flow",
      "args": ["mcp"]
    }
  }
}
  • Claude Code: claude mcp add agent-flow -- agent-flow mcp

  • Cursor: put the JSON above in .cursor/mcp.json

  • No MCP environment? Use the CLI fallback: agent-flow batch spec.json builds the whole graph from one JSON file and renders it.

Now just tell your agent: "Organize this project's progress into a flowchart" โ€” and keep talking to it normally while it maintains the graph.

The 7-State System

Every node carries an honest, test-backed status. The agent is instructed (via the bundled SKILL.md) to only mark completed after tests pass:

State

Color

Meaning

completed

๐ŸŸข green

done and tested

in_progress

๐Ÿ”ต light blue

being written now

planned

๐Ÿ”ท dark blue

design settled, not started

broken

๐Ÿ”ด red

has a bug

to_plan

โšช gray

raw idea, not yet planned

pending_decision

๐ŸŸก yellow

waiting for you to decide

deprecated

๐ŸŸค brown

abandoned, kept for history

Module nodes aggregate their children: all done โ†’ green; one unfinished state โ†’ that color; mixed states โ†’ the module shows all of them as color segments. Deprecated nodes are ignored โ€” dead code shouldn't raise alarms.

22 Node Types

  • Flow: start end process judge module

  • Data: database table file sql (tables auto-attach to their database)

  • AI apps: llm tool_call retrieval rerank assemble api embedding cache queue prompt agent human_loop checkpoint

module / llm / tool_call / agent / assemble support multi in/out ports. Layout is fully automatic (dagre, left-to-right) โ€” the agent never deals with coordinates.

Human-in-the-Loop Editing

Drag nodes to rearrange (saved in your browser, never pollutes the JSON the AI reads). Right-click-drag to box-select and move groups. If you change a node's state or delete it in the viewer, it generates a small ops JSON โ€” paste it back to your agent and it syncs the graph, always re-reading the latest file first.

CLI Reference

agent-flow init                 # init + print MCP config
agent-flow batch spec.json      # one-shot graph build (great for retrofitting old projects)
agent-flow apply ops.json       # run [{"tool":"add_node","args":{...}}, ...]
agent-flow render               # re-layout + refresh flow.html
agent-flow status               # progress overview (JSON)
agent-flow validate             # graph sanity check
agent-flow mcp                  # start the MCP stdio server

Why Not Mermaid / draw.io?

Mermaid

draw.io

agent-flow

AI maintains it as it codes

text diffs, merge hell

can't

โœ… 14 typed tools

Status colors (7 states)

manual

manual

โœ… built-in semantics

Human view

re-render

yes

โœ… zero-dep single HTML

Coordinates

manual

manual

โœ… automatic (dagre)

Development

npm run build   # tsc
npm test        # smoke tests (tsx)

If agent-flow saves you from doc-hell, please give it a โญ โ€” it helps other builders find it.

Related MCP Connectors

Related MCP Servers