ViteHub is still experimental. Expect bugs and breaking changes.

Errors and diagnostics

Reference common ViteHub error families and the local proof path for each one.

Errors and diagnostics belong to the package that owns the failing boundary. Use the error family to choose the next proof path before changing implementation code.

Error families

ErrorOwnerUsually means
CapabilityNotFoundErrorRuntime PackageA Runtime Capability handle is missing.
CapabilityDeniedErrorRuntime PackageRuntime policy denied a capability operation.
ApprovalRequiredErrorRuntime PackageA policy decision requires an Approval Request before execution.
EnvErrorEnv PackageEnv Declaration resolution, validation, or diagnostics failed.
AuthenticationRequiredErrorAuth PackageA route or Agent Invoker bridge needs an authenticated application user.
QueueErrorQueue PackageQueue dispatch, callback, or provider handling failed.
WorkspaceErrorWorkspace PackageWorkspace runtime, store, rule, or file-tree behavior failed.
WorkspaceNotFoundErrorWorkspace PackageThe requested Workspace is not registered.
WorkspacePathErrorWorkspace PackageA Workspace path is invalid or outside allowed shape.
SourceErrorSource PackageSource retrieval or Source Loader behavior failed.
SourceNotFoundErrorSource PackageThe requested Source key or Source Path is missing.
SourcePathErrorSource PackageA Source Path is invalid.
ScheduleErrorSchedule PackageStatic or runtime schedule behavior failed.
SandboxErrorSandbox PackageSandbox Provider setup, execution, or output recovery failed.
NotSupportedErrorSandbox shared runtimeA selected provider or operation is unsupported.
WorkflowErrorWorkflow PackageWorkflow run, step, or provider behavior failed.
RateLimitRejectedErrorAgent PackageRate Limit Capability rejected an Agent Invocation.
LlmGateRejectedErrorAgent PackageLLM Gate Capability rejected before the main Agent Invocation.

Diagnostics sources

SourceUse
CLI exit code and stderrCommand parsing, provisioning, and Agent Eval failures.
Env diagnosticsMissing, defaulted, valid, and masked Env Declaration status.
Generated filesDiscovery, Runtime Registry, and Provider Output inspection.
DevTools Bridge responsesInteractive Agent and Workspace inspection failures.
Trace EventsRuntime policy, approval, capability, lifecycle, and error records.
Package testsContract failures owned by the primitive package.

Local response

Start with the owning package and the failing proof path. For provider failures, inspect generated output before changing runtime code.

Terminal
pnpm vitehub provision run --provider cloudflare --dry-run
find .vitehub -maxdepth 4 -type f | sort
pnpm --filter @vite-hub/sandbox test

Production response

Production diagnostics should avoid leaking secrets. Use Server Env and Secret Env for runtime secret values, and rely on package diagnostics to redact known secret values where supported.

Copyright © 2026