An Eve coding agent that creates Eve agents, runs their checks, deploys them to Vercel, and verifies the live routes.
Eve Agent Builder turns a plain request like 'create an agent that answers onboarding questions' into a tested, deployed Eve agent, so you review approvals and results instead of running the delivery checklist yourself. Install it into an existing Eve app and talk to it through whatever channel that app already exposes: web chat, the Eve session API, Slack, or GitHub.
Every claim it makes is backed by a recorded result. The agent tests generated code in a real Vercel Sandbox with Node 24, and a hook captures the exit code of each eve info, build, and eval run. When it asks you to approve a deploy, the request quotes that recorded evidence, so you decide with facts rather than the model's recollection.
Deployment stays under your control. The bash tool denies Vercel CLI commands outright and routes them through run_vercel_cli, which pauses for human approval on every Connect setup, project link, and deploy, and refuses to deploy a workspace that is not already linked to a Vercel project. After deploying, it verifies the live health, session, and stream routes.
Ask for an agent that answers customer onboarding questions from your docs. The builder reads the repo, writes the instructions and evals, runs eve build and the eval suite locally, and stops with recorded results before any deploy.
The builder adds the Slack channel with run_eve_cli, then walks the Vercel Connect flow: create the Slack client, detach the default destination, attach it to /eve/v1/slack with triggers, deploy, and smoke-test delivery. You approve each Vercel step.
Deploy the builder itself and call it from another Eve app as a typed subagent with defineRemoteAgent. Task-mode runs return a structured delivery report: changed files, command outcomes, deployment URL and target, verification evidence, and blockers.
Point it at a failing Vercel deployment. It uses the Vercel MCP connection to pull build logs, runtime errors, and Agent Runs traces, fixes the cause in the repo, reruns the local checks, and redeploys after approval.
No. Every Vercel Connect setup, project link, preview deploy, and production deploy pauses for human approval; only the read-only whoami check runs without it. Deploys also refuse to run unless the workspace is already linked to a Vercel project, so a deploy can never silently create or target a project you did not confirm.
No. Eve injects VERCEL_TOKEN at the sandbox network policy, so it never enters command text, sandbox files, or generated source, and the bash tool denies any command that sets VERCEL_TOKEN. The preview bypass secret gets the same treatment and is cleared after verification.
A hook records the real exit code of every eve info, build, and eval call, and the runtime-status block replays that evidence to the agent each turn. Seven bundled evals also regression-test the guardrails, including that it never deploys before local testing and that it stops when credentials are missing.
It ships with zai/glm-5.2-fast at high reasoning effort, set in agent/agent.ts; change the model string there to use any model your gateway serves. The eval suite judges outputs with openai/gpt-5.4-mini, configured separately in evals/evals.config.ts.
Run npx shadcn@latest add @evex/eve-agent-builder inside an existing Eve app, then set VERCEL_TOKEN in the app runtime. The package adds no channel of its own; if your app has no interactive surface yet, add a web or Slack channel first.
npx shadcn@latest add @evex/eve-agent-builder