--- title: CLI description: Reference for every eve CLI command: init, set, info, build, start, dev, logs, traces, link, deploy, eval, channels, extension, and telemetry. --- # CLI Relevant `eve` commands can run from the application root or any directory beneath it. Running `eve` with no command runs `eve init` when the current directory is not an eve project, or `eve dev` when it is. ## Commands | Command | Description | | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | | `eve` | Initialize the current directory, or start development when it is already an eve project | | `eve init [target]` | Create a new agent, or add an agent to an existing project | | `eve info` | Print the resolved application, including static instructions and discovered capabilities, routes, artifact paths, and diagnostics | | `eve build` | Compile `.eve/` artifacts and build the host output; prints the output directory | | `eve start` | Serve the built `.output/` app; prints the listening URL | | `eve dev` | Start the local dev server and open the terminal UI | | `eve dev ` | Connect the UI to an existing server URL (e.g. a remote deployment) instead of booting a local server | | `eve acp [url]` | Serve the local application or an existing eve server URL as a stable ACP v1 agent over stdio | | `eve logs [logid]` | Print an `eve dev` diagnostic log (the most recent when `logid` is omitted) | | `eve logs ls` | List `eve dev` diagnostic logs, most recent first | | `eve traces ls` | List locally captured agent traces, most recent first | | `eve traces [trace]` | Show a local span tree (the most recent when omitted) | | `eve telemetry ` | Show, enable, or disable CLI telemetry collection | | `eve link` | Link the directory to a Vercel project and pull AI Gateway credentials | | `eve deploy` | Deploy the agent to Vercel production (links first if needed) | | `eve eval` | Run evals against the local app or a remote target | | `eve channels list` | List user-authored channels | | `eve extension init [target]` | Create a new extension package | | `eve extension build` | Build the current package as an extension | | `eve set` | Change the root agent's model and reasoning effort | | `eve add ` | Install an item from the official or a configured shadcn registry | | `eve integration setup ` | Run a built-in setup flow directly after its registry files are installed | | `eve registry ` | Add sources and list, search, or view registry catalog items | When `eve build` fails on discovery errors, it prints the full diagnostics report (severity, message, source path) and the diagnostics artifact path. ## CLI telemetry eve collects CLI telemetry by default to improve the command-line interface. Run `eve telemetry disable` to disable it for this machine, or set `EVE_TELEMETRY_DISABLED=1` for one command. See [CLI telemetry](./telemetry) for the current data fields, exclusions, debug mode, notice, and local preference storage. ## `eve init` ```bash eve init [target] [--model ] [--reasoning ] [--channel-web-nextjs] ``` Creates a new agent app or adds an agent to an existing app. Always installs dependencies. New directories also initialize Git. | Target | What happens | | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | `eve init my-agent` | Creates an agent project in `my-agent/` | | `eve init` or `eve init .` in an empty directory | Creates an agent project in the current directory | | `eve init` or `eve init .` in a directory with files other than environment metadata and no `package.json` | Refuses to overwrite the directory. Pass a new directory name, such as `eve init my-agent` | | `eve init` or `eve init .` in an existing project | Adds `agent/` plus missing `eve`, `ai`, and `zod` dependencies. Requires `package.json` and no existing `agent/` files | | `eve init path/to/app` | Adds an agent to the existing package at `path/to/app` | Existing packages do not need a target-selection prompt: run `eve init` from the project directory or `eve init path/to/app`. New projects in non-interactive environments need a new directory name, such as `eve init my-agent`. After scaffolding, a human terminal usually continues into `eve dev`. Enable the self-modification subagent to edit your agent from the dev session. Otherwise, if a coding-agent REPL is on `PATH`, you can launch it to make changes instead of opening the TUI. Fresh projects use the parent workspace's package manager when there is one; otherwise they use the manager that launched `eve init`. | Flag | Type | Default | Description | | ---------------------- | ------ | -------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | `--model ` | string | `openai/gpt-5.6-luna-fast` | Set the root agent's AI Gateway model ID. | | `--reasoning ` | enum | provider default | Set reasoning to `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`. `provider-default` leaves the field unauthored. | | `--channel-web-nextjs` | flag | off | Add the Web Chat app (Next.js). Not for existing projects — run `eve add channel/web` there instead. | ## `eve extension` Commands for reusable [extension](/docs/extensions) packages. An extension declares distinct authoring and distribution roots in `package.json#eve.extension` (for example `"eve": { "extension": { "source": "./extension", "dist": "./dist/extension" } }`). ### `eve extension init` ```bash eve extension init [target] ``` Creates a new extension package, installs dependencies, and initializes Git. Prints next steps instead of starting `eve dev`. | Target | What happens | | --------------------------- | ------------------------------------------------------------- | | `eve extension init my-crm` | New extension package in `my-crm/` | | `eve extension init .` | Scaffold in the current empty directory | | No target | Same as `.` for humans; coding agents get a short setup guide | Create-only: cannot target an existing project that already has a `package.json`. See [Extensions](/docs/extensions) for authoring and mount details. ### `eve extension build` ```bash eve extension build ``` Builds the complete agent-shaped extension tree into its configured dist root, emits declarations and compatibility metadata, and fills the package `exports` map. The original TypeScript source is not required in the published package. ## Set model settings Change the root agent's AI Gateway model and reasoning effort without opening the dev TUI: ```bash eve set \ --model openai/gpt-5.6-sol \ --reasoning high ``` Pass either flag by itself to change one setting. When you pass both, eve writes them to `agent/agent.ts` in one source edit. `--reasoning` accepts `provider-default`, `none`, `minimal`, `low`, `medium`, `high`, or `xhigh`; `provider-default` removes the authored `reasoning` field. The command uses the same model ID validation and source editor as `/model` in the local dev TUI. It does not configure model credentials. The `--model` flag cannot rewrite models defined with `defineDynamic`, an environment expression, or a provider-authored SDK model; change those models in `agent.ts`. `--reasoning` can still update an editable root config when its model comes from an SDK call. ## Registry items Commands for installing and discovering [shadcn registry](https://ui.shadcn.com/docs/registry) items. Official registry items use a kind and slug (for example, `extension/agent-browser`); URLs and configured registry addresses are also supported. ```bash eve add extension/agent-browser eve add channel/linear eve add channel/slack --skip-install eve add https://example.com/r/my-extension.json --overwrite eve registry add @acme=https://example.com/r/{name}.json eve registry search browser eve registry search browser --limit 5 eve registry search browser --registry @acme eve registry view @acme/my-extension eve add @acme/my-extension ``` `eve add` asks before running setup declared by an official item and runs multiple declared flows in declaration order. Interactive Vercel-backed setup signs in and creates or links a project when needed instead of stopping with a prerequisite. `--yes` accepts detected or recommended setup answers. Coding agents should use `eve add --non-interactive`, adding `--yes` to accept recommended setup values and reduce setup round trips. Explicit `--answer` values take precedence. This mode never opens an eve prompt. When a setup decision is missing, the NDJSON terminal event includes a stable question key and a safe continuation command; add the requested answer to that command. Supply answers with repeatable `--answer 'key='` options. Follow a reported `eve link` prerequisite before retrying Vercel Connect setup. Do not put secrets in command-line answers; use the integration's documented environment variable or secret store. When setup is skipped, cancelled, or needs more input after installation, eve prints or returns the matching `eve add --skip-install` continuation. It reruns the item's declared flows without reinstalling registry files. `eve registry add` records configured sources in `package.json#registries`. `eve registry list` aggregates the official catalog and all configured sources by default. `eve registry search` also includes [skills.sh](https://skills.sh), available without configuration at `@skills`, and groups results by source with each source's available result count. Search returns up to 10 matches per source by default; pass `--limit ` to request between 1 and 100. Either command can browse one supplied URL or namespace. Official and other universal items with explicit file targets do not require shadcn project configuration. ## `eve info` ```bash eve info [--json] ``` | Flag | Type | Default | Description | | -------- | ---- | ------- | ------------ | | `--json` | flag | off | Emit as JSON | Run this first when something behaves unexpectedly. It confirms a file was discovered, lists the active surface, and surfaces discovery diagnostics, all faster than booting the dev server. Static instructions appear in source order with their `system` or `user` role. Dynamic instruction results are runtime-only and do not appear here. ## `eve build` ```bash eve build [--profile ] [--skip-sandbox-prewarm] ``` Compiles and bundles in an invocation-owned directory under `.eve/builds/`, then publishes the completed host output and prints its path. Scratch workspaces are removed after success or failure. Authored bundles preserve custom Node.js resolution conditions supplied through `--conditions`, `-C`, or `NODE_OPTIONS`. For example, `NODE_OPTIONS="--conditions=react-server" eve build` keeps a channel's `server-only` imports on the same export used during compilation. | Flag | Type | Default | Description | | ------------------------ | ------ | ------- | --------------------------------------------------------------------------------------------- | | `--profile ` | string | off | Best-effort versioned JSON report with build-phase timings and final output-size measurements | | `--skip-sandbox-prewarm` | flag | off | Skip sandbox template prewarm for a Vercel build; the output might not be deployable | Use a profile file to establish a repeatable baseline before changing the build pipeline: ```bash eve build --profile .eve/build-profiles/baseline.json ``` The report is attempted only after a successful build. It records total elapsed time, completed phase timings, and final regular-file totals for file count, raw bytes, and the sum of each file compressed with gzip. For Vercel output it also includes a subtotal for every real `.func` directory, so app and flow bundles can be compared separately. The profile path resolves from the app root and should be outside the published output directory; profile collection does not add a file to the deployment. If collection or writing fails, eve emits a warning but keeps the completed build successful. Production builds do not write through the stable compiler, host, Nitro, or Workflow files owned by `eve dev`, so builds can run while a local dev server is active. A failed build leaves the last successful `.output/` and agent summary untouched. Concurrent completed builds serialize only the final publication window. Useful stable artifacts written by inspection and development flows under `.eve/` include: | Artifact | Description | | ---------------------------------------------- | ---------------------------------------------------- | | `.eve/discovery/agent-discovery-manifest.json` | What eve found on disk | | `.eve/discovery/diagnostics.json` | Authored-shape errors and warnings | | `.eve/compile/compiled-agent-manifest.json` | The serialized authored surface eve loads at runtime | | `.eve/compile/compile-metadata.json` | Build-time metadata and paths | | `.eve/compile/module-map.mjs` | Compiled module entrypoints eve imports at runtime | ## `eve start` ```bash eve start [--host ] [--port ] ``` | Flag | Type | Default | Description | | --------------- | ------ | ------------------ | ---------------------- | | `--host ` | string | all interfaces | Host interface to bind | | `--port ` | number | `$PORT`, then 3000 | Port to listen on | Serves the previously built output. Prints the listening URL. For self-hosted deployments, copy the app source, `.output/`, and installed dependencies together. The deployment directory can differ from the build directory. Preserve the relative layout of any workspace packages used by the app; startup resolves sandbox prewarm modules from the deployed source. ## `eve dev` ```bash eve dev [options] eve dev https://your-app.vercel.app ``` Pass a bare URL and the UI connects to that server instead of booting a local one (same as `--url`), which lets you smoke-test a preview or production deployment. The interactive UI turns off in a non-TTY terminal. | Flag | Type | Default | Description | | ----------------------------------- | ------ | ------------------ | ----------------------------------------------------------------------------------------- | | `--host ` | string | all interfaces | Host interface to bind | | `--port ` | number | `$PORT`, then 2000 | Port to listen on | | `-u, --url ` | string | none | Connect to an existing server URL instead of starting one | | `-H, --header
` | string | none | Request header for a URL target, in `Name: value` form; repeat for multiple headers | | `--no-ui` | flag | UI on | Start the server without an interactive UI | | `--name ` | string | app folder name | Title shown in the terminal UI | | `--input ` | string | none | Pre-fill the prompt input | | `--tools ` | enum | `auto-collapsed` | Tool-call rendering: `full` \| `collapsed` \| `auto-collapsed` \| `hidden` | | `--reasoning ` | enum | `full` | Reasoning rendering: `full` \| `collapsed` \| `auto-collapsed` \| `hidden` | | `--subagents ` | enum | `auto-collapsed` | Subagent-section rendering: `full` \| `collapsed` \| `auto-collapsed` \| `hidden` | | `--connection-auth ` | enum | `full` | Connection-authorization rendering: `full` \| `collapsed` \| `auto-collapsed` \| `hidden` | | `--assistant-response-stats ` | enum | `tokensPerSecond` | Assistant header statistic: `tokens` \| `tokensPerSecond` | | `--context-size ` | number | none | Model context window size, shown as a usage percentage | | `--logs ` | enum | `stderr` | Server/agent logs to show: `all` \| `stderr` \| `sandbox` \| `none` | `eve acp` reserves stdin and stdout for newline-delimited JSON-RPC and sends diagnostics to stderr. Without a URL, it supervises an isolated local development server. With a URL, it bridges ACP to that server's existing eve HTTP API and accepts the same URL credentials and request headers as `eve dev `. Pass `--scope ` when the active Vercel scope does not own the deployment; `EVE_VERCEL_SCOPE` provides the same value for managed harnesses. See [Agent Client Protocol (ACP)](../protocols/acp) for client configuration and capability limits. A fresh `eve init` starts onboarding before the first prompt: the TUI installs the Vercel CLI if needed, asks you to log in if needed, guides you through model configuration, then lets you choose channels and integrations. Other `--input` text stays editable in the prompt. For a URL target protected by HTTP Basic auth, put the credentials in the URL. eve sends them as a Basic `Authorization` header and strips them from the server URL before connecting: ```bash eve dev https://user:pass@your-app.example.com ``` For bearer tokens or custom schemes, pass explicit headers with `-H`. ### `eve invoke` | Option | Type | Default | Description | | ----------------------- | ------ | ------- | ----------------------------------------------- | | `[prompt]` | string | none | Prompt, follow-up, or answer to a pending input | | `-u, --url ` | string | local | Invoke an existing server | | `-H, --header
` | string | none | Request header for a URL target; repeatable | | `--resume` | flag | off | Read a previous resumable result from stdin | | `--scope ` | string | current | Vercel team that owns the URL target | | `--json-schema` | flag | off | Print the result JSON Schema and exit | Use `eve invoke` to submit a turn without opening the TUI. It emits JSON after the invocation completes or reaches a blocking input or authorization event. ```bash eve invoke "Summarize station telemetry" result=$(eve invoke "Deploy the application") printf '%s' "$result" | eve invoke --resume "approve" eve invoke --json-schema ``` `--resume` reads a complete previous result from stdin. Supply text for a `ready` follow-up or pending input; the agent harness resolves input text against all pending requests. A `ready` result includes the previous turn's completed or failed `outcome`. An `authorization-required` result lists every unresolved challenge in `authorizations`; complete them, then resume without text. Pass explicit headers again for protected remote servers. If the URL belongs to another Vercel team, pass its slug with `--scope`; this does not relink the current directory. Pass the scope again when resuming. Paused invocations exit `3`; failures exit `1`. Local callback-based connection authorization requires a persistent server. Run `eve dev`, then use `eve invoke --url ` instead. If a waiting invocation receives `SIGINT` or `SIGTERM` after acceptance, it emits a final resumable `running` result before exiting. Local dev records the last ready URL per resolved app root in `.eve/dev-server-state.v1.json`. A second interactive `eve dev` reconnects only when that URL is loopback and healthy; each terminal UI creates a fresh client session while sharing the server process. A stale or malformed record is replaced when eve starts a new server. Passing `--host`, `--port`, or a `PORT` environment value skips reconnection and reports a healthy recorded server instead. Local dev keeps immutable runtime generations under `.eve/dev-runtime/snapshots/` so in-flight turns hold a consistent code revision while new turns pick up rebuilds. Each generation contains the compiled authored module graph and runtime resources rather than a recursive copy of the app or workspace. The terminal REPL keeps its logical session across successful rebuilds, so the next turn continues the conversation on the latest generation; `/new` terminally retires that session before clearing the transcript, and the next prompt starts a fresh session with a new session-scoped sandbox on first sandbox use. After a generation is superseded, `eve dev` retains it for at least 30 minutes and also retains the five most recently superseded generations, regardless of the configured Workflow World. The active generation is never pruned. Old runtime snapshots and local sandbox templates are pruned in the background. For manual cleanup, stop `eve dev` before deleting `.eve/dev-runtime/snapshots/` or `.eve/sandbox-cache/local/templates/`. A turn that remains unfinished beyond the automatic retention window can no longer resume after its generation is pruned. When no authored `agent/instrumentation.ts` exists, local dev also records traces under `.eve/traces/`, and bounds that store by age, size, and a keep-newest floor. Configure it with `EVE_TRACES*` in `.env.local`; see [`eve traces`](#retention) for the rules and defaults. ## `eve logs` ```bash eve logs # print the most recent diagnostic log eve logs ls # list logs, most recent first eve logs # print a specific log eve logs --dump # prepend the log's environment dump eve logs --events # interleave session events from the local workflow store ``` Each interactive `eve dev` process writes a private diagnostic log under `.eve/logs/` capturing stderr, stdout (including sandbox and rebuild lines), tool failures, workflow errors, and eve framework log records — regardless of what the transcript shows. The file is JSON Lines — every line is one JSON record with `at` and `source` fields. `eve logs` reads those files back. A log id is the file name without `.log` (for example `dev-2026-07-15T12-00-00.000Z-123`). `eve logs ` also accepts the file name, the `.eve/logs/...` path printed in the dev transcript, or any unambiguous prefix of the id with or without the `dev-` lead — so `eve logs 2026-07-15` works when a single log matches. An ambiguous prefix fails and lists the candidates. `eve logs` prints nothing but records — no path banner on either stream — so `eve logs 2>&1 | jq -c .` always parses. Discover ids and file paths with `eve logs ls`; `eve logs ls --json` emits a machine-readable array with `id`, `path`, `startedAt`, and `sizeBytes`. `eve logs --events` resolves session events (`session.started`, `turn.failed`, message deltas, …) from the local workflow store (`.eve/.workflow-data`) at query time and interleaves them into the output by timestamp as `source: "event"` records — the log file itself never stores them, so nothing is duplicated at capture time. Selection is by the log's time window (its start through the next log's start), so events from concurrently running `eve dev` processes may appear. Each log has a same-named `.dump` sibling holding environment diagnostics and session stats as one JSON document. `eve logs --dump` (with or without a log id) prepends that document to the JSONL log body; the combined output is a valid JSON value stream (`eve logs --dump | jq -c .`), one self-contained report to attach to an issue. When a log has no dump, the flag is silently a no-op. ## `eve traces` ```bash eve traces ls # list traces, most recent first eve traces ls --json # emit machine-readable trace summaries eve traces # show the most recent span tree eve traces # show one span tree eve traces --verbose # expand every span with all attributes and events eve traces --json # dump the full trace as JSON ``` Reads the immutable OTLP/JSON segments under `.eve/traces/v1`, so `eve dev` need not be running. Accepts a full trace id, a `gen_ai.conversation.id`, or an unambiguous prefix of either. Malformed segments are skipped without hiding valid spans from the same trace. Span rows carry inline metrics when the span recorded them — `↑input`/`↓output` token counts, gateway cost, and the tool name for `execute_tool` spans — and the header aggregates models, token totals, cost, and error count across the trace's step spans. `--verbose` expands each span under its tree row: status (with the error message on failures), timing, ids, every attribute (prompts, responses, and tool payloads as transcripts or pretty-printed JSON), and every span event with its offset from span start. `--json` prints the same records as JSON, one object per selected trace. Every subagent activation starts its own trace. The first child's `invoke_agent` root links to the dispatching caller with `eve.link.type=agent.dispatch`; remote agents preserve that caller in W3C `tracestate` even when HTTP `traceparent` advances through platform ingress. Later turns also start fresh traces without repeating the initial caller link. All related sessions retain the same `gen_ai.conversation.id`, and `agent.subagent.name` labels the child invocation. Each `agent()` call inside an authored workflow has its own `agent.action` caller span, including sequential, parallel, and background calls. A workflow tool that coordinates one of those calls has an enclosing `invoke_workflow ` span; a workflow tool without agent calls remains `agent.action`. The tool also keeps its `execute_tool ` span. Only agent execution uses `invoke_agent`. A durable conversation produces one bounded trace per turn. Worker replacements reuse the prepared context for the same turn, while a later turn or an independently replayed attempt starts a fresh trace. Passing the conversation ID shows every trace it produced, oldest first. Every span carries a real duration. A turn's root `invoke_agent` span is written when the turn settles, so a running turn shows only its steps. Model, `execute_tool`, and memory spans retain their content by default. Set `EVE_TRACES_CONTENT=off` to omit system prompts, prompt messages, and response text for models; call arguments and results for tools; and recalled memory records. Each captured value is capped at 32 KB. Step spans carry token counts under `agent.usage.*`, and cost when Vercel AI Gateway served the call. Model spans also expose `gen_ai.usage.*` token counters. The CLI sums step-level counters only, so model and delegated-call totals are not counted twice. ### Retention eve sweeps the store when an activation's writes finish, when a session finishes, and when the dev server starts. An open conversation does not pin every completed turn's trace. Sweeps evict oldest-first past the bounds below, except that active traces, the newest traces, and anything written in the last five minutes are kept. A sweep can therefore exceed the size budget. Set the bounds in `.env.local`, which `eve dev` loads automatically; each accepts `off` to disable it individually. | Variable | Default | Effect | | ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------------- | | `EVE_TRACES` | on | `off` stops writing traces and stops sweeping | | `EVE_TRACES_CONTENT` | on | `off` omits model prompt/response, tool input/output, and memory-record attributes on local spans | | `EVE_TRACES_MAX_AGE_MS` | `604800000` (7d) | Age after which a trace may be evicted | | `EVE_TRACES_MAX_TOTAL_BYTES` | `536870912` (512 MB) | Size budget for the whole store | | `EVE_TRACES_RETAIN_COUNT` | `20` | Newest traces kept regardless of age or size | ## `eve link` ```bash eve link eve link --non-interactive --project [--team ] ``` Links the current directory to a Vercel project. After selecting a team, you can create a project named for the agent or link an existing project. The existing-project picker shows recent projects; type a project name and choose **Search for ''** to search the rest of that team's projects. Vercel links the resolved project, eve verifies its project ID, and then pulls the project's environment so an AI Gateway credential (`VERCEL_OIDC_TOKEN` or `AI_GATEWAY_API_KEY`) lands in `.env.local`. Running it again re-links: the pickers always run, and the new choice wins. For CI or an agent, pass `--non-interactive` and `--project`. `--project` accepts the same Vercel project name or ID as `vercel link`; `--team` accepts its team ID or slug. The command never opens a picker or browser in this mode. A running `eve dev` reloads env files automatically, so you don't need to restart after the pull. ## `eve deploy` ```bash eve deploy eve deploy --non-interactive --yes [--project ] [--team ] ``` Deploys the agent to Vercel production (`vercel deploy --prod`), installing dependencies first and pulling environment variables after. An already-linked project deploys with or without a TTY. When a terminal is present, an unlinked deployment signs in to Vercel if needed and then walks the `eve link` pickers. For CI or an agent, pass `--non-interactive --yes`. `--yes` explicitly confirms the production deployment. With `--project`, eve links that Vercel project and pulls its environment before deploying; `--team` has the same ID-or-slug semantics as `eve link`. Without `--project`, the directory must already be linked. The non-interactive mode never opens a picker, browser, or login flow. ## `eve eval` ```bash eve eval [evalId...] [--url ] [options] ``` Runs all discovered evals when no eval ids are given; ids match exactly or by directory prefix (`eve eval weather` runs everything under `evals/weather/`). Exits `0` when every eval passed its checks, `1` when any eval failed (a failed check, an execution error, or a `--strict` threshold miss), `2` on configuration errors. | Flag | Type | Default | Description | | ------------------------ | ------ | ------- | ------------------------------------------------------------- | | `--url ` | string | none | Remote agent URL (skip local host startup) | | `--tag ` | string | none | Run only evals carrying a tag | | `--exclude-tag ` | string | none | Skip evals carrying a tag | | `--strict` | flag | off | Below-threshold scores also fail the exit code | | `--list` | flag | off | Print evals selected by the tag filters, without running them | | `--timeout ` | number | none | Per-eval timeout in milliseconds | | `--max-concurrency ` | number | 8 | Max concurrent eval executions | | `--json` | flag | off | Output results as JSON | | `--junit ` | string | none | Write JUnit XML results to a file | | `--skip-report` | flag | off | Skip eval-defined reporters (e.g. Braintrust) | | `--verbose` | flag | off | Stream per-eval logs and workflow run IDs to stdout | See [Evals](../evals/overview) for authoring evals. ## `eve channels list` ```bash eve channels list [--json] ``` Lists the user-authored channels in the current project. | Flag | Type | Default | Description | | -------- | ---- | ------- | -------------- | | `--json` | flag | off | Output as JSON | ## Recommended loop 1. Edit files under `agent/`. 2. `eve info` to confirm discovery or read diagnostics. 3. `eve dev` while iterating locally. 4. `eve build` before shipping. 5. `eve start` to smoke-test the built output locally. Related: [Project layout](../getting-started#project-layout) · [Instrumentation](../observability/instrumentation). ## What to read next * [Project layout](../getting-started#project-layout): what `eve info` discovers * [Instrumentation](../observability/instrumentation): tracing and the error catalog * [Deployment](../guides/deployment/overview): `eve build` and `eve start` in production --- For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md) For an index of all available documentation, see [/llms.txt](/llms.txt) For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)