agent-graph-flow
DashboardPremium · ... leftv0.22.3 · available

Stigmergy · deliver software with the power of nature

Ants don't
have a CEO.

They carry leaves. Leave pheromone trails. The entire system evolves on its own, no alignment meeting, no roadmap, no central orchestrator.

This is stigmergy: intelligence that emerges from the trail each agent leaves behind.

agf (agent-graph-flow) is an open-source CLI that orchestrates AI coding agents using stigmergy — each cycle deposits pheromone that biases the next, so the system improves without a central orchestrator. It runs locally: no Docker, no mandatory cloud.

local-first · no docker · 5 platforms

Apache-2.0 · open forever · auditable in any environment

The analogy

A colony learns without any single ant knowing the whole.

EPICtasktasktasktasktaskDONEagent-graph-flowa living graph · pheromone trails · the colony finds the optimal pathstrong trail — the route the colony reinforced (ACO)weak edge — a path still being exploredepic · task · done — nodes of the persistent graph
Each ant carries a task and lays down pheromone; the colony converges on the EPIC → task → task → DONE path with no central orchestrator. The gray edges are routes still being explored.
⌖ in the forest
  • 01An ant finds the shortest path to food.
  • 02Leaves pheromone — a trail of context for those who follow.
  • 03Others reinforce, refine, improve the path.
  • 04The colony learns on its own, without a central orchestrator.
$ in agf
  • 01An agent executes a task and leaves a trail of context.
  • 02The graph learns what worked and calibrates the next cycle.
  • 03Each project reinforces the patterns of the previous ones.
  • 04The system delivers faster, without anyone knowing everything.

We didn't build a tool that thinks for you. We built one that learns with you, cycle by cycle.

What agf is

You describe what you want.
The graph makes it happen in cycles.

agent-graph-flow is a local-first CLI for AI agent orchestration. A text request becomes a persistent execution graph that runs an autonomous cycle with guardrails.

Mandatory TDD. One task at a time. Each call is measured in tokens, so the cost stays low and predictable.

SHAPEdecomposes the epic into atomic, testable tasks on the graph.
BUILDRED → GREEN → REFACTOR. No line without a failing test first.
SHIPDefinition of Done validates. Pheromone deposited. Next cycle calibrated.
the cycle restarts, and each turn grows stronger than the last

v0.22.3 · release highlights

The leafcutter ant technique.

This version replicates the behavior of Atta: pheromone is used adaptively. Efficient trails are reinforced; inefficient ones evaporate naturally.

reinforcement · τ ↑

Each success deposits pheromone

Δτ = Q/L. What worked cheaply and well becomes the most likely trail.

evaporation · ρ ↓

Every trail loses strength each cycle

ρ = 0.10. Obsolete patterns disappear on their own, without lock-in.

exploration · q₀

70% exploits the best trail

30% tries new paths. The colony never gets stuck on the first local optimum.

And an identity guided by an honest principle: no humanwashing. agf doesn't think, doesn't feel, isn't "intelligent" in the human sense. It replicates an algorithm from nature and does exactly what it promises.

01

Real speed

Automatic decomposition of epics into atomic, parallelisable tasks. What would take weeks, the graph delivers in cycles.

02

Quality without overhead

TDD built into the flow. Each cycle passes through Definition of Done. No task advances without evidence.

03

Memory across projects

agf learns patterns from your history. The next project starts with the accumulated knowledge from all previous ones.

Local-first · one command

No Docker. No mandatory cloud. Runs on your machine.

All output is a single-line minified JSON, made to be read by another AI. Each command prints its own cost in tokens.

WindowsmacOSLinuxoffline · self-contained

Install once. Use offline. No external dependencies beyond the agent itself.

agf · bash
# one request, full pipeline $ agf deliver "login com e-mail + testes" ↳ shape · 6 atomic tasks on the graph ↳ build · RED → GREEN → REFACTOR ↳ ship · DoD ✓ · pheromone deposited $ agf stats --select data.byStatus {ok:true,data:{done:6,pending:0},meta:{tokens:1840}} $ agf savings

Install in seconds · single binary

Download agf

One self-contained binary per OS — no Node, no npm, no Docker. Download and run.

macOS

Install with one command:

Linux

Install with one command:

Windows

Install with one command:

macOS: the binary is unsigned — the installer clears the quarantine attribute automatically. When downloading manually, verify the checksum (.sha256).

Quickstart after download

1. Make it executable
macOSchmod +x agf-darwin-arm64
Linuxchmod +x agf-linux-x64
WindowsNo extra step — .exe runs directly
2. Verify the checksumshasum -a 256 agf-darwin-arm64Compare the output with the .sha256 file from the release.
3. Run your first command./agf --versionPrints version + token cost. Then try: ./agf shape "your first request"
4. Add to your projectAdd agf to CLAUDE.md, or clone the skills repository into .agents/skills/ — the agent triggers each skill by name.agf shape "build a REST API for todos"

The 3 graphs — and only 3

Nature’s technique, in 3 moves

Three skills cover the whole cycle: plan, build, harden. Each mirrors a master from nature.

PLAN

Rufous hornero (João-de-barro)

graph-backlog-generation

The architect bird builds a meticulously planned mud nest before laying its first egg. The backlog graph does the same: it turns an idea into a PRD and a graph of atomic tasks with testable criteria — structure before a single line of code.

BUILD

Leafcutter ant

graph-builder-leafcutter

The colony cuts leaf by leaf, in line, never stopping, cultivating the fungus that feeds them all. The builder graph pulls task by task (WIP=1), implements with TDD (RED→GREEN→REFACTOR) and deposits what it learns — until the backlog is exhausted.

HARDEN

