omadia
Back to home

the builder · agentic

An agent that builds agents.

spec → code → typecheck → smoke → ship.

Describe the agent you need. Talk to it while it’s still taking shape. The builder writes the code, runs the typechecker, fixes its own ESLint errors, smoke-tests at runtime, and only ships when green. Output is a signed ZIP plugin with the same install path as every other omadia plugin.

repairspeccodegentypechecksmokeinstallPLUGIN.ZIP

the honest pitch

Most ‘AI builders’ are templated form-fillers.

They ask you to pick from a dropdown, swap a few placeholders, and call it generation. The omadia builder is an agent in its own right. It writes the TypeScript. It runs `tsc`. It runs ESLint with auto-fix. It boots the plugin in a sandbox and pokes it with synthetic input. If a pass fails, it reads the error and tries again. You see every step.

A generator that skips the typechecker isn’t writing code. It’s writing guesses.
how the builder is built

pipeline

Five passes between idea and install.

Every plugin draft moves through the same gated pipeline. Each pass has a structured failure mode, with a repair loop the builder agent drives itself.

Spec

agentSpec

A versioned, validated draft of the agent: capabilities, tools, prompts, slots. Source of truth for every pass downstream.

Codegen

codegen + boilerplate

Spec is rendered into a working plugin tree on top of the live boilerplate. No string-template black box. Every emitted file is reviewable.

Typecheck + lint

slotTypecheckPipeline · eslintAutoFix

TypeScript strict-mode compile plus ESLint with auto-fix. Errors are parsed, fed back to the builder agent, and patched in place.

Runtime smoke

runtimeSmokeOrchestrator

The plugin is loaded in a sandbox, given synthetic input, and observed end-to-end. Crash, timeout, schema-mismatch. All caught here, not in production.

Install

installCommit

Green plugin gets sealed into a signed ZIP and committed to the Plugin Store. Same install surface as any other plugin. Uninstall is clean.

BUILD CONSOLE

spec

agent: hr-time-off · capabilities: chat · tools: list_pto, request_leave · channel: teams

  • phaseagentSpecok
  • phasecodegen + boilerplateok
  • phaseslotTypecheckPipeline · eslintAutoFixok
  • phaseruntimeSmokeOrchestratorok
  • phaseinstallCommitrun

5/5 passes · ready to install

what you get

Six things templated builders can't do.

All of it ships by default, and each one is why we built our own builder.

Talk to it while it builds

Live preview chat with the half-finished agent. Tweak the prompt, watch the next turn change. No build-wait-test loop.

Repairs its own errors

Typecheck and lint failures feed back into the builder agent as structured hints. It patches, recompiles, retries, and shows you the diff.

Smoke-tested before install

Synthetic input, a sandboxed boot, end-to-end observation. Anything that ships has already run there.

Round-trip from installed

Clone any installed plugin back into an editable draft. Modify, retest, reinstall. The bundle is the spec, the spec is the bundle.

Sandboxed builds

Builds run in an isolated worker. No host-process access, no internal-package leakage, manifest linted before install.

Same install surface

Output is a normal signed ZIP plugin. It goes through the same Plugin Store and the same Capability matrix as any third-party plugin.

shipped

Dashboard codegen.

status · shipped
B.12

The builder ships agent plugins and their operator dashboards. A single ui_routes block in the spec compiles to a React-SSR dashboard route the middleware mounts. Same pipeline, same passes, same signed-ZIP output. uiRouteSchema is on main.

pilot

Want to build one in the call?

Pick a 30-minute slot. We open the builder live, spec out an agent that fits a real workflow on your side, and you walk away with a draft you can install on your infrastructure.

Book a slotRequest a demo · 30 min · video