Adoption
Engineers at major corporations and the companies on everyone's Future 500 list — the orgs betting on agentic development — already run fluidstate and Tree in daily workflows.
Teams at
Not just today's Fortune 500 — the companies redefining how software gets built. Agentic workflows, parallel agents, and architectural clarity at scale.
Engineering teams run fluidstate in CI pipelines, internal tooling, and daily dev loops. Tree pilots sit alongside existing IDEs for large-repo refactors and onboarding.
Teams report cutting sequential AI loops from hours to minutes — with clearer visibility into what agents touched and where human judgment actually matters.
The shop
Pick the interface that fits how you work. Terminal purists grab the CLI. Builders who need to see the architecture grab the IDE. Stack them together or run either on its own.
A single-binary CLI that wraps Claude Code, Codex, and your shell into parallel agent panes. Real PTYs, keyboard-driven navigation, built-in diff and approval flow — no Electron, no Node.
A desktop IDE that runs the same agent workflow but maps your repo into pages, routes, schemas, and hooks — then flashes every touched node as agents write code.
The problem
Claude Code and Codex are powerful — but a single chat tab forces sequential work. You lose track of which agent is doing what, and you never see how changes land across the codebase.
“Ask Claude to fix the bug. Wait. Ask it to write tests. Wait again. Squint at a file tree trying to remember what changed.”
Result
“Three agents run in parallel. In the terminal you see every pane. In Tree you see every node light up on the blueprint as code lands.”
Result
Workflow
Same agent engine underneath. The CLI optimizes for speed and keyboard flow. Tree adds the architectural layer on top.
curl the install script. A single Rust binary lands on your machine — no Node, no Electron, no runtime to babysit.
Each pane wraps a real agent session with its own PTY, context, and scrollback. Open focused layouts or denser grids as work grows.
Navigate files, inspect diffs, search commands, and handle permissions without dropping back into a pile of terminal tabs.
Tree scans the codebase and maps files into their architectural role — pages, routes, schemas, hooks, and the edges between them.
The graph shows how your app actually connects. Every write on disk flashes the touched node in real time as agents work.
Claude, Codex, and shell sessions run inside Tree with the same parallel workflow — but you always see where changes land.
Who it's for
Different builders need different surfaces. Pick the one that matches how you think — or run both and never lose the picture.
You want Claude Code and Codex running in parallel without leaving your shell. Spin up agents for API, UI, and tests — review and merge when they're done.
You're onboarding to a large repo or refactoring across layers. Tree shows every page, route, and schema on a live graph while agents work — so you always know what changed and where.
Install
Install one or both. They share the same agent workflow — different surfaces.
One curl command. A Rust binary — no Node, no Electron. Run fluidstate in any project directory.
Requires curl · macOS 12+ or Linux x86_64/arm64
Desktop app with the live code blueprint. DMG for macOS, installer for Windows, or install from source.
Unsigned — right-click Tree.app → Open on first launch. Or from source:
Contact
Questions about fluidstate or Tree? Reach out for access, feedback, or pilots.
© 2026 Fluid State. All rights reserved.