01 STUDIO OS / OPEN SOURCE / LOCAL FIRST

The missing layer between a prompt and a product.

Studionaut gives coding agents a studio to work inside. It keeps project truth, directs specialist work, watches the rendered product, repairs what breaks and decides whether the work is ready to ship.

SCROLLTHE STUDIO STARTS HERE
02 / WHY IT EXISTS

Generation is not
production.

AI can make an interface in minutes. The hard part begins after the first answer: preserving decisions, coordinating dependencies, catching visual drift, testing the browser and knowing when to stop.

Studionaut is the operating layer for that work. It does not replace the coding agent. It gives the agent a system to operate within.

WITHOUT A STUDIOPrompt → output → hope
×
WITH STUDIONAUTContext → direction → evidence → ship
03 / THE SYSTEM

One layer.
Five responsibilities.

Keep the host you already use. Put a persistent operating model around it.

01

Remember

Project state, decisions, constraints, artifacts and Design Truth stay explicit and inspectable.

02

Direct

Work becomes owned tasks with real dependencies, sequencing and specialist routing.

03

Observe

The rendered browser becomes evidence, not an afterthought to the source code.

04

Repair

Issues route back to the smallest capable specialist through bounded repair loops.

05

Decide

Review and verification determine whether the product ships or remains blocked.

BRIEF
HOST AGENT
BROWSER
EVIDENCE
THE CONTROL LAYERSTUDIONAUTTRUTH / GRAPH / POLICY / GATES
04 / THE OPERATING MODEL

From brief
to ship.

Fourteen explicit states turn an open-ended agent session into a controlled production loop.

01 / 14

Discover the project.

Read the brief, repository, constraints, hosts and capabilities before deciding how the work should be done.

OUTPUTPROJECT CONTEXT
DISCOVERUNDERSTANDDIRECTIMPLEMENTOBSERVEAUDITREPAIRVERIFYSHIP / BLOCK
05 / QUALITY

Quality is
a loop.

Prevention without detection misses reality. Detection without repair creates a backlog. Repair without verification creates regressions. Studionaut closes the loop.

01

PREVENT

Design Truth, rules, contracts and acceptance criteria establish the intended state.

02

DETECT

Validators and browser observation turn quality gaps into evidence-backed issues.

03

REPAIR

The responsible specialist fixes the issue inside a bounded convergence loop.

04

VERIFY

Relevant gates run again before the state can move toward release.

QUALITY SURFACE
BRANDLOGOTYPECOLOURVISUALIAUXCONTENTASSETSRESPONSIVEA11YINTERACTIONMOTIONSEOAEOGEOPERFORMANCECODESECURITYAI SLOP
06 / BROWSER TRUTH

Built code
is not proof.

The thing users experience is the rendered product. Studionaut makes browser observation part of the operating model, across target viewports and important interactions.

OBSERVATION / PRODUCT PREVIEW390 × 844
STUDIOWORK / SYSTEM / ABOUT
OBSERVATIONTHE BROWSER
IS EVIDENCE.
07 / HOST AGNOSTIC

Bring your agent.
Keep your studio.

Studionaut is designed to sit above the execution environment, not compete with it.

YOURS
LOCALMCPMIT
08 / THE BOUNDARY

The studio
stays yours.

Local-first. Cloud-optional. Deployment-agnostic. The core does not require a hosted Studionaut account, database or browser farm.

Read the architecture
09 / START

Give your agents
a place to work.

$npx studionaut setup
View on GitHub