Use event-driven agent interactions when exploration, iteration speed, and live observation matter more than strict ordering.
Custom Agentic Builder
A multi-agent CLI built for controlled execution, not toy demos
The Nostate CLI is a local-first runtime for coordinating specialized agents, observing behavior live, replaying session history, and switching between reactive collaboration and deterministic workflow execution when reliability matters more than improvisation.
- Free conversation mode for event-driven agent interaction
- Sequential mode for deterministic workflow execution and repeatability
- Durable session and message persistence for auditability and replay
Execution surface
$ upai session start$ upai run --mode free --agents planner,builder,reviewer$ upai workflow run publish-site --mode sequentialUse ordered workflows when the task needs explicit control, reproducibility, and a narrower failure surface.
Modes
Two execution modes, one runtime contract
The builder keeps the same core message, session, and policy ideas while allowing two different operating styles depending on how much determinism you need.
Specialized agent coordination
The runtime is designed to coordinate multiple focused agents instead of forcing every task through one monolithic assistant.
Live observation and replay
Operators can watch the system react in real time and revisit conversation history when debugging or reviewing output.
Hexagonal runtime boundaries
Provider adapters and infrastructure concerns stay out of the core domain so the runtime remains maintainable as integrations grow.
Workflow
Designed to move from prompt to execution without losing traceability
The CLI is intended for real operating work: define the task, choose the execution mode, watch the agents do the job, and keep enough history to inspect what happened later.
Start a session with explicit intent
Open a local-first session and choose whether the work should stay exploratory or follow a deterministic workflow.
Coordinate specialized agents
Let multiple roles contribute to the task while preserving separation between orchestration and low-level provider concerns.
Persist messages and state
Keep session and message history durable enough for replay, debugging, and future enterprise controls.
Integrate with the rest of the stack
Use the builder alongside the CMS and platform so content, workflows, and runtime validation stay connected.
Safeguards
Built with operator control, persistence, and future provider change in mind
The builder is meant to stay boring where it matters: explicit concurrency, lifecycle ownership, durable persistence, and clean integration edges.
- Local-first CLI and TUI operation instead of opaque browser-only behavior
- Durable session and message persistence as a first-class runtime concern
- Future LLM provider integrations without contaminating domain logic
- Deterministic workflow execution that can be tested independently from live agent interaction
Start
Use the CLI when you want agents to work with structure, not without guardrails.
The builder is strongest when it sits next to the CMS and platform: one place to automate work, one place to store structure, and one place to validate the result in a real environment.