Tasks in the right order
Generation follows task dependencies, with up to three ready tasks running at once. Each task has assigned files, so separate outputs have a defined place to come together.
Nemeow Harness
An idea needs more than a model.
Nemeow Harness is the system we built around app generation. It organizes context, sequences tasks and checks the results, carrying your confirmed requirements through to a preview you can review.
Built into Builder · Purpose-built for app generation
Understand the request
Bring requirements and project context together.
Confirm and build
Start generation after an explicit Build confirmation.
Orchestrate and generate
Prepare the design and file responsibilities, then generate in dependency order.
Check and correct
Validate structure, imports and compilation within bounded correction rounds.
Preview and refine
Review the result, then continue the conversation.
Process illustration. Publishing is a separate decision.
WHAT IS A HARNESS?
The structure around the intelligence.
A model generates an answer. A harness organizes the work around that answer: what context to provide, which task comes next, how to check the output, and when to ask for clarification. In Nemeow, this is a dedicated part of Builder that turns separate generation steps into a controlled process.
Give each step a purpose. Give each result a check.
Checks before the preview
Output structure, file ownership, imports and compilation are checked. Located problems feed bounded correction rounds; unresolved failures remain visible.
Clarify, then continue
When a generation task needs clarification, it can return a question with its draft. Validated completed work can be reused when generation resumes.
A process with a record
Generation traces record stages, checks and outcomes for diagnosis. Cancellation and billing are handled by the platform alongside the generation flow.
AN ILLUSTRATIVE WORKFLOW
Take a customer follow-up page.
“Help me see my customers, their status and the next follow-up.”
An example of the process, not a generated result or a promise that every request succeeds.
Make the request concrete
Clarify the fields, page layout and actions needed before confirming the build.
Build within a shared plan
Assign page and component files, respect their dependencies and check the combined output.
Review the actual page
Inspect the preview and refine the details. Data access follows the app’s authorization; publishing stays a separate step.
Useful work, within clear boundaries.
Your confirmation matters
Chat, Plan and Build have distinct roles. Discussing an idea does not authorize a build, and completing a build does not automatically publish an app.
Access has a defined scope
Workspace and App isolation apply throughout. Data access goes through the controlled SDK and trusted Gateway, with capability approval and revocation. Generated code receives no direct database, secret or arbitrary SQL access.
A draft is not a release
App publishing activates an immutable Release through its own checks. Preview, publishing and rollback retain separate permission boundaries; rollback cannot restore revoked access.
A few useful distinctions.
How is Harness different from MCP?
Harness organizes how Builder carries out generation. MCP is a protocol for connecting AI applications with tools and context. They solve different parts of the workflow; the MCP page describes that product direction and its availability.
Explore the MCP overviewIs this an agent that can use any tool?
No. The current harness is a platform-directed Builder workflow. It follows defined generation tasks and validation rules, rather than letting a model choose arbitrary tools or run unrestricted code.
Does it keep repairing until everything works?
Correction is bounded. A task may need clarification or stop with a failure. Passing code checks does not prove that every interaction meets your needs; review the actual preview before deciding what comes next.
Start with the work you want to do.
Describe your idea. Shape the plan. Review what gets built.
Start building