Vibe graphing IDE · an agentic graph engineering loop · free
Teams · MCP · web apps · X-ray · Sagas · coming soon for Windows, Linux and macOS

VIBE GRAPHING

antiloki is an agentic graph engineering loop IDE. Your Leader drafts the team as a graph of agents, tools, checks and gates; you edit the board, set the budget and run it on the AI subscriptions you already have. Free: no account, no trial clock, no API key to paste.

Coming soon
scroll
one binary · no account · your current subscription is the engine
vibe graphing

A team is a graph. Watch one get drawn, and run.

Scroll. The Leader drafts a team as a graph, the circuit lifts off the plane as it runs, the branches fan out, a loop runs until its check passes, and nothing ships until you say so.

Leaderclaude · opus⋯

youlaunch a landing page: two designers' takes, a copywriter, a contrast check, and I approve before anything ships.

● leaderDrafting the team as a graph: a planner, two designers, a copywriter, a contrast check, QA and a gate.

● leaderEvery node is a real step: an agent, a tool, a fork, a check, a gate.

● leaderForks run side by side. Each node records its seat, model, time and cost.

● leaderA loop runs until its check passes, under a max count and a cost cap.

● leaderQA reviews the work. Nothing ships until you say so.

● leaderApproved, and delivered. Draw the team. Run the loop. Read the receipts.

❯
launch-a-landing-pageRunEditSagaspent $0.00 of $1.00
LEADER opus Leader your terminal queuedrunningdone AGENT sonnet Planner splits the page queuedrunningdone $0.02 FORK Fork branches at once queuedrunningdone TOOL 2 tools Web search search + fetch queuedrunningdone AGENT gpt Designer layout, type scale queuedrunningdone $0.03 AGENT sonnet Copywriter headline, body, CTA queuedrunningdone $0.02 JOIN Join waits for all queuedrunningdone IF Contrast ok? routes on the result queuedrunningdone QA gemini QA fresh context queuedrunningdone $0.04 GATE You approve your yes or no queuedrunningdone DELIVER Deliver page + report queuedrunningdone

X-ray launch-a-landing-page · example

♥ 82 health⚠ 18 risk▤ 214 files⚗ 61% coverage◉ 34% solo-owned⛨ 0 vulnerable deps
Health over time
health and risk per snapshot · last 12
7080
Hotspots
x: gravity (how much code leans on it) · y: churn (how often it changes) · colour: health
The codebase
every file is a box · area = mass · colour = the lens
graph/run.ts58
graph/board.tsx63
ui/panes.tsx49
store/sync.ts66
store/db.ts81
api/routes.ts86
auth.ts72
render.ts94
router.ts88
cli/main.ts70
legacy/mail.js31
util/time.ts98
ui/theme.ts91
store/migrate.ts77
Laws broken most
mass = violations, weighted by the law
no import cycles9
one owner per module6
no file over 800 lines4
every API route tested2
Movers since the previous snapshot
files whose health moved the most
graph/run.ts76 → 64-12
api/routes.ts79 → 86+7
legacy/mail.js40 → 31-9

Sagas 4

in progress 1
onboarding emails7/9$0.062m
todo 1
pricing page copy0/6—1h
failed 1
weekly changelog4/5$0.0318m
done 1
launch-a-landing-page11/11$0.114m
waiting for younodes 0/11passes –
L

LeaderYour terminal agent. Designs the team with you. Exactly one per graph.

A

AgentPlanner, worker, QA, debugger, audit, or your own agent with its own brief.

T

ToolWeb search and page reading, and this app's own tools, each with an allow-list the node must name.

F

Fork and joinBranches run side by side. The join waits for all, or for a quorum.

?

If and switchRoute on what a node said. A switch needs a default port.

O

LoopRepeat until a condition holds. It needs a max count and a cost cap.

E

For eachOne branch per item, in parallel up to a limit you set.

R

RetrySend a failed node round again, then take the exhausted port.

G

Gate and cost capA human gate waits for your yes or no. Any node can carry a cost cap.

D

Artifact and deliverThe documents a run makes, and the end of the graph: the pack reaches you.

teams and mcp

Teams are graphs. Antiloki is an MCP server.

A team is a graph you can see and edit. Antiloki also speaks MCP, so the tools you already use can drive it: its threads and panes, its sagas, its X-ray and its teams.

T

Teams, drawnThe Leader designs the team with you on the board. A driver runs it node by node, under its budget.

S

Skills, proposedAgents propose changes to their skills as drafts. Nothing changes until you approve it.

A

ArtifactsThe documents a run produces, such as a report or a draft. The next node reads them, and you can open them.

M

MCPAn MCP client can open threads and panes, read and add sagas, rebuild and open the X-ray, and design and run teams (antiloki_team_design, antiloki_team_status, antiloki_sagas, antiloki_xray).

compared with the tools alone

On top of the tools you already use.

antiloki runs Claude Code, Cursor, Codex, Gemini and Grok. It does not replace them.

what you wantthe tools alonewith antiloki
TeamsOne agent in one chatA team drawn as a graph: planner, workers, QA and gates, edited on the board and run in a loop
ToolsEach tool's own built-in toolsWeb search and page reading as nodes, and an MCP server, each with an allow-list the node must name
Web appsA browser tab, when you need itWeb apps open in their own pane, from a store, beside your agents
Parallel workTerminals side by side, you keep trackReal terminals in Cowork panes; each thread gets its own git branch and worktree
Where the work livesA to-do list inside one session, gone when it endsSagas: a list per project of goals, tasks and runs, for you and your agents
Who did whatScroll back through a chat to find outEvery node records its agent, exact model, time and cost, in order
Your codebaseThe agent reads your repo cold, every timeThe X-ray: a health view with a codebase map, hotspots, laws broken and what moved since the last snapshot
BoundariesPermissions and a sandbox you set upEach node writes only inside its folders; a commit or a publish waits at a gate for your yes
BudgetEach tool's own usage pageA cost cap on every loop and on any node; a run stops at its budget
The recordWhatever the chat keptA finished saga stays: it cannot be canceled or deleted, so the history is the history

