Flow Console

One web app for your coding agents. It runs on your machine and drives the agent you already pay for, such as Claude Code. Each agent gets memory it shares across sessions, machines and teammates, and agents working in parallel see each other's intent before they edit.

i

Current version: 0.4.15. It updates itself; see Updates.

Install and first run

  1. Have Node.js 20 or newer

    Check with node --version. If it is missing or older, install the LTS from nodejs.org, or with Homebrew:

    brew install node
  2. Install Flow Console

    Open Terminal and run:

    npm install -g metantel-cli

    If npm answers EACCES, your Node is a system install: use Homebrew's Node or nvm rather than sudo.

  3. Open it in your project
    cd ~/code/your-project
    metantel flow-console

    Your browser opens on 127.0.0.1. Sign in with Google or a code we email you, and Flow Console opens that folder.

Try it without installing: npx metantel-cli flow-console

Your agent: sign in to Claude Code once in a terminal and Flow Console drives it on your own subscription. Codex, Antigravity CLI, GitHub Copilot CLI, Cursor CLI, Grok Build and opencode work the same way. No agent installed? Use Metantel's models, paid from usage credits.

Works with
macOS12 Monterey or newer, Apple silicon (M1 to M4). Intel Macs are not supported.
WindowsWindows 10 and 11, 64-bit (x64). Tested on Windows Server 2022. Windows on Arm is not supported.
Node.js20 or newer. Tested from Node 20.20 to Node 25.8.
npm9 or newer. Tested with npm 9.9, 10, 11 and 12.2.
BrowserAny current Chrome, Edge, Safari, Firefox or Arc.

The first run, step by step

  1. Sign in. Use Google, or type your email and enter the six-digit code we send. It is the same Metantel account as metantel.com and Artel, and it stays signed in on this machine.
  2. Choose a plan if you have not yet, on metantel.com/pricing. Free is enough to start. Your plan shows at the top right of every page.
  3. Open a folder. The folder you started from opens by itself. Otherwise type a path, pick a recent folder, or browse.
  4. Pick an agent and a model from the menu in a new session: Claude Code, another agent you have installed, or a Metantel model.
  5. Describe the task in plain words and send it. You can watch every step and file change, and steer the agent mid-task.

Requirements

SystemmacOS 12 or newer on Apple silicon; Windows 10 or 11, 64-bit
Node.js / npmNode 20 or newer with npm 9 or newer, needed only to install and launch. Flow Console itself is a native program.
A coding agentClaude Code, signed in, for most people. Optional: Codex, Antigravity CLI, GitHub Copilot CLI, Cursor CLI, Grok Build, opencode. Or none, with Metantel models on usage credits.
NetworkAccess to api.metantel.com for sign-in, memory and updates. Your agent talks to its own provider as usual.
DiskAbout 40 MB for the program, plus your sessions and a week of logs in your home folder

Agents and models

Flow Console drives coding agents rather than replacing them. The agent menu lists every agent found on your machine, and what each needs before it can run.

  • Claude Code runs on your own Claude subscription or API key, exactly as it does in a terminal. Flow Console adds the memory, the session view, and coordination with your other agents.
  • Other coding agents are on by default: Codex, Antigravity CLI, GitHub Copilot CLI, Cursor CLI, Grok Build and opencode, each on your own subscription. Flow Console shows each agent's own modes, models, settings and slash commands, and its approval requests. Memory reaches them with each message. Pre-edit coordination is Claude Code only for now. You can turn other agents off in Settings → Agents.
  • Metantel models are hosted by Metantel and paid from usage credits. Each shows its price per million input and output tokens under its name. They include open models from NVIDIA (Nemotron), Meta (Llama) and Google (Gemma), plus Gemini Pro.

Memory

Every folder is connected to a space, a memory your agents read from and write to. What one session works out, the next session can use, whichever agent runs it and whichever machine it is on. Teammates in the same space share it.

  • Memory is served at the agent's pace. The agent asks for what the task needs, in rounds, and is told what is left, so it doesn't re-read whole files on every turn.
  • A new folder gets a space of its own automatically. You can connect it to an existing space, or make a new one, from the Artel page inside Flow Console.
  • At a task's end the context is made lean again, so long sessions stay fast and cheap.

Folders and tabs

Each folder opens in a browser tab of its own, with its own agents. Choose another folder from the folder name at the top: if a tab already has that folder open, it comes to the front; otherwise a new tab opens for it. Agents in one tab never act in another tab's folder.

AI Workers

When a session has done good work, choose Graduate to AI Worker. The worker keeps what it learned and can be set to work in any folder, on any machine where you are signed in.

