Mayar Eve Builder 1.0.0

Mayar Eve Builder v1.0.0

Mayar v1.0.0 is the first stable comparison release of the Eve-powered builder pipeline. It keeps the existing NestJS jaxagentsdk untouched and provides a standalone Eve implementation that developers can run, inspect, and extend independently.

Highlights

• Standalone Eve app and website builder under agent/.
• Durable Eve session entrypoint through /eve/v1/session and /eve/v1/session/:sessionId/stream.
• Multi-agent pipeline: intent, conversation, orchestrator, design research, code writer, autofix, and security review.
• Human approval checkpoint before code generation through Eve's built-in ask_question flow.
• Eve-native local tools for generated file writes, finite quality commands, preview process startup, and Unsplash image search.
• Role-based model selection with environment overrides, mirroring the multi-model strategy from jaxagentsdk.
• Sandbox-first generation under /workspace/generated-app, with safe relative-path validation and no secret writes.
• CI and release workflows for audit, typecheck, build, smoke checks, packaging, artifact upload, and GitHub releases.

Architecture

Mayar routes every user message through the root Eve agent. The root calls the intent subagent first, refuses unsafe requests before builder agents, sends normal chat to the conversation subagent, and sends build requests through the builder chain.

The builder path is:

1. intent: classify request and safety.
2. orchestrator: convert the prompt into a build handoff.
3. design_research: produce an approval-ready design plan.
4. ask_question: pause for approve, revise, or stop.
5. code_writer: generate a complete Next.js project.
6. write_generated_files: write files into the Eve sandbox under /workspace/generated-app.
7. run_quality_commands: install and run finite quality commands.
8. autofix: repair generated files when validation fails.
9. start_preview: start the preview process and return sandbox status, command, port, and sandbox id.
10. security_review: check for secret exposure, unsafe browser env usage, and common web app risks.
11. conversation: produce the final user-facing summary.

Developer notes

• Use pnpm install --frozen-lockfile for reproducible installs.
• Use pnpm run typecheck and pnpm run build before pushing.
• Use pnpm run smoke for static project-shape verification.
• Use pnpm run dev for local Eve testing.
• If local Eve dev reports a stale workflow cache after edits, clear generated artifacts with rm -rf .eve .output and restart.

Environment

Required:

• AI_GATEWAY_API_KEY, or Vercel OIDC in an environment where the configured AI Gateway route is available.

Optional:

• UNSPLASH_ACCESS_KEY
• UNSPLASH_API_BASE_URL
• INSFORGE_API_BASE_URL
• INSFORGE_API_KEY
• MAYAR_ROOT_MODEL
• INTENT_AGENT_MODEL
• ORCHESTRATOR_AGENT_MODEL
• DESIGN_RESEARCH_AGENT_MODEL
• CODE_WRITER_AGENT_MODEL
• AUTOFIX_AGENT_MODEL
• SECURITY_REVIEW_AGENT_MODEL
• CONVERSATION_AGENT_MODEL

Compatibility

• Node.js >=24 <27
• pnpm 11.5.0
• Eve 0.11.4
• AI SDK 7.0.0-beta.178
• Zod 4.4.3

Known limitations

• Eve preview URL resolution is not exposed in the current local docs, so v1 reports sandbox id, preview command, and port instead of inventing a URL.
• The current Eve/provider combination rejects valid JSON text when optional subagent outputSchema is passed for this workflow. Mayar keeps shared Zod schemas for developer reference and asks subagents for plain JSON text in the message field.
• CI validates buildability and static smoke checks. Full live agent smoke tests require model credentials and are best run locally or in a protected environment.