Vercel eve v0 operator

Configure eve channels and schedules with platform triggers, cron definitions, identities, delivery targets, autonomous-run bounds, timezone handling, and failure recovery. Use when putting an agent in chat, adding scheduled work, changing triggers, or diagnosing duplicate and missed autonomous runs.

Look up Vercel eve commands, configuration, policy, and focused operations across definitions and tools, sessions and workflows, subagents and approvals, channels and schedules, evals and observability. Use when the user wants a concise reference instead of a guided workflow.

Create and operate eve agent definitions, instructions, model configuration, skills, MCP connections, and typed tools with explicit authority and validation. Use when defining an agent, adding knowledge or tools, configuring a model, or connecting an MCP server.

Inspect Vercel eve versions, local project structure, account or team context, environment variable names, configured resources, policies, observability, and safe checks without changing anything. Use before Vercel eve work, when the target is uncertain, or when the user asks what is configured.

Author and operate eve eval suites, CI gates, Agent Runs, traces, token and tool accounting, redaction, retention, and regression review. Use when testing an agent, gating deployment, inspecting a failed run, or measuring prompt and tool changes.

Connect Vercel eve to application runtimes, identity, external services, persistence, observability, CI, and deployment while preserving account, credential, data, and action boundaries. Use when Vercel eve must cross another system or operate consistently through production.

Operate eve durable sessions and workflow-backed conversations including creation, streaming, continuation tokens, checkpoints, pause, resume, crash recovery, and version behavior. Use when starting or resuming sessions, fixing lost progress, consuming the session API, or validating durability.

Install and configure Vercel eve from zero with project-local tooling, exact account and project scope, server-only credentials, baseline policies, one minimal feature, and bounded verification. Use when a project has no Vercel eve setup or the user explicitly asks to initialize it.

Design eve built-in and declared subagents plus durable human approvals with scoped delegation, isolated context, permission boundaries, decision payloads, and resume behavior. Use when adding specialists, delegating parallel work, or requiring a person to approve consequential agent actions.

Diagnose Vercel eve failures involving versions, account scope, credentials, permissions, configuration, remote resources, durability, providers, observability, costs, and deployment without masking the original error. Use when Vercel eve fails, behaves differently across environments, or causes unexpected remote effects.