Agentlas OS

Meta-Agent Factory

Turns a one-line request into a specified, buildable agent — instead of one more weak role-prompt — by refusing to generate until the request is unambiguous enough to build correctly.

The Briefing Interview

Before generating anything, the build flow scores your request's ambiguity across four dimensions: goal, constraints, scope, and context. A clear request skips the interview entirely — there's a question budget so trivial asks don't get interrogated. An ambiguous one gets asked lens-based questions (scope, intent, edge cases, architecture) until the score clears the threshold.

What gets locked before code is written

A goal you actually confirmed, not one inferred from a single sentence.
Explicit constraints — what the agent must never do (its anti-scope).
Verifiable acceptance criteria, so "done" isn't a guess.
An assumption ledger: anything the interview didn't ask, tagged with why it was assumed.

This gets frozen as a work brief before the build runs, so the finished agent's routing triggers and anti-triggers can be traced back to what you actually asked for.

Three build modes

Single agent

One focused worker with its own memory contract and routing card.

Multi-agent team

An orchestrator plus workers, Memory Curator, and policy gate, wired together.

Package an existing agent

Turn something you already built into an installable, portable package.

Browse built agents on the Hub →