Coming soon for Windows, Linux and macOS. The docs cover every screen: read the docs →

Free.

No trial clock. No paid tier. No account.

antiloki is free to use, read and change. It runs on the subscriptions you already pay your model vendors, so the only bill is theirs.

Use it
$0forever
  • everything — the graph board, teams, Cowork, Sagas, the X-ray and MCP
  • no card, no account, no trial to run out
  • your projects stay on your machine
Coming soon
Read it
soonsource
  • the source is coming, to be published under an open-source license
  • read how the graph runs, change it, send a fix back
  • the team and graph format is in the docs →

antiloki is free. Model subscriptions and API keys are billed by their own vendors, not by antiloki.

Coming soon.

antiloki is not downloadable yet.

What is antiloki?

A free vibe graphing IDE. You describe the work in plain words, the Leader drafts a team as a graph of agents, tools, checks and gates, you edit it on the board, and the loop runs it on the AI subscriptions you already have. Antiloki is also an MCP server, so the tools you use can drive its threads, sagas, X-ray and teams.

What is vibe graphing?

Describing the work in plain words and getting a graph back: the Leader drafts a team as nodes and edges (agents, tools, forks and joins, checks, loops, gates), you edit it on the board, and the loop runs it under the budget you set. Every node is visible while it works and is recorded afterwards, so the graph is both the plan and the proof of what ran.

What are the nodes of a graph?

A graph is built from nodes you can see, edit and run: the Leader (your terminal agent, exactly one per graph); agents (a planner, worker, QA, debugger, audit, or your own agent with its own brief and tools); tools (web search and page reading, and this app's own tools, each with an allow-list); fork and join to run branches side by side; if and switch to route on a result; loops with a max count and a cost cap; for-each, retry, a human gate that waits for your yes or no, artifacts (documents the run makes) and deliver.

How does a run stay within budget?

Every loop needs a max count and a cost cap, and any node can carry its own cost cap. A run is stopped when it reaches its budget. Every node records its agent, exact model, time and cost, in order, on the saga.

What are teams?

A team is a graph you draw and edit. The Leader designs it with you, a driver runs it node by node, and each run leaves artifacts (documents the next node reads and you can open). Agents can propose changes to their skills, but as drafts: nothing changes until you approve it.

Is antiloki an MCP server?

Yes. An MCP client such as Claude Code can open threads and panes, read and add sagas, rebuild and open the X-ray, and design and run teams through antiloki's MCP tools (for example antiloki_team_design, antiloki_sagas and antiloki_xray). A node in a graph can use only the tools it names.

What is the Cowork screen?

Your agents' real terminals, side by side in panes, with the Leader and the team's graph beside them. Web apps open in their own pane from a store. Threads give each line of work its own git branch and worktree, so agents can work on different things at once and land them when you say.

What are Sagas?

A list per project of goals, tasks and their runs. A saga keeps who did each step, the exact model, the time and the cost, and a finished saga stays on the record.

What is the X-ray?

The X-ray is a health view of your repo: a verdict row (health, risk, coverage, solo-owned files, vulnerable dependencies), health over time, hotspots by gravity and churn, a codebase map that colours every file by the lens you pick (health, cascade, ownership, debt, heat or runtime coverage), the laws broken most, and what moved since the last snapshot. The chat sees all of it, so "why is this file 81?" gets a real answer.

Are web apps supported?

Yes. Web apps open in their own pane from a store, next to your agents. A graph can also use the web node, which searches the web and reads a page for the agent that asked.

Is it really free? What is the catch?

There is no catch in antiloki: no paid tier, no trial that ends, no account. The only costs are the model subscriptions or API keys you choose to use, and those are billed by their vendors. We plan to publish the source, so you can check that nothing is hidden.

Does it replace Claude Code, Codex, Cursor, Gemini or Grok?

No — it runs them, twice over: as the agent in its box, and as the engine behind antiloki's own AI (the chat, the reviews, the ultra review), each through its own vendor CLI. Keep your subscriptions; there is no API key to paste.

Can an agent change my files without asking?

No. An agent can only write inside the folders its node is allowed to touch. Anything that leaves the project, such as a commit to your branch or a publish, waits at a gate for your yes or no.

Do I need two subscriptions?

No. One subscription is enough: antiloki runs on whichever CLI you are signed in to. A team can use more than one seat, a planner on one and workers on another, if you have them. It only offers a provider you are actually signed in to: it reads the seat, not the installed binary.

Isn't this just worktrees and tmux?

Worktrees are the easy part. The fence enforced where the work lands, the gate before anything leaves the project, the sagas that keep the record, the X-ray that knows the repo, and the cost-per-run record are what you can't script in an afternoon.

Can my company install it?

One binary, local, no account, no telemetry. The network calls are: your CLIs' own calls; an update check against a static file on GitHub Releases; the window's fonts, fetched from Google Fonts (fonts.googleapis.com and fonts.gstatic.com) when it opens; api.openai.com or openrouter.ai only if you set up the optional OpenCode route with your own key; and GitHub only if you add a token or open a pull request. Send that to security.