Flow Console
We brought HPC cache coherence to AI agents.
Where coordination bites. Run multiple coding agents across teammates and machines on the AI provider you already pay for—like Claude Code—inside an active orchestration harness with shared agent-paced memory and zero merge collisions.
Cost over 40 Sonnet 5.5 coding requests ($9.78 → $5.13)
Cost over 39 Haiku 5.5 coding requests
Peak context window reduction in long coding sessions
Failed merges across 8 coordinated agents
The Pain Point, Our Solution, and Why Metantel.
Agents working alone burn tokens and break each other’s code
In solo coding sessions, Claude Code re-reads the whole conversation on every turn, spiking context to 313K tokens. Across a team, two agents editing related code on two laptops only discover the collision at git merge—requiring human rework.
An active orchestration harness: MOESI cache coherence + EDIP memory
Connect a harness, not a passive tool. Flow Console gives each agent an isolated git worktree, feeds judged project context in rounds via the EDIP Librarian Harness, and coordinates parallel edits using CPU-inspired MOESI cache coherence. Overlaps are settled by intent before the edit happens.
Compounding token savings and conflict-free shipping on your existing AI bill
You bring the Claude Code subscription you already pay for. By request 21–40 in a session, Flow Console + EDIP cuts token cost by 63% (−47% overall), while turning high-performing sessions into reusable AI Workers.
Cut long-session token usage by 47% on Sonnet 5.5 and 74% on Haiku 5.5. Reopen any session, steer mid-task, and graduate your best sessions into persistent AI Workers.
See every teammate’s active agents, their intent, and uncommitted changes on the same function before your agent edits. Agents message each other across machines.
Zero new LLM inference vendor to approve—runs on your existing Claude Code licences while enforcing org-scoped memory via EDIP.
A Lock Says Stop. Coherence Says Keep Working.
Traditional multi-agent setups either let agents overwrite each other until a broken PR merge, or slap coarse file locks on the repository that force agents to sit in a queue and give up half their throughput.
Flow Console brings High-Performance Computing (HPC) MOESI cache coherence to software engineering. Every agent runs in its own git worktree and shares a live intent layer. When two agents touch different functions, neither stops. When two agents reach the exact same function on the same branch, the second agent receives the first agent’s live intent and uncommitted diff before making its edit—building on the change instead of colliding with it.
How Flow Console Changes Day-to-Day Engineering
- Conflicts settled while agents work: overlaps surface before the edit, not in code review. People step in only when agents disagree.
- Compounding session savings: EDIP keeps active context small (117K peak vs 313K), saving 19% in the first 20 requests and 63% in requests 21–40.
- Graduate sessions into AI Workers: turn a well-calibrated session into a persistent worker whose experience carries into future tasks.
- Full mid-task steering: change the model, adjust thinking depth, message an agent mid-run, or inspect the live multi-agent dependency map.
- No new AI bill: drives the Claude Code installation and subscription your team already pays for—connecting full harnesses, not just stateless MCP tools.
Measured in Real 40-Request Coding Sessions
Tested side-by-side on the same machine, repository, model, and 40 real coding requests (features, bug fixes, refactors, tests, and docs): Claude Code alone cost $9.78 and hit 313K peak context; with Flow Console + EDIP (including EDIP’s own cost), the session cost $5.13 and peaked at 117K context. All 8 of 8 short 5-request sessions were also net cheaper (−16%).
How Flow Console connects to the Metantel stack
Every Metantel product shares one underlying memory and governance layer. Context, verification proofs, and access rules flow between tools automatically.
Serves judged, multi-hop codebase and organizational evidence in rounds so Flow Console agents stop grepping blind.
Explore EDIP →Browser QA verdicts and network proofs flow directly back into Flow Console so coding agents fix real defects.
Explore Artel QA →Monitor, steer, or queue Flow Console agent runs remotely from your phone.
Explore Elenchus →