# Development diagnostics

<!-- Generated by docs/modules/diagnostics from the package catalogs. Write a guide in docs/diagnostics/<CODE>.md instead of editing this file. -->

Each Development error has a stable `code`. Its `docs` link opens the page of that code. This page lists all 358 codes, and [All diagnostics](https://vitehub.dev/docs/reference/diagnostics) lists every primitive.

## Runtime errors

| Code | What happened |
| --- | --- |
| [`CLI_R0001`](https://vitehub.dev/docs/development/diagnostics/cli_r0001) | Nuxt config was found, but Nuxt could not be loaded for CLI discovery. |
| [`CLI_R0002`](https://vitehub.dev/docs/development/diagnostics/cli_r0002) | The installed @vite-hub/cli package manifest has no valid version. |
| [`CLI_R0003`](https://vitehub.dev/docs/development/diagnostics/cli_r0003) | --url must be a URL. |
| [`CLI_R0004`](https://vitehub.dev/docs/development/diagnostics/cli_r0004) | \<name\> changes or removes data and was not confirmed. |
| [`CLI_R0005`](https://vitehub.dev/docs/development/diagnostics/cli_r0005) | No dev server is running for \<value\>. |
| [`INTERNAL_R0001`](https://vitehub.dev/docs/development/diagnostics/internal_r0001) | Unknown ViteHub host: \<host\>. |
| [`INTERNAL_R0002`](https://vitehub.dev/docs/development/diagnostics/internal_r0002) | The \<host\> host cannot provide \<service\>. \<reason\> Configure an explicit portable implementation through the owner package or disable this capability. |
| [`INTERNAL_R0004`](https://vitehub.dev/docs/development/diagnostics/internal_r0004) | HTTP response exceeds the configured \<maxResponseBytes\>-byte limit. |
| [`INTERNAL_R0005`](https://vitehub.dev/docs/development/diagnostics/internal_r0005) | HTTP request method "\<method\>" is not supported. Use GET, HEAD, or POST. |
| [`INTERNAL_R0006`](https://vitehub.dev/docs/development/diagnostics/internal_r0006) | HTTP request timeout must be a positive finite number no greater than 2147483647. |
| [`INTERNAL_R0007`](https://vitehub.dev/docs/development/diagnostics/internal_r0007) | HTTP request maxResponseBytes must be a positive safe integer no greater than \<maximumHttpMaxResponseBytes\>. |
| [`INTERNAL_R0008`](https://vitehub.dev/docs/development/diagnostics/internal_r0008) | Invalid \<label\>: \<issues\> |
| [`INTERNAL_R0009`](https://vitehub.dev/docs/development/diagnostics/internal_r0009) | Invalid \<label\>: \<issues\> |
| [`INTERNAL_R0010`](https://vitehub.dev/docs/development/diagnostics/internal_r0010) | Cloudflare provisioning returned an invalid response. |
| [`INTERNAL_R0011`](https://vitehub.dev/docs/development/diagnostics/internal_r0011) | Invalid \<label\> app. Expected an h3 app or a fetch-compatible handler. |
| [`INTERNAL_R0012`](https://vitehub.dev/docs/development/diagnostics/internal_r0012) | HTTP request failed with status \<status\>. |
| [`INTERNAL_R0013`](https://vitehub.dev/docs/development/diagnostics/internal_r0013) | Provision request failed: \<method\> \<path\> (\<status\>).\<suffix\> |
| [`INTERNAL_R0014`](https://vitehub.dev/docs/development/diagnostics/internal_r0014) | Cannot read Provision State from "\<path\>". |
| [`INTERNAL_R0020`](https://vitehub.dev/docs/development/diagnostics/internal_r0020) | Operation \<name\> is invalid: \<reason\> |
| [`INTERNAL_R0021`](https://vitehub.dev/docs/development/diagnostics/internal_r0021) | No operation is named \<name\>. |
| [`INTERNAL_R0022`](https://vitehub.dev/docs/development/diagnostics/internal_r0022) | Invalid input for \<name\>. \<issues\> |
| [`INTERNAL_R0023`](https://vitehub.dev/docs/development/diagnostics/internal_r0023) | \<message\> \<fix\> |
| [`INTERNAL_R0024`](https://vitehub.dev/docs/development/diagnostics/internal_r0024) | See the page of the code. |
| [`INTERNAL_R0025`](https://vitehub.dev/docs/development/diagnostics/internal_r0025) | The server runs another project than the command expects. |
| [`INTERNAL_R0026`](https://vitehub.dev/docs/development/diagnostics/internal_r0026) | The server parsed a destructive operation that the CLI did not confirm. |
| [`RUNTIME_LEASE_FAILED`](https://vitehub.dev/docs/development/diagnostics/runtime_lease_failed) | The lease store could not \<operation\> the lease \<key\>. |
| [`RUNTIME_LEASE_INVALID_TTL`](https://vitehub.dev/docs/development/diagnostics/runtime_lease_invalid_ttl) | `ttl` must be a positive number of seconds. |
| [`RUNTIME_R0001`](https://vitehub.dev/docs/development/diagnostics/runtime_r0001) | Diagnostic error maxDepth must be a non-negative integer. |
| [`RUNTIME_R0002`](https://vitehub.dev/docs/development/diagnostics/runtime_r0002) | Diagnostic error maxErrors must be a positive integer. |
| [`RUNTIME_R0003`](https://vitehub.dev/docs/development/diagnostics/runtime_r0003) | Diagnostic error maxStringLength must be an integer of at least 64. |
| [`RUNTIME_R0004`](https://vitehub.dev/docs/development/diagnostics/runtime_r0004) | Process drain reported \<status\>. |
| [`RUNTIME_R0005`](https://vitehub.dev/docs/development/diagnostics/runtime_r0005) | Process \<pid\> exited before drain completed. |
| [`RUNTIME_R0006`](https://vitehub.dev/docs/development/diagnostics/runtime_r0006) | ViteHubError requires a valid public error contract. |
| [`RUNTIME_R0007`](https://vitehub.dev/docs/development/diagnostics/runtime_r0007) | Invalid execution authority descriptor. |
| [`RUNTIME_R0009`](https://vitehub.dev/docs/development/diagnostics/runtime_r0009) | Process reconciler intervalMs must be between 1 and 2,147,483,647 milliseconds. |
| [`RUNTIME_R0010`](https://vitehub.dev/docs/development/diagnostics/runtime_r0010) | Process reconciler signal \<configuredSignal\> cannot be handled. |
| [`RUNTIME_R0011`](https://vitehub.dev/docs/development/diagnostics/runtime_r0011) | Process reconciler callbacks cannot call drain() while active. |
| [`RUNTIME_R0015`](https://vitehub.dev/docs/development/diagnostics/runtime_r0015) | The event has no request, so ViteHub cannot set `~standard`. Pass the event of an H3 or Nitro route. |
| [`RUNTIME_R0016`](https://vitehub.dev/docs/development/diagnostics/runtime_r0016) | H3 does not read `~standard.res.body`. Return the body or a Response from the handler. |
| [`RUNTIME_R0017`](https://vitehub.dev/docs/development/diagnostics/runtime_r0017) | \<instancesEnvName\> is \<instances\>, but these primitives keep their state in one process or on one host. Each instance would see different data: |
| [`RUNTIME_R0018`](https://vitehub.dev/docs/development/diagnostics/runtime_r0018) | \<source\> must be a positive integer. It is \<value\>. |
| [`SKILL_NOT_FOUND`](https://vitehub.dev/docs/development/diagnostics/skill_not_found) | No skill or skill file at \<uri\>. |
| [`SKILL_SETTINGS_UNAVAILABLE`](https://vitehub.dev/docs/development/diagnostics/skill_settings_unavailable) | The skill settings store failed to \<action\> which skills are off. |
| [`VITE_HUB_R0001`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0001) | The Redis KV driver is unavailable because this ViteHub build does not configure a store that can use Redis. |
| [`VITE_HUB_R0040`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0040) | Cannot mount the ViteHub Console handler at "\<route\>" because the app route "\<handler\>" uses that path. Move the app route to another path. |
| [`VITE_HUB_R0041`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0041) | See the page of the code. |
| [`VITE_HUB_R0042`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0042) | The Console returned an invalid database inspection. |
| [`VITE_HUB_R0043`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0043) | The Console returned an invalid database inspection. |
| [`VITE_HUB_R0044`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0044) | The Console returned an invalid database inspection. |
| [`VITE_HUB_R0045`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0045) | Agent name \<name\> must be a non-empty trimmed string of at most 512 characters. |
| [`VITE_HUB_R0046`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0046) | See the page of the code. |
| [`VITE_HUB_R0047`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0047) | Console cannot inspect multiple Agent invocation journals. Configure one shared journal for the discovered Agent Definitions. |
| [`VITE_HUB_R0049`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0049) | Blob inspection has not been installed for this runtime. |
| [`VITE_HUB_R0050`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0050) | See the page of the code. |
| [`VITE_HUB_R0051`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0051) | Database inspection has not been installed for this runtime. |
| [`VITE_HUB_R0052`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0052) | See the page of the code. |
| [`VITE_HUB_R0053`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0053) | Invalid Agent name |
| [`VITE_HUB_R0054`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0054) | Invocation not found |
| [`VITE_HUB_R0058`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0058) | Invalid invocation cursor |
| [`VITE_HUB_R0059`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0059) | Too many invocation ids |
| [`VITE_HUB_R0060`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0060) | Invalid Agent name |
| [`VITE_HUB_R0061`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0061) | Invalid Capability id |
| [`VITE_HUB_R0062`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0062) | Invalid invocation limit |
| [`VITE_HUB_R0063`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0063) | This app has no Agent Invocation journal for the Console to read. The Console is off, or the app has no Agent Definition. |
| [`VITE_HUB_R0070`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0070) | Invalid Agent name |
| [`VITE_HUB_R0071`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0071) | Invalid usage window |
| [`VITE_HUB_R0072`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0072) | Invalid usage status |
| [`VITE_HUB_R0073`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0073) | Console invocation URLs require a request context or a `vitehub({ publicUrl })` origin. With several configured origins, the request host must be one of them. |
| [`VITE_HUB_R0074`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0074) | Console invocation URLs require an invocation with agentName and id. |
| [`VITE_HUB_R0075`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0075) | Blob is unavailable for this host. Configure an explicit Blob store before using Blob APIs or Agent Capabilities. |
| [`VITE_HUB_R0076`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0076) | vitehub name must contain at least one letter or number. |
| [`VITE_HUB_R0077`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0077) | WRANGLER_CI_OVERRIDE_NAME must contain at least one letter or number. |
| [`VITE_HUB_R0078`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0078) | deployment identity \<configured\> conflicts with WRANGLER_CI_OVERRIDE_NAME=\<workersBuildsName\>. |
| [`VITE_HUB_R0079`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0079) | See the page of the code. |
| [`VITE_HUB_R0080`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0080) | See the page of the code. |
| [`VITE_HUB_R0081`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0081) | See the page of the code. |
| [`VITE_HUB_R0082`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0082) | See the page of the code. |
| [`VITE_HUB_R0083`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0083) | See the page of the code. |
| [`VITE_HUB_R0084`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0084) | See the page of the code. |
| [`VITE_HUB_R0085`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0085) | vitehub() requires an options object. |
| [`VITE_HUB_R0087`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0087) | The "deno" host cannot deploy the Agent Deno runtime because its generated server is outside the deployed Nitro entrypoint. Use the host's Nitro runtime or compose an explicit Deno Agent deployment. |
| [`VITE_HUB_R0088`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0088) | Browser currently requires the Cloudflare host. |
| [`VITE_HUB_R0089`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0089) | email: true currently requires the Cloudflare host; configure an explicit Email driver for other hosts. |
| [`VITE_HUB_R0095`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0095) | The Console returned invalid Blob metadata. |
| [`VITE_HUB_R0096`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0096) | The Console returned an invalid Blob object. |
| [`VITE_HUB_R0097`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0097) | The Console returned an invalid Blob page. |
| [`VITE_HUB_R0098`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0098) | The Console returned an invalid Rate Limit result. |
| [`VITE_HUB_R0101`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0101) | See the page of the code. |
| [`VITE_HUB_R0102`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0102) | The Agent invocation response did not include an id. |
| [`VITE_HUB_R0103`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0103) | See the page of the code. |
| [`VITE_HUB_R0104`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0104) | See the page of the code. |
| [`VITE_HUB_R0106`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0106) | See the page of the code. |
| [`VITE_HUB_R0107`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0107) | See the page of the code. |
| [`VITE_HUB_R0108`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0108) | See the page of the code. |
| [`VITE_HUB_R0109`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0109) | See the page of the code. |
| [`VITE_HUB_R0113`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0113) | Invalid Agent name. |
| [`VITE_HUB_R0114`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0114) | Agent status is unavailable. |
| [`VITE_HUB_R0115`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0115) | Invalid usage cursor |
| [`VITE_HUB_R0116`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0116) | History requires user or assistant messages. |
| [`VITE_HUB_R0117`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0117) | History requires text or attachment parts. |
| [`VITE_HUB_R0118`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0118) | History message ids must be unique. |
| [`VITE_HUB_R0120`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0120) | dataDir requires the node host and a persistent filesystem. Configure remote stores for other hosts. |
| [`VITE_HUB_R0121`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0121) | dataDir must be a non-empty directory path. |
| [`VITE_HUB_R0124`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0124) | connections requires database because grants and activity are stored in the app database. Remove `database: false`. |
| [`VITE_HUB_R0125`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0125) | observability.service must be a non-empty service name. |
| [`VITE_HUB_R0126`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0126) | observability.posthog reads its API key from Server Env. Remove env: false. |
| [`VITE_HUB_R0127`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0127) | observability.papercuts stores reports in the Console invocation journal. Enable agent and console. |
| [`VITE_HUB_R0128`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0128) | env.server.observability is reserved for vitehub({ observability }). |
| [`VITE_HUB_R0129`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0129) | observability currently requires Nitro-hosted Agents. Netlify and Deno Agent output are not supported. |
| [`VITE_HUB_R0131`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0131) | agent.invocations "database" requires database. Set database in vitehub(). |
| [`VITE_HUB_R0132`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0132) | agent.invocations requires Nitro-hosted Agents. Netlify and Deno Agent output are not supported. Set agent.invocations to false and configure invocations on each Agent Definition. |
| [`VITE_HUB_R0135`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0135) | This version of Nitro cannot run after vitehub() when nitro() comes first. Put vitehub() before nitro() in plugins. |
| [`VITE_HUB_R0136`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0136) | \<value\> Install them in your app with: pnpm add \<value\> |
| [`VITE_HUB_R0137`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0137) | The "node" host has no cron, so this build would never run its Schedules. Set schedule: { runtime: { driver: "process" }, providerOutput: "auto" } to run them in the server process, or schedule: { providerOutput: false } to wake them yourself. |
| [`VITE_HUB_R0141`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0141) | queue.driver "\<driver\>" works with the "node" host only. The "\<host\>" host uses its own Queue. Remove queue.driver, or use the "node" host. |
| [`VITE_HUB_R0142`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0142) | See the page of the code. |
| [`VITE_HUB_R0143`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0143) | This server has no durability report. ViteHub records it when a Node server starts. |
| [`VITE_HUB_R0144`](https://vitehub.dev/docs/development/diagnostics/vite_hub_r0144) | rateLimit.driver "kv" works with the "node" host only. The "\<host\>" host uses its own Rate Limit. Remove rateLimit.driver, or use the "node" host. |

## Configuration errors

| Code | What happened |
| --- | --- |
| [`INTERNAL_C0001`](https://vitehub.dev/docs/development/diagnostics/internal_c0001) | Duplicate \<sourceLabel\> name "\<name\>":   - \<handler\>   - \<handler\> |
| [`INTERNAL_C0002`](https://vitehub.dev/docs/development/diagnostics/internal_c0002) | Duplicate \<feature\> name "\<name\>" from multiple discovery sources:   - \<handler\> (\<value\>)   - \<handler\> (\<value\>) |
| [`VITE_HUB_C0001`](https://vitehub.dev/docs/development/diagnostics/vite_hub_c0001) | Env section not found. |
| [`VITE_HUB_C0002`](https://vitehub.dev/docs/development/diagnostics/vite_hub_c0002) | Definition inspection has not been installed for this runtime. |
| [`VITE_HUB_C0003`](https://vitehub.dev/docs/development/diagnostics/vite_hub_c0003) | `cache: true` has no default store for the \<host\> host. Remove `cache` or use a host that provides one. |
| [`VITE_HUB_C0004`](https://vitehub.dev/docs/development/diagnostics/vite_hub_c0004) | `cache.driver` is \<driver\>. ViteHub renamed this driver to "\<renamed\>", and it does not read \<driver\>. |

## Build errors

| Code | What happened |
| --- | --- |
| [`INTERNAL_B0001`](https://vitehub.dev/docs/development/diagnostics/internal_b0001) | Cloudflare \<identityKey\> \<identity\> from \<owner\> is already assigned to an incompatible resource. |
| [`INTERNAL_B0015`](https://vitehub.dev/docs/development/diagnostics/internal_b0015) | Deno output imports \<name\> from multiple package installations. Bundle one version before deployment. |
| [`INTERNAL_B0016`](https://vitehub.dev/docs/development/diagnostics/internal_b0016) | Expected package.json to contain an object. |
| [`INTERNAL_B0017`](https://vitehub.dev/docs/development/diagnostics/internal_b0017) | Expected package.json \<key\> to contain strings. |
| [`INTERNAL_B0018`](https://vitehub.dev/docs/development/diagnostics/internal_b0018) | Expected package.json \<key\> to contain string values. |
| [`INTERNAL_B0019`](https://vitehub.dev/docs/development/diagnostics/internal_b0019) | Expected package.json peerDependenciesMeta to contain an object. |
| [`INTERNAL_B0020`](https://vitehub.dev/docs/development/diagnostics/internal_b0020) | Expected package.json name to contain a string. |
| [`INTERNAL_B0021`](https://vitehub.dev/docs/development/diagnostics/internal_b0021) | See the page of the code. |
| [`INTERNAL_B0022`](https://vitehub.dev/docs/development/diagnostics/internal_b0022) | Conflicting runtime package installations for \<name\>: \<path\> and \<resolvedPackageJsonPath\>. |
| [`INTERNAL_B0025`](https://vitehub.dev/docs/development/diagnostics/internal_b0025) | Deno \<outputName\> contains an unsupported computed local import \<specifier\>. Use a static import so ViteHub can bundle its dependency. |
| [`INTERNAL_B0026`](https://vitehub.dev/docs/development/diagnostics/internal_b0026) | Deno \<outputName\> contains an unsupported computed import. Use a static import so ViteHub can bundle its dependency. |
| [`INTERNAL_B0027`](https://vitehub.dev/docs/development/diagnostics/internal_b0027) | Deno \<outputName\> contains an unsupported computed require. Use a static import so ViteHub can bundle its dependency. |
| [`INTERNAL_B0028`](https://vitehub.dev/docs/development/diagnostics/internal_b0028) | Deno deployment output \<outputDir\> is already being finalized by process \<owner\>. |
| [`INTERNAL_B0029`](https://vitehub.dev/docs/development/diagnostics/internal_b0029) | Could not acquire the Deno deployment output lock for \<outputDir\>. |
| [`INTERNAL_B0031`](https://vitehub.dev/docs/development/diagnostics/internal_b0031) | Deno Schedule output requires the project-root "main.ts" application entrypoint to import "./schedule/deno-cron.mjs". |
| [`INTERNAL_B0032`](https://vitehub.dev/docs/development/diagnostics/internal_b0032) | Deno Schedule output requires the project-root "main.ts" application entrypoint to import "./server/index.mjs". |
| [`INTERNAL_B0035`](https://vitehub.dev/docs/development/diagnostics/internal_b0035) | Invalid Provider Output ownership file schema: \<fileName\> |
| [`INTERNAL_B0039`](https://vitehub.dev/docs/development/diagnostics/internal_b0039) | Provider Output finalization reset |
| [`INTERNAL_B0040`](https://vitehub.dev/docs/development/diagnostics/internal_b0040) | See the page of the code. |
| [`INTERNAL_B0043`](https://vitehub.dev/docs/development/diagnostics/internal_b0043) | Provider output config must be a JSON object. |
| [`INTERNAL_B0046`](https://vitehub.dev/docs/development/diagnostics/internal_b0046) | Could not resolve package.json for \<name\>. |
| [`INTERNAL_B0047`](https://vitehub.dev/docs/development/diagnostics/internal_b0047) | Expected \<path\> to contain a JSON object. |
| [`INTERNAL_B0048`](https://vitehub.dev/docs/development/diagnostics/internal_b0048) | \<owner\> sets vitehub.operations, which must be a list of { module, export }. |
| [`INTERNAL_B0049`](https://vitehub.dev/docs/development/diagnostics/internal_b0049) | The operations \<name\> and \<name\> are both the CLI command `vitehub <key>`. |
| [`INTERNAL_B0050`](https://vitehub.dev/docs/development/diagnostics/internal_b0050) | The operations \<name\> and \<name\> are both the MCP tool \<tool\>. |
| [`INTERNAL_B0051`](https://vitehub.dev/docs/development/diagnostics/internal_b0051) | The Cloudflare \<path\> entry "\<name\>"\<scope\> is written by ViteHub and by the project's Wrangler config with a different \<field\>: \<generated\> and \<project\>. |
| [`INTERNAL_B0052`](https://vitehub.dev/docs/development/diagnostics/internal_b0052) | The column "\<column\>" of the Console section "\<section\>" needs both `format: "switch"` and a `switch` operation name such as "skills.set". |
| [`VITE_HUB_B0001`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0001) | Could not locate the packaged Console runtime. |
| [`VITE_HUB_B0004`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0004) | console must be true, false, or an options object, such as console: { authorize: "./server/console-authorize.ts" }. |
| [`VITE_HUB_B0005`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0005) | console.impersonation needs app Auth. Set auth: true and add server/auth.ts with Better Auth's admin plugin, or remove console.impersonation. |
| [`VITE_HUB_B0008`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0008) | Cannot auto-import \<name\> from \<from\> because it is already configured from \<from\>. |
| [`VITE_HUB_B0009`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0009) | See the page of the code. |
| [`VITE_HUB_B0011`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0011) | Env projectRoot \<configuredEnvProjectRootOption\> conflicts with the installed Env Vite plugin. |
| [`VITE_HUB_B0012`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0012) | vitehub({ observability }) requires the evlog package. Install evlog. |
| [`VITE_HUB_B0013`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0013) | Database is disabled but \<value\> imports \<specifier\>. \<enableDatabase\> |
| [`VITE_HUB_B0015`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0015) | \<message\> |
| [`VITE_HUB_B0016`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0016) | agent.invocations.retention.maxSize is not supported by the D1 journal, because D1 reports the size of the whole app database. Use maxAge or maxRecords, or set agent.invocations.databaseUrl to a SQLite file. |
| [`VITE_HUB_B0018`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0018) | Comments keeps its threads in the Database, and the `comments` option turns Comments on, but `database` is false. Remove `database: false`, or set `comments: false`. |
| [`VITE_HUB_B0019`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0019) | `comments: false` turns Comments off, but the app has \<file\>. Remove the file, or remove `comments: false`. |
| [`VITE_HUB_B0020`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0020) | console.\<key\> was removed. \<fix\> |
| [`VITE_HUB_B0021`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0021) | agent.invocations.databaseUrl is a local file, which a Cloudflare Worker cannot open. Remove it to use the D1 binding of the default Database, or set a remote libSQL URL. |
| [`VITE_HUB_B0022`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0022) | console.auth false is for development. Remove console.auth so the app takes only signed calls, and set the VITEHUB_CONSOLE_KEY_\<NAME\> line that the ViteHub Console shows when you link the app (or that vitehub secret console-key prints). |
| [`VITE_HUB_B0023`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0023) | vite-hub/nuxt needs Nuxt 5, which runs Nitro 3 and H3 2. This app runs Nuxt \<version\>. Until Nuxt 5 is stable, install the nightly release: pnpm add nuxt@npm:nuxt-nightly@5x |
| [`VITE_HUB_B0024`](https://vitehub.dev/docs/development/diagnostics/vite_hub_b0024) | `<key>` in \<where\> is no longer a ViteHub option. \<why\> \<fix\> |

## Errors

| Code | What happened |
| --- | --- |
| [`BUNDLE_HOST_SIZE_LIMIT`](https://vitehub.dev/docs/development/diagnostics/bundle_host_size_limit) | The server JavaScript is \<bytes\> before compression. Cloudflare rejects a Worker over \<limit\> (64 MiB), and the deployment also counts files other than JavaScript. |
| [`BUNDLE_STARTUP_UNUSED`](https://vitehub.dev/docs/development/diagnostics/bundle_startup_unused) | \<value\> \<value\> at server startup. \<reason\> |
| [`CACHE_DRIVER_WRONG_HOST`](https://vitehub.dev/docs/development/diagnostics/cache_driver_wrong_host) | `cache.driver: "<driver>"` needs the \<required\> host, but the host is \<host\>. |
| [`CACHE_INVALID_INPUT`](https://vitehub.dev/docs/development/diagnostics/cache_invalid_input) | See the page of the code. |
| [`CACHE_KV_DISABLED`](https://vitehub.dev/docs/development/diagnostics/cache_kv_disabled) | `cache.driver: "kv"` keeps the Nitro cache in KV, but `kv` is not enabled. |
| [`CACHE_NAMESPACE_ID_CONFLICT`](https://vitehub.dev/docs/development/diagnostics/cache_namespace_id_conflict) | The Cloudflare cache binding "\<binding\>" already uses the KV namespace "\<existing\>", but `cache.namespaceId` asks for "\<requested\>". |
| [`CACHE_NAMESPACE_ID_MISSING`](https://vitehub.dev/docs/development/diagnostics/cache_namespace_id_missing) | The Cloudflare cache binding "\<binding\>" has no KV namespace ID. |
| [`CACHE_STORAGE_FAILED`](https://vitehub.dev/docs/development/diagnostics/cache_storage_failed) | See the page of the code. |
| [`CLI_CONSOLE_LOGIN_FAILED`](https://vitehub.dev/docs/development/diagnostics/cli_console_login_failed) | Sign-in to \<console\> did not finish. \<message\> |
| [`CLI_CONSOLE_SIGNED_OUT`](https://vitehub.dev/docs/development/diagnostics/cli_console_signed_out) | There is no valid API key for \<console\>. The key is missing, expired, or revoked. |
| [`CLI_ENV_FILE_EXISTS`](https://vitehub.dev/docs/development/diagnostics/cli_env_file_exists) | \<file\> exists. `vitehub env pull` does not replace a file without --yes. |
| [`CLI_ENV_FILE_NOT_IGNORED`](https://vitehub.dev/docs/development/diagnostics/cli_env_file_not_ignored) | \<file\> is not in .gitignore, so the values could be committed. |
| [`CLI_ENV_PULL_FAILED`](https://vitehub.dev/docs/development/diagnostics/cli_env_pull_failed) | The Console refused the pull (\<code\>). \<message\> |
| [`CLI_HOST_RESPONSE_INVALID`](https://vitehub.dev/docs/development/diagnostics/cli_host_response_invalid) | The \<host\> API returned an unexpected response. |
| [`CLI_SETUP_FAILED`](https://vitehub.dev/docs/development/diagnostics/cli_setup_failed) | See the page of the code. |
| [`CONSOLE_ACCESS_DENIED`](https://vitehub.dev/docs/development/diagnostics/console_access_denied) | The Console access policy rejected this account. |
| [`CONSOLE_ACCESS_NOT_CONFIGURED`](https://vitehub.dev/docs/development/diagnostics/console_access_not_configured) | Console access is not configured. The server has no Console access policy. |
| [`CONSOLE_APP_VITEHUB_OUTDATED`](https://vitehub.dev/docs/development/diagnostics/console_app_vitehub_outdated) | The app runs vite-hub \<version\>, which does not accept this call of the ViteHub MCP. An older app knows fewer fields of the signed caller. |
| [`CONSOLE_CONFLICT`](https://vitehub.dev/docs/development/diagnostics/console_conflict) | The data changed after the Console loaded it. |
| [`CONSOLE_DEVELOPMENT_ONLY`](https://vitehub.dev/docs/development/diagnostics/console_development_only) | The Console endpoint without Console options runs only on the development server. |
| [`CONSOLE_ENV_KEY_MISSING`](https://vitehub.dev/docs/development/diagnostics/console_env_key_missing) | A key that this Console does not have sealed \<name\> of \<stage\>, so it cannot open the value. VITEHUB_CONSOLE_ENV_KEY or VITEHUB_CONSOLE_ENV_KEYS does not hold that key. |
| [`CONSOLE_FORWARD_RATE_LIMITED`](https://vitehub.dev/docs/development/diagnostics/console_forward_rate_limited) | You sent \<limit\> calls to this app through the Console in one minute, which is the most that the Console sends for one person. The next call can go in \<retryAfter\> seconds. |
| [`CONSOLE_KEY_MALFORMED`](https://vitehub.dev/docs/development/diagnostics/console_key_malformed) | A `VITEHUB_CONSOLE_KEY_<NAME>` variable is not an Ed25519 public key. |
| [`CONSOLE_KEY_NOT_CONFIGURED`](https://vitehub.dev/docs/development/diagnostics/console_key_not_configured) | `console: true` needs a `VITEHUB_CONSOLE_KEY_<NAME>` variable in the server environment. |
| [`CONSOLE_KEY_UNKNOWN`](https://vitehub.dev/docs/development/diagnostics/console_key_unknown) | The app has no public key with the name that the signature names. |
| [`CONSOLE_LOOPBACK_ONLY`](https://vitehub.dev/docs/development/diagnostics/console_loopback_only) | The development Console without signed calls accepts only requests from this machine. |
| [`CONSOLE_MCP_AUTHORIZATION_FAILED`](https://vitehub.dev/docs/development/diagnostics/console_mcp_authorization_failed) | The OAuth sign-in with the MCP server failed. |
| [`CONSOLE_MCP_KEY_INVALID`](https://vitehub.dev/docs/development/diagnostics/console_mcp_key_invalid) | VITEHUB_CONSOLE_MCP_KEY is not 32 random bytes, so the Console cannot seal MCP connections. |
| [`CONSOLE_MCP_KV_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/console_mcp_kv_required) | VITEHUB_CONSOLE_MCP_KEY is set, but the app has no configured default KV store for MCP connections. |
| [`CONSOLE_MCP_SIGNED_OUT`](https://vitehub.dev/docs/development/diagnostics/console_mcp_signed_out) | The MCP server rejects the credentials of this connection. |
| [`CONSOLE_MCP_UNREACHABLE`](https://vitehub.dev/docs/development/diagnostics/console_mcp_unreachable) | The MCP server did not answer, or it failed the MCP handshake. |
| [`CONSOLE_NOT_FOUND`](https://vitehub.dev/docs/development/diagnostics/console_not_found) | The item does not exist, or the server removed it. |
| [`CONSOLE_ORIGIN_REJECTED`](https://vitehub.dev/docs/development/diagnostics/console_origin_rejected) | The request did not come from the Console origin. |
| [`CONSOLE_REQUEST_FAILED`](https://vitehub.dev/docs/development/diagnostics/console_request_failed) | The server could not complete the request. |
| [`CONSOLE_REQUEST_INVALID`](https://vitehub.dev/docs/development/diagnostics/console_request_invalid) | The server cannot read this Console request. |
| [`CONSOLE_SIGN_IN_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/console_sign_in_required) | You are not signed in, or your session ended. |
| [`CONSOLE_SIGNATURE_BODY`](https://vitehub.dev/docs/development/diagnostics/console_signature_body) | The request body is not the body that was signed. |
| [`CONSOLE_SIGNATURE_INVALID`](https://vitehub.dev/docs/development/diagnostics/console_signature_invalid) | The signature does not match the request. |
| [`CONSOLE_SIGNATURE_MISSING`](https://vitehub.dev/docs/development/diagnostics/console_signature_missing) | This app takes only signed Console requests, and this request is not signed. |
| [`CONSOLE_SIGNATURE_ORIGIN`](https://vitehub.dev/docs/development/diagnostics/console_signature_origin) | The request was signed for another origin, or the app has no trusted origin. |
| [`CONSOLE_SIGNATURE_STALE`](https://vitehub.dev/docs/development/diagnostics/console_signature_stale) | The request was signed more than 5 minutes before or after the app clock. |
| [`CONSOLE_SITE_SECRET_MISSING`](https://vitehub.dev/docs/development/diagnostics/console_site_secret_missing) | Site access without Auth seals the browser's cookie with VITEHUB_SECRET, and the app has none. |
| [`CONSOLE_TICKET_INVALID`](https://vitehub.dev/docs/development/diagnostics/console_ticket_invalid) | This one-time link expired, was used, or was changed. |
| [`CONSOLE_TICKET_MISMATCH`](https://vitehub.dev/docs/development/diagnostics/console_ticket_mismatch) | This one-time link was made for another person or another app. |
| [`CONSOLE_TICKET_NO_PERSON`](https://vitehub.dev/docs/development/diagnostics/console_ticket_no_person) | A one-time link opens the app as the person who asks for it, and this call names no person. A `vitehub` command signs its calls with a key, not as a person. |
| [`CONSOLE_TICKET_STORE_MISSING`](https://vitehub.dev/docs/development/diagnostics/console_ticket_store_missing) | One-time links need a store that every instance of the app shares, and the app has none. |
| [`CONSOLE_UNAVAILABLE`](https://vitehub.dev/docs/development/diagnostics/console_unavailable) | The server did not answer. It can be restarting, offline, or rate limited. |
| [`INTERNAL_INVARIANT_FAILED`](https://vitehub.dev/docs/development/diagnostics/internal_invariant_failed) | ViteHub reached a state that it does not expect: \<what\> |
| [`LOGS_CURSOR_EXPIRED`](https://vitehub.dev/docs/development/diagnostics/logs_cursor_expired) | The log cursor has expired. Refresh to read the retained events. |
| [`RUNTIME_HOST_BINDING_NOT_FOUND`](https://vitehub.dev/docs/development/diagnostics/runtime_host_binding_not_found) | The Worker has no binding named "\<name\>". |
| [`RUNTIME_HOST_BINDINGS_UNAVAILABLE`](https://vitehub.dev/docs/development/diagnostics/runtime_host_bindings_unavailable) | This code runs without host bindings, so the binding "\<name\>" is not available. Only Cloudflare Workers give bindings. |
| [`SEO_PUBLIC_URL_MISSING`](https://vitehub.dev/docs/development/diagnostics/seo_public_url_missing) | The build prerenders `<route>`, which holds full URLs, but `publicUrl` is not set to one origin. A prerendered file has no request to take the origin from. |
| [`SEO_SITEMAP_ENTRY_INVALID`](https://vitehub.dev/docs/development/diagnostics/seo_sitemap_entry_invalid) | `server/sitemap.ts` returned an entry that is not a page: \<entry\>. |
| [`SEO_SITEMAP_ROUTE_EXISTS`](https://vitehub.dev/docs/development/diagnostics/seo_sitemap_route_exists) | `seo.sitemap` serves `/sitemap.xml`, but the app has its own server route for `/sitemap.xml`. |
| [`SEO_SITEMAP_TOO_LARGE`](https://vitehub.dev/docs/development/diagnostics/seo_sitemap_too_large) | The sitemap has \<count\> URLs, but one sitemap file holds at most \<limit\>. |
| [`SERVED_SKILLS_INVALID_EXPORT`](https://vitehub.dev/docs/development/diagnostics/served_skills_invalid_export) | `server/skills.ts` exports no skills. |
| [`SERVED_SKILLS_NO_SETTINGS`](https://vitehub.dev/docs/development/diagnostics/served_skills_no_settings) | The skills of `server/skills.ts` have no switches. |
| [`SERVED_SKILLS_UNAVAILABLE`](https://vitehub.dev/docs/development/diagnostics/served_skills_unavailable) | This runtime has no `server/skills.ts`. |
| [`SETUP_CONFIG_MANUAL`](https://vitehub.dev/docs/development/diagnostics/setup_config_manual) | ViteHub cannot edit the vitehub() options in \<file\> without running the config (\<reason\>). |
| [`SETUP_CONFIG_NOT_LITERAL`](https://vitehub.dev/docs/development/diagnostics/setup_config_not_literal) | The vitehub() options in \<file\> cannot be read without running the config (\<reason\>). |
| [`SETUP_DEPLOY_BUILD_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_build_failed) | `<command>` exited with code \<exitCode\>. |
| [`SETUP_DEPLOY_CHECK_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_check_failed) | The app is deployed to \<url\>, but a `deploy.check` path did not answer with a 2xx status: \<failed\>. |
| [`SETUP_DEPLOY_CHECKOUT_CONFLICT`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_checkout_conflict) | A checkout folder of vitehub.lock has unresolved conflicts, so the Workspace push after the deploy would fail. Nothing was built or deployed: \<files\> |
| [`SETUP_DEPLOY_CHECKOUT_MODULE_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_checkout_module_failed) | The project installs \<specifier\>, but ViteHub cannot load it from \<file\>, so it cannot push the checkout folders of vitehub.lock. Nothing was built or deployed: \<message\> |
| [`SETUP_DEPLOY_COMMAND_REJECTED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_command_rejected) | The build output names a deploy command that ViteHub did not write, so it does not run it: \<command\> |
| [`SETUP_DEPLOY_CREDENTIALS_MISSING`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_credentials_missing) | No \<host\> credentials were found in the environment or in the host CLI login. |
| [`SETUP_DEPLOY_ENV_MISSING`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_env_missing) | The app needs \<names\>, and no value was found. This is the first deploy to \<host\>: the project is not linked, so the host has no variables yet and every required name needs a local value for the \<stage\> stage. Nothing was deployed. |
| [`SETUP_DEPLOY_ENV_NOT_LINKED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_env_not_linked) | The \<host\> project is not linked, so deploy cannot set \<names\> before the first deploy. Nothing was deployed. |
| [`SETUP_DEPLOY_ENV_STAGE_UNSAFE`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_env_stage_unsafe) | These existing Cloudflare secrets have no local value for stage \<stage\>: \<names\>. The latest uploaded version may belong to another stage, so inheriting its values is unsafe. Nothing was deployed. |
| [`SETUP_DEPLOY_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_failed) | `<step>` failed\<value\>.\<value\> |
| [`SETUP_DEPLOY_HOST_MISMATCH`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_host_mismatch) | The build output is for \<built\>, but this deploy goes to \<host\>. |
| [`SETUP_DEPLOY_HOST_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_host_unsupported) | `vitehub deploy` has no upload for the \<host\> host. |
| [`SETUP_DEPLOY_ORG_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_org_required) | The Deno Deploy organization is not known. |
| [`SETUP_DEPLOY_OUTPUT_MISSING`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_output_missing) | The build output has no \<file\>. |
| [`SETUP_DEPLOY_PREVIEW_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_preview_unsupported) | The \<host\> deploy that the build writes always deploys to production. |
| [`SETUP_DEPLOY_PROVISION_NEEDS_BUILD`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_provision_needs_build) | The deploy must create or change \<count\> resources, but --no-build deploys an output that was built without their ids. Nothing was created or deployed. |
| [`SETUP_DEPLOY_PROVISION_UNCHECKED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_provision_unchecked) | The deploy could not check the \<host\> resources of the app, so it created and deployed nothing: \<warnings\> \<missing\> |
| [`SETUP_DEPLOY_PUSH_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_push_failed) | The app is deployed to \<url\>, but the Workspace push failed: \<message\> |
| [`SETUP_DEPLOY_TEMPORARY_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_deploy_temporary_unsupported) | --temporary cannot run here. \<reason\> |
| [`SETUP_DEPLOYMENTS_ACCOUNT_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_deployments_account_required) | The \<host\> account of the linked project is not known. |
| [`SETUP_DEPLOYMENTS_CREDENTIALS_MISSING`](https://vitehub.dev/docs/development/diagnostics/setup_deployments_credentials_missing) | No \<host\> credentials were found in the environment or in the host CLI login, so the deployments cannot be read. |
| [`SETUP_DEPLOYMENTS_NOT_LINKED`](https://vitehub.dev/docs/development/diagnostics/setup_deployments_not_linked) | The project has no \<host\> target in .vitehub/link.json, so the host project to read is not known. |
| [`SETUP_DEPLOYMENTS_PROJECT_ID_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_deployments_project_id_required) | The \<host\> link has no project id, and the \<host\> API lists deployments by id. |
| [`SETUP_ENV_DECRYPT_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_env_decrypt_failed) | \<key\> cannot decrypt \<name\> in \<file\> (\<reason\>). |
| [`SETUP_ENV_FILE_NOT_IGNORED`](https://vitehub.dev/docs/development/diagnostics/setup_env_file_not_ignored) | The secret \<names\> reads \<file\>, which git does not ignore, so a commit can add it. `vitehub env push` pushes a secret only from a file that git ignores. |
| [`SETUP_ENV_FILE_TRACKED`](https://vitehub.dev/docs/development/diagnostics/setup_env_file_tracked) | The secret \<names\> reads \<file\>, which git tracks, directly or through `$NAME` expansion or a symlink. `vitehub env push` does not push a secret that is in git. |
| [`SETUP_ENV_GIT_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_env_git_failed) | Git could not tell whether it tracks or ignores \<file\>, which holds a secret: \<reason\>. Nothing was pushed. |
| [`SETUP_ENV_KEYS_TRACKED`](https://vitehub.dev/docs/development/diagnostics/setup_env_keys_tracked) | \<file\> holds the private keys of the encrypted env files and is tracked by git. `vitehub env push` does not decrypt with a key that is in git. |
| [`SETUP_ENV_NAME_UNKNOWN`](https://vitehub.dev/docs/development/diagnostics/setup_env_name_unknown) | The build output lists no variable named \<names\>. |
| [`SETUP_ENV_PRIVATE_KEY_MISSING`](https://vitehub.dev/docs/development/diagnostics/setup_env_private_key_missing) | \<file\> holds the encrypted \<names\>, and \<key\> is not set. |
| [`SETUP_ENV_STAGE_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_env_stage_unsupported) | The \<host\> host has no environment for the \<stage\> stage. |
| [`SETUP_ENV_VALUE_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_env_value_unsupported) | The value of \<name\> cannot go to \<host\> without a terminal prompt or argv. \<reason\> |
| [`SETUP_FEATURE_IMPLIED`](https://vitehub.dev/docs/development/diagnostics/setup_feature_implied) | \<feature\> stays on because \<by\> turns it on. |
| [`SETUP_FEATURE_IN_USE`](https://vitehub.dev/docs/development/diagnostics/setup_feature_in_use) | The app still uses \<features\>: \<references\> |
| [`SETUP_FEATURE_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_feature_required) | \<feature\> is required by the configured options of \<by\>. |
| [`SETUP_FEATURE_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_feature_unsupported) | \<feature\> is not supported on the \<host\> host. \<detail\> |
| [`SETUP_FILE_EXISTS`](https://vitehub.dev/docs/development/diagnostics/setup_file_exists) | \<file\> already defines a \<definition\> Definition that conflicts with \<starter\>, so the build would reject both. |
| [`SETUP_GITHUB_REPOSITORY_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_github_repository_required) | The git remote origin (\<remote\>) is not a github.com repository. |
| [`SETUP_GITHUB_REQUEST_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_github_request_failed) | GitHub refused `<operation>`: \<reason\> |
| [`SETUP_INIT_DIR_NOT_EMPTY`](https://vitehub.dev/docs/development/diagnostics/setup_init_dir_not_empty) | \<dir\> is not empty and holds no Vite or Nuxt app. ViteHub never overwrites a file. |
| [`SETUP_INIT_FRAMEWORK_MISMATCH`](https://vitehub.dev/docs/development/diagnostics/setup_init_framework_mismatch) | \<dir\> holds a \<found\> app, not a \<framework\> app. |
| [`SETUP_INIT_HOST_MIGRATION`](https://vitehub.dev/docs/development/diagnostics/setup_init_host_migration) | init cannot change an enabled ViteHub stack to the \<host\> host. |
| [`SETUP_INIT_NUXT_VERSION`](https://vitehub.dev/docs/development/diagnostics/setup_init_nuxt_version) | \<dir\> does not declare a known Nuxt 5 version. ViteHub did not adopt it. |
| [`SETUP_INPUT_NEEDED`](https://vitehub.dev/docs/development/diagnostics/setup_input_needed) | Set \<fields\> to add \<value\> on the \<host\> host. |
| [`SETUP_INSTALL_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_install_failed) | `<command>` exited with code \<exitCode\>. |
| [`SETUP_LINK_ACCOUNT_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_link_account_required) | The Cloudflare token has access to \<count\> accounts, so the account to link is not clear. |
| [`SETUP_LINK_CREDENTIALS_MISSING`](https://vitehub.dev/docs/development/diagnostics/setup_link_credentials_missing) | No \<host\> credentials were found in the environment or in the host CLI login. |
| [`SETUP_LINK_HOST_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_link_host_required) | The project links several hosts (\<hosts\>) and none is the default, so the host is not clear. |
| [`SETUP_LINK_HOST_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/setup_link_host_unsupported) | The \<host\> host has no project to link. A self-hosted Node server needs no link. |
| [`SETUP_LINK_NAME_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/setup_link_name_required) | The project name is not known. vitehub() has no literal `name` and package.json has no name. |
| [`SETUP_LINK_PROJECT_NOT_FOUND`](https://vitehub.dev/docs/development/diagnostics/setup_link_project_not_found) | The \<host\> project \<project\> does not exist\<value\>. |
| [`SETUP_NOT_A_PROJECT`](https://vitehub.dev/docs/development/diagnostics/setup_not_a_project) | \<root\> has no package.json, vite.config, or nuxt.config file. |
| [`SETUP_PLAN_UNKNOWN`](https://vitehub.dev/docs/development/diagnostics/setup_plan_unknown) | The dev server has no plan with this id. It was applied already, or the server restarted. |
| [`SETUP_SERVER_DIR_MANUAL`](https://vitehub.dev/docs/development/diagnostics/setup_server_dir_manual) | ViteHub cannot determine the Nuxt application server directory without running the config. |
| [`SETUP_STALE_PLAN`](https://vitehub.dev/docs/development/diagnostics/setup_stale_plan) | \<file\> changed after ViteHub planned the change. |
| [`SETUP_UNINSTALL_FAILED`](https://vitehub.dev/docs/development/diagnostics/setup_uninstall_failed) | `<command>` exited with code \<exitCode\>. |
| [`TASK_FAILED`](https://vitehub.dev/docs/development/diagnostics/task_failed) | Task "\<name\>" failed: \<detail\> |
| [`TASK_NOT_FOUND`](https://vitehub.dev/docs/development/diagnostics/task_not_found) | Task "\<name\>" does not exist. |
| [`TASK_NOT_IMPLEMENTED`](https://vitehub.dev/docs/development/diagnostics/task_not_implemented) | See the page of the code. |
| [`TASK_RUNTIME_UNAVAILABLE`](https://vitehub.dev/docs/development/diagnostics/task_runtime_unavailable) | Nitro tasks are not enabled in this runtime. |
| [`VITE_HUB_AGENT_OPTION_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_agent_option_missing) | \<value\> defines an Agent, but the `agent` option is not set, so the app has no Agent routes or Agent State. |
| [`VITE_HUB_CACHE_STALE_IF_ERROR_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_cache_stale_if_error_invalid) | `staleIfError` is the number of seconds after `maxAge` during which a failed call returns the stored value, but it is \<value\>. |
| [`VITE_HUB_CACHE_STALE_IF_ERROR_WITH_SERIALIZE`](https://vitehub.dev/docs/development/diagnostics/vite_hub_cache_stale_if_error_with_serialize) | `staleIfError` returns the stored value, but with `serialize` the stored value is the serialized form, and ocache would serialize it again. |
| [`VITE_HUB_CACHE_TAG_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_cache_tag_invalid) | Cache tags must be non-empty strings, but got \<tags\>. |
| [`VITE_HUB_CONSOLE_ACCESS_HANDLER_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_access_handler_invalid) | withConsoleAccess() requires a handler function. |
| [`VITE_HUB_CONSOLE_ACCESS_SCOPE_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_access_scope_invalid) | withConsoleAccess() requires { section } or { anySection: true }. |
| [`VITE_HUB_CONSOLE_ATTACHMENT_CLEANUP_QUARANTINED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_attachment_cleanup_quarantined) | Attachment cleanup ownership is quarantined |
| [`VITE_HUB_CONSOLE_AUTH_PLUGIN_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_auth_plugin_missing) | This page needs a Better Auth plugin that the app has not enabled. |
| [`VITE_HUB_CONSOLE_AUTHORIZE_FILE_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_authorize_file_missing) | console.authorize file does not exist: \<file\> |
| [`VITE_HUB_CONSOLE_AUTHORIZE_NOT_FUNCTION`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_authorize_not_function) | console.authorize must default-export a function. |
| [`VITE_HUB_CONSOLE_AUTHORIZE_PATH_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_authorize_path_invalid) | console.authorize must be a path to a server file. |
| [`VITE_HUB_CONSOLE_INVOCATION_FILES_LIMIT`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_invocation_files_limit) | Use at most ten images. |
| [`VITE_HUB_CONSOLE_JSON_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_json_invalid) | \<subject\> is not valid JSON. |
| [`VITE_HUB_CONSOLE_MCP_LIST_INCOMPLETE`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_mcp_list_incomplete) | The server returned a repeated pagination cursor. It could not finish the list. |
| [`VITE_HUB_CONSOLE_NUMBER_REQUIRED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_console_number_required) | Enter a number. |
| [`VITE_HUB_DEPLOY_CHECK_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_deploy_check_invalid) | A `deploy.check` path must be a path on the deployed site that starts with one `/`, such as `/api/health`, but it is \<value\>. |
| [`VITE_HUB_DEPLOY_INDEX_NOW_PUBLIC_URL_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_deploy_index_now_public_url_missing) | `deploy.indexNow` sends the URLs of the public site to IndexNow, and the build does not know that site: `publicUrl` is not a string. |
| [`VITE_HUB_HOST_PROVIDER_CONFLICT`](https://vitehub.dev/docs/development/diagnostics/vite_hub_host_provider_conflict) | `vitehub({ host: "<host>" })` builds \<host\> output, but `<variable>` is set, so this build runs on the \<detected\> host, which cannot run \<host\> output. |
| [`VITE_HUB_LOGS_FILTER_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_logs_filter_unsupported) | The source does not support \<filter\> filters. |
| [`VITE_HUB_LOGS_MAX_ENTRIES_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_logs_max_entries_invalid) | logs.maxEntries must be an integer from 1 to 10000. |
| [`VITE_HUB_LOGS_MAX_ENTRY_BYTES_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_logs_max_entry_bytes_invalid) | logs.maxEntryBytes must be an integer from 256 to 262144. |
| [`VITE_HUB_LOGS_SOURCE_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_logs_source_missing) | Production Logs needs an existing source. Set observability: { logs: { source: "./server/logs.ts" } }. The local buffer is per process and has no durable history. |
| [`VITE_HUB_LOGS_SOURCE_PAGE_TOO_LARGE`](https://vitehub.dev/docs/development/diagnostics/vite_hub_logs_source_page_too_large) | The source exceeded the requested page size. |
| [`VITE_HUB_MCP_AUTH_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_mcp_auth_missing) | The MCP server needs Auth, so that only signed-in MCP clients call its tools. |
| [`VITE_HUB_PACKAGE_VERSION_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_package_version_unsupported) (guide) | \<installed\> ViteHub packages of another release do not work with this vite-hub. The app can build and then fail at runtime, or run the code of the other release. |
| [`VITE_HUB_PUBLIC_URL_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_public_url_invalid) | `publicUrl` must be an http or https origin without a path, but it is \<value\>. |
| [`VITE_HUB_REDIRECTS_FILE_RULE_SKIPPED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_redirects_file_rule_skipped) | Cloudflare serves static files, such as prerendered pages, before the Worker runs, so ViteHub writes `redirect` route rules to the `_redirects` file. These rules cannot go in that file: \<rules\>. The Worker still redirects their paths, but not the static files on them. |
| [`VITE_HUB_REDIRECTS_FILE_TOO_LARGE`](https://vitehub.dev/docs/development/diagnostics/vite_hub_redirects_file_too_large) | With the `redirect` route rules, the `_redirects` file has more than Cloudflare's limit of \<fixed\> static or \<dynamic\> dynamic redirects, so ViteHub did not add the rules. The Worker still redirects their paths, but not the static files on them. |
| [`VITE_HUB_REDIRECTS_HOST_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_redirects_host_invalid) | `redirects.host` must be a host name such as `example.com`, but it is \<value\>. |
| [`VITE_HUB_REDIRECTS_PREVIEW_HOST_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_redirects_preview_host_invalid) | Each `redirects.previewHosts` entry must be a host name such as `staging.example.com` or `*.example.com`, but one is \<value\>. |
| [`VITE_HUB_REDIRECTS_TRAILING_SLASH_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_redirects_trailing_slash_invalid) | `redirects.trailingSlash` must be `"add"` or `"remove"`, but it is \<value\>. |
| [`VITE_HUB_RENAMED_PROVIDER_KEY`](https://vitehub.dev/docs/development/diagnostics/vite_hub_renamed_provider_key) | `<key>.provider` is \<value\>. ViteHub renamed this key to `driver`, and it does not read `provider`, so it would pick the driver of the host, or stop because the host has none. |
| [`VITE_HUB_REQUEST_BODY_TOO_LARGE`](https://vitehub.dev/docs/development/diagnostics/vite_hub_request_body_too_large) | The request body is larger than \<limit\> bytes, the `security.maxBodySize` of this app. |
| [`VITE_HUB_SANDBOX_CLI_DRAIN_TIMEOUT_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_sandbox_cli_drain_timeout_invalid) | --drain-timeout must be a non-negative number of milliseconds. |
| [`VITE_HUB_SANDBOX_CLI_DRIVER_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_sandbox_cli_driver_invalid) | --driver must be codex or claude-code. |
| [`VITE_HUB_SANDBOX_CLI_OPTION_MISSING`](https://vitehub.dev/docs/development/diagnostics/vite_hub_sandbox_cli_option_missing) | \<option\> is required. |
| [`VITE_HUB_SANDBOX_CLI_PORT_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_sandbox_cli_port_invalid) | --port must be between 1 and 65535. |
| [`VITE_HUB_SANDBOX_CLI_TIMEOUT_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_sandbox_cli_timeout_invalid) | --timeout must be a positive number of milliseconds. |
| [`VITE_HUB_SANDBOX_DRIVER_HOST_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_sandbox_driver_host_unsupported) | sandboxTask.driver "cloudflare" works with the "cloudflare" host only, because Cloudflare Sandbox needs the Container and Durable Object binding of a Worker. The "\<host\>" host cannot provide them. |
| [`VITE_HUB_SECURITY_HEADER_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_security_header_invalid) | `security.headers` sets \<name\>, which is not a valid header name, or its value has a line break or a character that a header cannot hold. |
| [`VITE_HUB_SECURITY_MAX_BODY_SIZE_INVALID`](https://vitehub.dev/docs/development/diagnostics/vite_hub_security_max_body_size_invalid) | `security.maxBodySize` is \<value\>, which is not a size. |
| [`VITE_HUB_SETUP_BODY_TOO_LARGE`](https://vitehub.dev/docs/development/diagnostics/vite_hub_setup_body_too_large) | The request body is too large. The dev Setup endpoints accept at most \<limit\> bytes. |
| [`VITE_HUB_TEST_MODULE_NOT_LOADED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_test_module_not_loaded) | The Vite server of vite-hub/test resolved "\<id\>", but no plugin loads it. |
| [`VITE_HUB_TEST_SERVER_FAILED`](https://vitehub.dev/docs/development/diagnostics/vite_hub_test_server_failed) | The Vite server of vite-hub/test failed: \<error\> |
| [`VITE_HUB_TEST_SERVER_TIMEOUT`](https://vitehub.dev/docs/development/diagnostics/vite_hub_test_server_timeout) | The Vite server of vite-hub/test did not start in 60 seconds. |

## Named errors

| Code | What happened |
| --- | --- |
| [`INTERNAL_CONSOLE_KEY_NAME_INVALID`](https://vitehub.dev/docs/development/diagnostics/internal_console_key_name_invalid) | The Console key name \<name\> must be 1 to 64 of A-Z, 0-9, and _. |
| [`INTERNAL_CONSOLE_PRIVATE_KEY_INVALID`](https://vitehub.dev/docs/development/diagnostics/internal_console_private_key_invalid) | A Console private key is the 32-byte Ed25519 seed as base64url (43 characters). `vitehub secret console-key` makes one. |
| [`INTERNAL_CONSOLE_PRIVATE_KEY_VARIABLE_INVALID`](https://vitehub.dev/docs/development/diagnostics/internal_console_private_key_variable_invalid) | \<variable\> must be the 43-character private key that `vitehub secret console-key` prints, and its name 1 to 64 of A-Z, 0-9, and _. |
| [`INTERNAL_CONSOLE_PRIVATE_KEY_VARIABLES_MULTIPLE`](https://vitehub.dev/docs/development/diagnostics/internal_console_private_key_variables_multiple) | Set one \<prefix\>\<NAME\> variable. This environment has \<variables\>. |
| [`INTERNAL_FORGE_NOT_INSTALLED`](https://vitehub.dev/docs/development/diagnostics/internal_forge_not_installed) | \<feature\> needs @vite-hub/forge, and the app did not install it. |
| [`INTERNAL_MCP_ARGUMENTS_INVALID`](https://vitehub.dev/docs/development/diagnostics/internal_mcp_arguments_invalid) | See the page of the code. |
| [`INTERNAL_MCP_METHOD_FAILED`](https://vitehub.dev/docs/development/diagnostics/internal_mcp_method_failed) | \<name\> failed on the server. |
| [`INTERNAL_MCP_RESOURCE_NOT_FOUND`](https://vitehub.dev/docs/development/diagnostics/internal_mcp_resource_not_found) | Resource not found: \<uri\>. Call resources/list or resources/templates/list for the resources of this server. |
| [`INTERNAL_PRESET_OPTION_UNKNOWN`](https://vitehub.dev/docs/development/diagnostics/internal_preset_option_unknown) | Unknown \<label\> option "\<key\>". |
| [`INTERNAL_PRESET_TUPLE_INVALID`](https://vitehub.dev/docs/development/diagnostics/internal_preset_tuple_invalid) | \<owner\> extends tuple requires [preset, options] with an options object. |
| [`INTERNAL_SECRET_PURPOSE_MISSING`](https://vitehub.dev/docs/development/diagnostics/internal_secret_purpose_missing) | A derived secret requires a purpose. |
| [`INTERNAL_SECRET_TOO_SHORT`](https://vitehub.dev/docs/development/diagnostics/internal_secret_too_short) | VITEHUB_SECRET must be at least \<minimum\> characters. Generate one with `openssl rand -base64 32`. |
| [`INTERNAL_SQLITE_ARGUMENT_INVALID`](https://vitehub.dev/docs/development/diagnostics/internal_sqlite_argument_invalid) | Only finite numbers (not Infinity or NaN) can be passed as arguments |
| [`INTERNAL_SQLITE_INTEGER_UNSAFE`](https://vitehub.dev/docs/development/diagnostics/internal_sqlite_integer_unsafe) | Received integer which cannot be safely represented as a JavaScript number |
| [`INTERNAL_VALIBOT_JSON_SCHEMA_TARGET_UNSUPPORTED`](https://vitehub.dev/docs/development/diagnostics/internal_valibot_json_schema_target_unsupported) | Valibot cannot convert a schema to the \<target\> JSON Schema target. |
| [`RUNTIME_CONSOLE_PATH_INVALID`](https://vitehub.dev/docs/development/diagnostics/runtime_console_path_invalid) | \<value\> is not a Console path. Use a path that starts with one /, such as /agents/\<agent\>. |
| [`RUNTIME_CONSOLE_PROJECT_URL_INVALID`](https://vitehub.dev/docs/development/diagnostics/runtime_console_project_url_invalid) | \<value\> is not a project URL. Use the https:// origin of the app, with its base path if it has one. |
| [`RUNTIME_EXECUTION_BUDGET_AMOUNT_INVALID`](https://vitehub.dev/docs/development/diagnostics/runtime_execution_budget_amount_invalid) | Execution budget \<counter\> amount must be a finite non-negative number. |
| [`RUNTIME_EXECUTION_BUDGET_EXCEEDED`](https://vitehub.dev/docs/development/diagnostics/runtime_execution_budget_exceeded) | Execution budget exhausted for \<counter\>. |
| [`RUNTIME_EXECUTION_BUDGET_LIMIT_INVALID`](https://vitehub.dev/docs/development/diagnostics/runtime_execution_budget_limit_invalid) | Execution budget limits must be finite non-negative numbers. |
| [`RUNTIME_SERIALIZED_RESPONSE_INVALID`](https://vitehub.dev/docs/development/diagnostics/runtime_serialized_response_invalid) | Invalid serialized Response |

## Definition errors

| Code | What happened |
| --- | --- |
| [`SKILL_DUPLICATE_NAME`](https://vitehub.dev/docs/development/diagnostics/skill_duplicate_name) | Two skills are named \<name\>. |
| [`SKILL_FILE_MISSING`](https://vitehub.dev/docs/development/diagnostics/skill_file_missing) | The skill\<value\> has no `SKILL.md`. |
| [`SKILL_INVALID_FRONTMATTER`](https://vitehub.dev/docs/development/diagnostics/skill_invalid_frontmatter) | The frontmatter of `SKILL.md` is not valid: \<problem\> |
| [`SKILL_INVALID_PATH`](https://vitehub.dev/docs/development/diagnostics/skill_invalid_path) | The skill file path \<path\> is not a relative path inside the skill, or is too long for a skill archive. |

<!-- vitehub-docs:section-links -->
## In this section

- [Local tools](https://vitehub.dev/raw/docs/development.md)
- [Build state](https://vitehub.dev/raw/docs/development/provisioning.md)
- [Proof and recovery](https://vitehub.dev/raw/docs/development/testing.md)

All pages: [llms.txt](https://vitehub.dev/llms.txt)