Working as a team

When several agents work on one repository, on one machine or on teammates' machines, Flow Console uses an approach inspired by CPU cache coherence:

  • each agent knows who else is working, on what, and why;
  • an agent about to edit code another agent is changing sees that agent's intent and uncommitted change first, and builds on it instead of colliding with it;
  • agents can message each other to settle an interface mid-task, and you only step in when they disagree;
  • each session can work in its own git worktree.

Decisions that need a person show on the Agents page, and as a notice wherever you are.

Plans and credits

Your plan covers memory, metered four ways: tokens ingested, tokens served, queries and storage. Metantel models and memory use beyond the Individual allowance are paid from usage credits. The full table is in Plans, usage and credits.

Commands

metantel flow-consoleOpen Flow Console in this folder (also metantel fc)
metantel flow-console --no-openPrint the address instead of opening the browser
metantel flow-console --port 7600Use a fixed port
metantel supportSend a problem report with Flow Console's logs, after showing you every file it includes
metantel updateInstall the newest version now
npx metantel-cli flow-consoleRun without installing

Every command is in Metantel CLI.

Updates

Updates are on by default. About once an hour Flow Console checks for a newer version, and an open console shows Restart to update; it comes back at the same address. A global install updates itself the next time it starts, and npx runs the newest version. Set METANTEL_NO_UPDATE=1 to turn updates off; they are off under CI.

Your data

  • Flow Console runs on your machine and answers only to 127.0.0.1, behind a key made fresh at each launch.
  • Your agent's requests go to its own provider, on your subscription, as they would without Flow Console.
  • What your sessions teach is stored in your memory space, so your agents and your space's members can use it. Secrets are scrubbed before storage.
  • Settings, sessions and a week of logs stay in ~/.flow-console-neo (on Windows, %USERPROFILE%\.flow-console-neo). Logs leave your machine only in a problem report you choose to send.

Technical specs

ProgramNative, compiled in Rust; one binary for the engine and the web app
Package~12–13 MB from npm (metantel-cli), one per platform
InterfaceLocal web app on 127.0.0.1; host and origin checks; a fresh key each launch
AgentsClaude Code plus six others through the Agent Client Protocol; Metantel models streamed
MemoryAgent-paced, served in rounds; spaces shared across sessions, machines and teammates
CoordinationIntent shared before an edit, cache-coherence-inspired; per-session git worktrees
FoldersOne console per folder, each in its own browser tab
LogsOne file a day, kept 7 days, capped at 20 MB a day

Measured

In coding sessions

Cost over 40 coding requests, Claude Sonnet−47% ($9.78 → $5.13); −63% on requests 21–40
Cost over 39 coding requests, Claude Haiku−74%
Peak context in long sessions313K → 117K tokens
Failed merges, 8 coordinated agents (simulation)0 of 132,920

The memory layer on public long-memory benchmarks

↑

The more there is to remember, the further ahead it pulls. At 10 million tokens of memory, the heaviest BEAM test, it scores 53.7% against Mem0's 48.6%. On LongMemEval-M it scores 80.8%, 8.8 points above the benchmark paper's best pipeline.

BenchmarkMemory sizeQuestionsMetantelCompared withGraded by
BEAM, 10M tokens10 conversations, ~110M tokens20053.7%Mem0: 48.6%gpt-4.1-mini, BEAM's own prompt and scoring
BEAM, 1M tokens35 conversations, ~38M tokens70060.4%Mem0: 64.1%gpt-4.1-mini, BEAM's own prompt and scoring
LongMemEval-M~500 sessions per question (129M tokens in all)50080.8%Paper's best pipeline: 72.0%GPT-4o, the benchmark's own judge
LongMemEval-Mthe same answers50082.0%GPT-5.4

Measured 1–2 November 2026 with one memory recall per question and one answer. Mem0's scores are their own, by a method not published in full; ours use each benchmark's own code and judge.

Troubleshooting

metantel: command not found
npm's global folder is not on your PATH. Run npm prefix -g and add its bin folder (on Windows, the folder itself) to PATH, or use npx metantel-cli flow-console.
Claude Code shows "Not signed in"
Run claude once in a terminal and log in, then choose Check again in Settings → Agents.
The browser did not open
Open the address Flow Console prints in the terminal. --no-open always prints it.
Sign-in does not finish
Use Email me a code instead of Google. If that fails too, choose Report a problem on the sign-in screen.
Metantel models are locked
They are paid from usage credits. Buy credits and they open within a minute.
Anything else
Settings → Help → Report a problem, or metantel support. Or talk to the developers.