Web Dev Agent
TencentEdgeOne/vibe-coding-agent
Agent que converte requisições naturais em apps web com preview instantâneo
Ver no GitHubAgent baseado no Claude Agent SDK que transforma requisições em linguagem natural em projetos web funcionais. Cria um sandbox isolado temporário para cada conversa, gerando e editando arquivos, instalando dependências, publicando preview ao vivo e fornecendo feedback de verificação no loop do agent.
Instalação
npx convez-ai TencentEdgeOne/vibe-coding-agent1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar protótipos de Next.js, React/Vite ou apps estáticos sob demanda
- Criar previews ao vivo de projetos web durante desenvolvimento
- Automatizar criação e ajuste de código web com feedback de compilação
Veredito

Agent bem estruturado para desenvolvimento web ágil, com suporte a múltiplos stacks e sandbox isolado. Integração direta com Makers Models torna-o prático para prototipagem, mas documentação local e exemplos de uso poderiam ser mais detalhados.
README
A tradução para o português deste README ainda está na fila.
Web Dev Agent
A sandbox-based web development agent built with the Claude Agent SDK on EdgeOne Makers.
Framework: Claude Agent SDK · Category: Coding · Language: TypeScript
Overview
Web Dev Agent turns natural-language requests into runnable web projects. For each conversation, it prepares an isolated temporary sandbox workspace where it creates or edits project files, installs dependencies, publishes a live preview, and feeds verification results back into the agent loop. Use it for coding-style Makers templates where users need a generated app, a visible preview, and a file browser in one workflow.
- Temporary sandbox workspace — creates and edits project code inside the current conversation's temporary sandbox
- Multi-stack generation — creates or updates Next.js, Vite/React, static, Node service, Flask/FastAPI, and similar lightweight web apps
- Claude Agent SDK loop — runs the model with EdgeOne sandbox MCP tools and a restricted tool set
- Live preview — starts the app inside the temporary sandbox and returns a runtime-generated preview URL
- Verification feedback — runs build or Python compile checks and attempts one automatic repair pass when verification fails
Environment Variables
| Variable | Required | Description |
|---|---|---|
AI_GATEWAY_API_KEY | Yes | Model gateway API key. Use your Makers Models API Key, or any OpenAI-compatible provider key. |
AI_GATEWAY_BASE_URL | Yes | Gateway base URL. For Makers Models, use https://ai-gateway.edgeone.link/v1. |
AI_GATEWAY_MODEL | No | Model ID. Defaults to @makers/minimax-m2.7 (a built-in Makers model). |
WEB_DEV_AGENT_DEBUG | No | Set to true or 1 to enable redacted server-side debug logs. Defaults to off. |
This template follows the OpenAI-compatible standard — point these at Makers Models or any compatible provider.
How to get AI_GATEWAY_API_KEY
- Open the Makers Console.
- Sign in and enable Makers.
- Go to Makers → Models → API Key and create a key.
- Copy it into
AI_GATEWAY_API_KEY.
Built-in models are free and rate-limited, which makes them suitable for validation. For production, bind your own provider key (BYOK) in the console.
Provider fallbacks
The agent prefers AI_GATEWAY_* variables. It also accepts Anthropic-compatible and DeepSeek-compatible fallback variables when needed:
| Variable | Required | Description |
|---|---|---|
ANTHROPIC_API_KEY | No | Anthropic-compatible API key fallback. |
ANTHROPIC_AUTH_TOKEN | No | Anthropic-compatible auth token fallback. |
ANTHROPIC_MODEL | No | Anthropic-compatible model fallback. |
ANTHROPIC_BASE_URL | No | Anthropic-compatible base URL fallback. |
ANTHROPIC_CUSTOM_HEADERS | No | Extra headers passed to the Anthropic SDK. |
DEEPSEEK_API_KEY | No | DeepSeek-compatible API key fallback. |
DEEPSEEK_MODEL | No | DeepSeek-compatible model fallback. |
DEEPSEEK_BASE_URL | No | DeepSeek-compatible base URL fallback. |
CLAUDE_CODE_EXECUTABLE_PATH | No | Optional path to a custom Claude Code executable. |
Local Development
Prerequisites: Node.js, npm
npm install
cp .env.example .env
edgeone makers dev
Open http://localhost:8088/agent-metrics for the local observability panel.
Project Structure
web-dev-agent/
├── app/ # Next.js frontend UI
│ ├── layout.tsx # App metadata and root layout
│ ├── page.tsx # Chat, progress, preview, and file browser UI
│ └── globals.css # Global styles
├── agents/ # EdgeOne Makers agent routes and pipeline
│ ├── chat.ts # /chat route
│ ├── file.ts # /file route
│ ├── _agent.ts # Claude Agent SDK integration
│ ├── _constants.ts # Runtime constants
│ ├── _memory.ts # Conversation history and project state
│ ├── _pipelines.ts # Chat and file-read pipelines
│ ├── _project.ts # Sandbox project, preview, and verification helpers
│ ├── _types.ts # Shared TypeScript types
│ ├── tools/ # Custom sandbox MCP tools
│ └── utils/ # Path, text, and build-error helpers
├── edgeone.json # Agent runtime configuration
├── next.config.ts # Next.js configuration for the template app
├── package.json # Scripts and dependencies
└── tsconfig.json # TypeScript configuration
Files prefixed with _ are private modules — not exposed as public routes by EdgeOne.
How It Works
The agent runs in session mode under agents/. Requests with the same conversation_id are routed to the same runtime instance and reuse the same temporary project workspace for the sandbox lifetime.
- Request — the frontend calls
/chatwith a message and theMakers-Conversation-Idheader. A new request from the home view can also setresetProject: trueto recreate the project workspace. - State restore — the chat pipeline reads conversation history from
context.storeand loads metadata for the current temporary sandbox project. - LLM and tool loop — the Claude Agent SDK runs with the
edgeone-sandboxMCP server,permissionMode: 'dontAsk', and sandbox-only tools. The agent must callensure_project_scaffoldbefore reading or writing project files. - Project editing — generated source files are written through
write_project_filesor sandbox file tools. Commands and dependency installation run inside the sandbox. - Preview publish —
publish_previewstarts the app on internal port3000, waits for the preview entry to become ready, and returns a preview URL that is valid only for the current temporary sandbox lifetime. - Verification — the runtime runs
npm run buildwhen a Node project has a build script, orpython -m compileall .when Python files are present. If verification fails after a successful agent run, the pipeline attempts one auto-fix pass. - Response stream — the frontend receives status events, logs, tool calls, tool results, file tree updates, the preview URL, build status, and the final assistant reply as newline-delimited JSON.
The file route is /file?path=<relative-path> and uses the same conversation context to read text files from the temporary sandbox project. Sandbox credentials are provided by the runtime; no local sandbox credentials are required. The sandbox and generated code are temporary, and their lifetime is controlled by agents.sandbox.timeout in edgeone.json, currently set to 1800 seconds.
Resources
License
MIT