Woodpecker

graph-woodpecker

The woodpecker drums the trunk to find what is hollow and rotten inside. The woodpecker graph hunts bugs, vulnerabilities and debt, and proves every fix with a regression test — toward ≥80% coverage.

How to configure it in your project

  1. Clone the skills repository into .agents/skills/ (project) or ~/.claude/skills/ (global).
  2. Keep the zip structure: it already ships _shared.md, the protocols (_pilot/_rag) and each skill’s references/ folder — everything the 3 need.
  3. Done: the agent triggers each skill by name (graph-backlog-generation, graph-builder-leafcutter, graph-woodpecker).

The visual dashboard

The agf dashboard, explained in plain words

When you run the agf dashboard command, your browser opens a panel with two screens: the Graph (the map of the work) and the Economy (how much you saved). Here is every item explained simply — no jargon.

Screen 1 · Graphagf dashboard — Graph panel

The map of everything the project has to do. Each little box is a unit of work; the lines show what depends on what.

  1. Project scoreboard (2323/3770 done)

    At the top, progress in a single number: 2,323 of 3,770 tasks already finished. The fastest way to know 'how much is left'.

  2. Search nodes

    Type a word and the panel finds the task by name, with no need to scroll the whole map. Great for finding something instantly.

  3. Filters

    Shows only what matters — e.g. just what's in progress, only the bugs, or a single owner's work. Use it to focus and cut the noise.

  4. Dagre / ELK

    Two ways to lay out the map automatically. If a layout looks cluttered, switch between them until it reads clearly — it's just a visual preference.

  5. Expand / Collapse

    Opens or closes the details (the subtasks) of each box. Start everything collapsed to see the big picture, then open only what you're examining.

  6. Tree / Table

    Swaps the visual map for a hierarchical list (Tree) or a spreadsheet (Table). For people who prefer reading a list over a diagram.

  7. The boxes (the nodes)

    Each box is a unit of work. The colored tag tells the type: EPIC (a big goal), TASK (one task), or REQUIREMENT (a rule). The green 'done' badge means completed.

  8. The lines between boxes

    They show the links: what depends on what, and what is part of what. Following the lines is how you understand the order the work must happen in.

  9. Zoom and corner buttons (+ / −)

    Zoom in, out, and recenter the map. Essential for navigating large projects without getting lost.

Screen 2 · Economyagf dashboard — Economy panel

How much the agf saved you on AI cost. The core idea: send little text to the model, reuse whatever it can, and keep everything measured.

  1. Saved ($)

    How much money you avoided spending on AI calls. '99% savings rate' means: for every $1 you'd normally spend, the agf avoided 99 cents.

  2. Delegate Savings

    The biggest saving comes from 'delegate mode': instead of sending the whole project to the AI, the agf sends only a lean summary. The number beside it (e.g. 11,652) is how many times that happened.

  3. Cache Hit Rate

    How many answers were reused from local memory instead of calling the AI again. 0% here is expected: in delegate mode it's your agent — not the agf — that calls the model.

  4. Tokens Saved

    Tokens are the little chunks of text the AI charges for. This number is the tokens that were NOT sent to the model — fewer tokens, smaller bill.

  5. Spent ($)

    How much the agf spent directly on AI. Usually zero because, in delegate mode, it's your own agent that pays for the calls — the agf just organizes and saves.

  6. Delegate Economy (the green bar)

    Shows visually how much was sent (emitted) versus how much was saved, compared to sending the whole 'raw graph' (baseline). Almost the entire bar is savings. Below it: average savings, number of calls, average size sent, how much data was avoided, and the average response speed.

  7. Local Cache

    The local memory of answers. It only fills up when you use an AI provider with the --live option. That's why it shows empty in delegate mode — and the panel explains that right on screen, never leaving you in the dark.

  8. Savings by Lever

    The 'levers' are automatic reuse techniques that are switched on, and how much each one saved. In the example, rag_out_recovery saved 900 tokens across 7 uses and rag_in_reuse 720 tokens across 33 uses. You do nothing: they act on their own and everything is logged.

All of this is local and runs on your machine — the panel reads your own project's graph. Run agf dashboard and explore.

Token economy

The edge nobody shows you: the cost.

Output costs 3–5× the input — and input is cacheable. agf attacks the dominant spend right at the gateway, without being asked. Every saving is recorded and auditable.

3–5×what output costs vs. cacheable input

Diff edits

Rewrites only the changed region of a file, never the whole file. Generation is the dominant cost — agf generates the minimum.

Ranked repo map

A PageRank-prioritised repository map in ~1k tokens, instead of dumping the entire tree into context.

Reversible CCR

Cold content becomes a cached ⟨ccr:hash⟩ marker, recoverable on demand with agf retrieve. Lossless compression.

Command-boundary compression

Shell output compressed before the agent reads it — automatic, via hook. Every saved token lands in the ledger.

No promises, just numbers. Every call goes to the llm_call_ledger — audit it with agf savings and agf metrics.

AI enterprise software

The revolution has begun

Join this new revolution in AI-driven enterprise software development.

Leave your email to follow the evolution.

FAQ

What is agf?

agf (agent-graph-flow) is an open-source CLI that orchestrates AI coding agents using stigmergy: each cycle deposits pheromone that biases the next, so quality and speed compound without a central orchestrator.

How does stigmergy speed up agents?

Every success deposits pheromone on a trail and every trail decays each cycle; the next run exploits the strongest trails (~70%) while still exploring (~30%), so the colony reuses what worked instead of re-deriving it.

Does agf need the cloud or Docker?

No. agf is local-first — it runs on your machine with no Docker and no mandatory cloud, across macOS, Linux and Windows.