Adoption
The vision spans planning, execution, and architecture: v2 for the product layer, fluidstate for the terminal, and Tree for the codebase map.
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 system
Start with product intent in v2, execute through fluidstate, and watch architecture move in Tree. Each product stands on its own, but the full vision is the handoff between them.
A single-binary CLI for running Claude Code, Codex, and shell sessions as parallel panes with real terminal control.
A desktop IDE that maps your repo into pages, routes, schemas, hooks, and files that light up as agents write code.
A product-facing workspace for turning goals, specs, and open decisions into scoped agent runs across fluidstate and Tree.
Connection
Agentic work breaks when product intent, terminal execution, and codebase understanding live in separate places. Fluid State connects the handoff between all three.
“Write a spec in one tool. Run agents in another. Review the diff somewhere else. Reconstruct the architecture from memory.”
Result
“v2 turns the goal into scoped work. fluidstate runs the agents. Tree shows every code path the work touches as it lands.”
Result
Workflow
v2 shapes the work, fluidstate executes it, and Tree keeps the architecture visible. Use one surface or move through the full loop.
Run the installer, open a project, and launch agent panes without adding a Node or Electron runtime to the workflow.
Give API, UI, tests, or review work to separate panes while keeping every session visible and interruptible.
Stay in the shell for diffs, permission checks, command history, and the final judgment calls before code lands.
Tree scans the project and groups files into the architectural roles that matter for real product work.
As agents edit files, the graph flashes the touched nodes so you can tell which pages, routes, and schemas are moving.
Use the map and panes together to decide where to intervene, where to review, and where the system is already coherent.
Capture the desired outcome, constraints, open questions, and acceptance checks before agents touch the repo.
Convert a broad ask into focused implementation, test, design, and review tracks that can run in parallel.
Move execution into fluidstate for speed, Tree for architecture-heavy work, or both when the job needs multiple views.
Who it's for
The main page is the vision. The individual pages are the details: planning, terminal execution, and architectural visibility.
For builders who already live in the terminal and want agentic work to feel native instead of bolted onto a chat window.
Open page→For teams navigating larger codebases, refactors, onboarding, and any agent run where a flat file tree hides too much context.
Open page→For founders, product-minded engineers, and teams that need to preserve intent while agents handle more implementation surface area.
Open page→Install
Download all three directly. v2 now sits alongside fluidstate and Tree as an installable surface for agentic planning and execution handoff.
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:
Download v2 directly from the latest fs-code release. If the latest tag is not available, the links fall back to the releases page.
Direct download
Grab the latest release archive for your platform.
Uses the latest fs-code release tag when available.
Contact
Questions about fluidstate, Tree, or v2? Reach out for access, feedback, or pilots.
© 2026 Fluid State. All rights reserved.