STARTER · TEAMMATES
Grok Bot–style proactive team
Teammates that work in the background on schedules and triggers, and check in when they need you.
Harness your AI workforce.
Build your own harness, from one agent to a whole workforce, shaped to how your team works, on any model, at a cost you control.
Your own harness, from one agent to a whole workforce, on any model, at a cost you control.
Or add it to an app you have
pnpm add @flow-state-dev/core @flow-state-dev/engine zod
Today's harness is someone else's product.
Claude Code, Codex and Grok Bot are impressive, sub-agents and all. But you work inside their UX, on their models, with their memory, and you wait for them to ship the feature you need. There's no deterministic step and no hybrid flow. Customizing them means adding extensions like skills, and each one usually means more token spend.
Own it
Stop renting your AI harness.
Anyone can build software now. So why rent your company's work OS from the AI labs that already sell you the model? Subscriptions hide what it really costs. Fit the system to your process instead, on software you own, and control both the cost and the workflow.
Own it, without starting from scratch. Flow State is open, pluggable and remixable, and it sits on a foundation that keeps getting better. Upgrades and new features ship to everyone who builds on it, and every change you make stays yours.
01
The best model changes every few weeks.
Switch per block or per task the day a better one ships.
02
Your data stays in systems you run.
The layer that reads every document should be one you control.
03
Pay for intelligence only where it earns it.
Deterministic steps run as code. Models and agents run where they make the difference.
Start from a working app, not a blank page.
2 starters · 1 backendPick the experience closest to what you're building and make it yours. Every app here runs on the same backend; only the UI is different.
STARTER · AGENT
Claude Code–style agent
One conversation driving an agent loop, with sub-agents for parallel work and approvals in line, on any provider's model.
COMING SOON · SHIFT MANAGER
A workforce that runs overnight
Make the decisions during the day shift; the fleet runs overnight, and any calls it had to make itself are ready for review in the morning. Built on the same backend as the starters.
Your flow fits your process.
Build the process as a graph and choose what runs each step: plain code where the work is deterministic, a small model where it's cheap, a full agent like Claude Code only where it earns its cost, and a person where it matters. Bring the subscriptions you already have.
A workforce is many flows, working together.
Each flow becomes a worker you can assign. Workers share a task board, state and memory in your own stores, message each other, and bring questions to you and the people you work with. Run it locally or in the cloud, for one person, a team, or many orgs.
What you could build first.
-
01Your company
Runs your process, not a vendor's.
Ops, support and engineering work runs on loops that follow how your company works.
→ ops · support · engineering -
02Your users
Built for your users, not just your team.
Put a Claude Code–style agent inside your own product, on any model. Your users get an agent built for their work. The data and the margins stay yours.
→ your product · your users -
03Engineering teams
One board over every coding agent.
Route work across Claude Code, Codex and Cursor from one board, with checks before anything lands and budgets that hold.
→ claude code · codex · cursor
It runs out of the box. Change it when you need to.
Flows · blocksMost of the time you won't touch the backend. When your product needs something different, configure a ready-made block, write a custom flow, or turn any flow into a worker. Nothing is a fixed slot. And because it's all built on the same foundation, you can run it as its own app or add it to a web app you already have.
Underneath, a foundation you build on.
SDK · runtime · clientEverything above runs on one foundation: an SDK of blocks, state and a web runtime that you own. It is multi-user by design, so the same code serves one person or many. Use it to build your own app, or add it to a web app you already have. Most new features are configuration, not plumbing.
Start from a starter, or from nothing.
Define flows on the backend, then build the front end with typed React hooks and components. The foundation handles state, streaming and runs.
Mount it in the app you have.
Drop the runtime into Next.js or a Node server, point it at your own stores, and call it from your existing front end. No rewrite.
Blocks
Five kinds of building block, from model calls to plain code, checks and routing. Compose them into any flow.
State and resources
An ORM for agents: typed state and documents, scoped to a session, user or org, on the store you choose.
Task boards
Tasks and sub-tasks that people and workers share, with status everyone can see.
Workers
A worker is any flow you can assign work to: an agent, a coding harness like Claude Code, Codex or Cursor, or a workflow of your own.
Worker messaging
Workers pass work along, ask each other questions, and ask a person when they need one.
Durable runs
Long work survives restarts and resumes where it stopped.
Routing and budgets
Send each task to the right model or agent, within the budgets and CPU you set.
Client SDK and React
Typed hooks and components, so the front end is the only part you build.
Also included
-
DevTools
See every run, step, message and state change as it happens.
-
Multi-user
Many people on one workforce, each with their own sessions and state.
-
Scale across servers
Run your backend on several hosts and add more servers as load grows.
-
MCP
Give workers tools through MCP servers, yours or the community's.
-
Scheduled jobs
Work that starts itself, on a schedule.
-
Webhooks
Start work from events in the systems you already use.
-
Skills
Package know-how as skills any worker can load, and share them across your workforce.
-
Memory
Workers remember what matters across runs, stored in your state, not a vendor's.
Built for the web, from one user to many.
Flow State is a web service, not a single process on one machine. Every run belongs to a user and streams to their browser as it happens. State is scoped to a session, user or org and lives in your own stores. When load grows, add servers.