Beta access: FlowOS Local MCP is ready for early testing. For access notes, feedback, or beta coordination, email [email protected].
Local MCP beta
FlowOS
FlowOS gives an agent a local record system for decisions, standards, handoffs, evidence, scoped recall, reviewed capability growth, and A2A peer work.
What it does
FlowOS runs beside the agent as a local record system. Codex or another MCP-capable client calls its tools during normal work to recover project context, write back durable records, and coordinate scoped tasks with external agents.
Each workspace keeps its own record set, so agents can separate project memory and retrieve only the context that belongs in the current task.
Core objects
- Records keep decisions, evidence, issues, notes, standards, and handoffs.
- Recall returns active scoped records for behavioral use.
- State capsules compose compact task briefings from records.
- Capabilities describe reusable behavior, including repeated peer-agent workflows, and stay draft until reviewed.
Bootstrap
After beta access is set up, initialize a workspace and point your MCP client at the FlowOS stdio command.
flowos init
flowos status
flowos mcp
flowos a2a agent-card
flowos a2a serve
[mcp_servers.flowos]
command = "flowos"
args = ["mcp"]
Agent bootstrap prompt
Give this to a zero-context agent after adding the MCP command:
You have access to a local MCP server named flowos. At the start of meaningful work, call flowos.state_capsule with the current task and scope, or use flowos.recall when you need matching records. Write durable decisions, standards, evidence, issues, and handoffs with flowos.write_record. Use flowos.a2a tools when work belongs with another agent. Treat capability records as drafts until they are reviewed and promoted with flowos.promote_capability.
Beta focus
The current beta is focused on the agent record loop: recall the active context, write down what changed, coordinate peer work when needed, and promote reusable behavior only after review.