# ViteHub

> Portable Agents for Vite, built on Server Primitives.

Rules for coding agents:

- Read the installed package exports and types before you write imports or options. When the installed packages, these docs, and remembered syntax disagree, follow the installed packages.
- Prefer the `vite-hub` distribution: register `vitehub()` from `vite-hub` in the Vite config and import Runtime Helpers from feature subpaths such as `vite-hub/kv`. Some pages use owner packages such as `@vite-hub/kv`; follow the style that the project already uses.
- Keep provider and host selection in the Vite config. Application code calls the same Runtime Helper on every host.
- Give an Agent authority only through Capabilities, Workspaces, Sources, or Channels. Do not pass application secrets or broad access to an Agent implicitly.
- Open the raw page for one feature, such as `https://vitehub.dev/raw/docs/kv.md`, before you write code. Raw pages contain agent-only details that the rendered site does not show. Do not load llms-full.txt for one task.
- Prove the change: run the Runtime Helper, Agent Invocation, webhook, or schedule, and inspect the generated `.vitehub/` state or provider output.
- Install the ViteHub skill for routed guidance: `npx skills add https://vitehub.dev --skill vitehub`.

## Overview

- [ViteHub](https://vitehub.dev/raw/index.md)

## Documentation Sets

- [ViteHub](https://vitehub.dev/llms-full.txt): Server primitives for Vite.

## When to use ViteHub

Use ViteHub when a Vite application needs portable server storage, queues, workflows, schedules, sandboxes, or other Server Primitives; when it needs inspectable Agent Definitions with explicit Capabilities and Workspaces; or when the same runtime behavior must deploy across supported hosts without leaking provider APIs into application code.

- [Choose a ViteHub layer](https://vitehub.dev/raw/docs/getting-started.md): Decide whether the job needs a Server Primitive, an Agent, or both.
- [Install ViteHub](https://vitehub.dev/raw/docs/getting-started/installation.md): Install the framework distribution or a focused owner package.

## ViteHub developer resources

Use these named machine interfaces to inspect ViteHub before reading the full documentation set. ViteHub is installed into your application and does not expose a shared hosted runtime API.

- [ViteHub OpenAPI document](https://vitehub.dev/openapi.json): Discover the public machine-readable resources served by vitehub.dev.
- [ViteHub Agent Skill](https://vitehub.dev/.well-known/skills/vitehub/SKILL.md): Install or inspect the coding-agent instructions and routed references.
- [ViteHub MCP server](https://vitehub.dev/mcp): Connect an MCP client to the Streamable HTTP documentation endpoint.
- [ViteHub CLI on npm](https://www.npmjs.com/package/vite-hub): Install the official CLI included with the vite-hub package.

## Project and trust information

- [About ViteHub](https://vitehub.dev/raw/about.md)
- [Contact ViteHub](https://vitehub.dev/raw/contact.md)
- [ViteHub privacy](https://vitehub.dev/raw/privacy.md)

## Docs

Every page below is available as raw markdown.

- [ViteHub documentation](https://vitehub.dev/raw/docs.md): Server Primitives and Agents for Vite applications, one product section each, deployed on the host you select.
- [Agents](https://vitehub.dev/raw/docs/agents.md): Define an AI agent on your server in one file, choose what runs it, and reach it from chat, Slack, GitHub, or HTTP.
- [Agent Actors](https://vitehub.dev/raw/docs/agents/actors.md): Carry trusted caller identity into one Agent Invocation, normalize Actor fields, and use Actors for access decisions.
- [Agent Definitions](https://vitehub.dev/raw/docs/agents/agent-definitions.md): Declare how one Agent runs, what it can use, and how callers reach it.
- [Agent Drivers](https://vitehub.dev/raw/docs/agents/agent-drivers.md): Choose model-backed, provider-backed, question-backed, or application-owned Agent execution.
- [Babysitter](https://vitehub.dev/raw/docs/agents/babysitter.md): Deploy an Agent that repairs pull requests, waits for checks, and merges ready ones.
- [Capabilities](https://vitehub.dev/raw/docs/agents/capabilities.md): Give an Agent tools and behavior without handing it unrestricted server access.
- [Access](https://vitehub.dev/raw/docs/agents/capabilities/access.md): Admit trusted chat traffic and narrow the Workspace before other Capabilities add tools.
- [Budget](https://vitehub.dev/raw/docs/agents/capabilities/budget.md): Bound Agent Invocation tokens and estimated model cost with one inspectable policy.
- [Chat](https://vitehub.dev/raw/docs/agents/capabilities/chat.md): Add the chat.message Agent Trigger, Chat History state, and chat finish behavior to an Agent without Channels.
- [Chat summary](https://vitehub.dev/raw/docs/agents/capabilities/chat-summary.md): Add a summary command that replaces explicit input with a conversation summary.
- [Custom capabilities](https://vitehub.dev/raw/docs/agents/capabilities/custom.md): Build one product-specific Agent ability with requirements, tools, policy, and metadata.
- [Diagnostics](https://vitehub.dev/raw/docs/agents/capabilities/diagnostics.md): Report Agent Invocation outcomes and scoped runtime resource observations.
- [Fetch](https://vitehub.dev/raw/docs/agents/capabilities/fetch.md): Expose named HTTP request tools for endpoints that the developer approves, with security, approval, and driver support.
- [Forge](https://vitehub.dev/raw/docs/agents/capabilities/forge.md): Give an Agent tools to read and change repositories, pull requests, and issues on GitHub, GitLab, and Forgejo.
- [Git](https://vitehub.dev/raw/docs/agents/capabilities/git.md): Give an Agent bounded Git source-history access inside a Workspace Session.
- [Gmail](https://vitehub.dev/raw/docs/agents/capabilities/gmail.md): Let an Agent search and read Gmail and create unsent drafts through a Google Connection.
- [Input commands](https://vitehub.dev/raw/docs/agents/capabilities/input-commands.md): Transform explicit user commands such as /docs before the Agent Driver runs.
- [LLM gate](https://vitehub.dev/raw/docs/agents/capabilities/llm-gate.md): Allow or reject an Agent Invocation with a model decision before the Agent Driver runs.
- [LLM route](https://vitehub.dev/raw/docs/agents/capabilities/llm-route.md): Choose one developer-defined route with a model decision before the Agent Driver runs.
- [MCP](https://vitehub.dev/raw/docs/agents/capabilities/mcp.md): Connect an Agent to tools from external MCP servers, authenticate through a Connection, and pin the tool definitions.
- [Memory](https://vitehub.dev/raw/docs/agents/capabilities/memory.md): Add scoped durable memory records that an Agent can search, read, remember, and delete.
- [Official capabilities](https://vitehub.dev/raw/docs/agents/capabilities/official.md): Choose an official Capability by what the Agent needs to do, such as Blob, Browser, Email, MCP, Sandbox, or Channel delivery.
- [OpenAPI](https://vitehub.dev/raw/docs/agents/capabilities/openapi.md): Expose selected OpenAPI operations as bounded Agent tools or a generated Capability CLI.
- [OTLP](https://vitehub.dev/raw/docs/agents/capabilities/otlp.md): Export live Agent Invocation events and completed traces to an OpenTelemetry receiver.
- [Papercuts](https://vitehub.dev/raw/docs/agents/capabilities/papercuts.md): Let an Agent report small failures and wasted work to an application-owned sink.
- [Progress summary](https://vitehub.dev/raw/docs/agents/capabilities/progress-summary.md): Stream a short user-facing summary of current Agent activity, render it in your UI, and send it through Channels.
- [Skills](https://vitehub.dev/raw/docs/agents/capabilities/skills.md): Make a Workspace or external Source Skill available to an Agent, and verify how the Agent loads and uses the Skill.
- [Title](https://vitehub.dev/raw/docs/agents/capabilities/title.md): Generate a short title for an Agent Invocation and attach it to output, finish hooks, and Channel threads.
- [Transcribe](https://vitehub.dev/raw/docs/agents/capabilities/transcribe.md): Convert audio input parts into transcript text before an Agent runs, with streaming and asynchronous remote transcription.
- [Usage](https://vitehub.dev/raw/docs/agents/capabilities/usage.md): Request provider usage metadata and expose normalized tokens and cost at finish.
- [Web search](https://vitehub.dev/raw/docs/agents/capabilities/web-search.md): Give an Agent model web search or normalized web search and read tools, with credentials, approval, and driver support.
- [Agent Channels](https://vitehub.dev/raw/docs/agents/channels.md): Connect an Agent to web chat and messaging platforms without mixing transport with identity.
- [Chat History and sessions](https://vitehub.dev/raw/docs/agents/chat-history-sessions.md): Select prior conversation messages without confusing them with durable Agent Memory.
- [Child invocations](https://vitehub.dev/raw/docs/agents/controlled-child-invocations.md): Start, inspect, respond to, and cancel child Agent work from trusted code.
- [Evals](https://vitehub.dev/raw/docs/agents/evals.md): Run repeatable scenarios against an Agent Definition and score its behavior.
- [Forge Channels](https://vitehub.dev/raw/docs/agents/forge-channels.md): Run an Agent on GitLab, Forgejo, and Codeberg pull request events, with the Server Env and webhook setup for each forge.
- [Define your first Agent](https://vitehub.dev/raw/docs/agents/get-started.md): Install Agents, build an offline greeting Agent that needs no API key, call it from a server route, and verify the response.
- [Gmail Channel](https://vitehub.dev/raw/docs/agents/gmail.md): Run an Agent on each new Gmail message and let hooks label, archive, or trash it.
- [Instructions](https://vitehub.dev/raw/docs/agents/instructions.md): Write durable model-facing behavior and policy for an Agent in colocated documents, shared guidance, and trusted values.
- [Invocations](https://vitehub.dev/raw/docs/agents/invocations.md): Run, stream, and observe one request to an Agent, validate its input, invoke Triggers, and cancel an Invocation.
- [Auth Users and Agent Invokers](https://vitehub.dev/raw/docs/agents/invokers.md): Understand how application identity becomes trusted invocation identity.
- [Gmail Labeller preset](https://vitehub.dev/raw/docs/agents/labeller.md): Label Gmail messages with ordered rules and a constrained Jev fallback.
- [Observability](https://vitehub.dev/raw/docs/agents/observability.md): Export Agent lifecycle events, request failures and durable papercut reports through evlog.
- [Agent presets](https://vitehub.dev/raw/docs/agents/presets.md): Start from a reusable Agent Definition and configure it for your application.
- [Process hosts](https://vitehub.dev/raw/docs/agents/process-hosts.md): Run one long-lived Node process that admits, recovers, and drains background Agent work.
- [Provider status](https://vitehub.dev/raw/docs/agents/provider-status.md): Inspect provider authentication and subscription quota without running an Agent.
- [Runtime policy, approvals, and traces](https://vitehub.dev/raw/docs/agents/runtime-policy.md): Choose when an Agent tool can run, know who owns each approval, and inspect the policy decision after the Invocation.
- [Run your first Sandbox](https://vitehub.dev/raw/docs/agents/sandbox-tutorial.md): Install the Sandbox package, open a trusted-host Sandbox session, run one command, and inspect the result.
- [Sandboxes](https://vitehub.dev/raw/docs/agents/sandboxes.md): Run a built-in provider Driver inside a Sandbox with a private Home, checkout, credentials, and process requirements.
- [Build a support Agent](https://vitehub.dev/raw/docs/agents/support-agent.md): Compose a support Agent that answers in Teams from scoped Workspace evidence.
- [Test an Agent](https://vitehub.dev/raw/docs/agents/testing.md): Check Agent contracts with deterministic tests, Evals, and a local invocation before you deploy.
- [Triggers](https://vitehub.dev/raw/docs/agents/triggers.md): Translate product events into Agent Invocations while the Driver continues to own execution.
- [Workspace context](https://vitehub.dev/raw/docs/agents/workspace-context.md): Give an Agent scoped files and Sources with explicit read and write authority.
- [Workspace preset](https://vitehub.dev/raw/docs/agents/workspace-preset.md): Read mounted Sources and cite files at their resolved GitHub revision.
- [Auth](https://vitehub.dev/raw/docs/auth.md): Add sign-up, sign-in, and protected routes to your app with Better Auth, from one server file.
- [Auth configuration](https://vitehub.dev/raw/docs/auth/configure.md): Write the Auth Definition, supply runtime options, and record storage placement.
- [Create your first Auth session](https://vitehub.dev/raw/docs/auth/get-started.md): Create an email-and-password user and verify their session with a saved cookie.
- [Auth hosts](https://vitehub.dev/raw/docs/auth/hosts.md): See what Better Auth owns, what ViteHub Auth owns, and which Provider Output Auth generates for each supported host.
- [Auth limits and errors](https://vitehub.dev/raw/docs/auth/limits-and-errors.md): Check Auth before production, handle required authentication in routes, and read the stable Auth error codes.
- [Auth server API](https://vitehub.dev/raw/docs/auth/server-api.md): Read sessions, call Better Auth, and guard routes from server and Vue code.
- [Blob](https://vitehub.dev/raw/docs/blob.md): Save uploads and other files from your server, then read or serve them with the same code on every host.
- [Blob capability](https://vitehub.dev/raw/docs/blob/agent-capability.md): Give an Agent a Blob read tool and, in write mode, a tool that puts or deletes objects.
- [Blob configuration](https://vitehub.dev/raw/docs/blob/configure.md): Configure Blob Stores, the opt-in route that serves blob-backed assets, and the options for each storage provider.
- [Store your first Blob object](https://vitehub.dev/raw/docs/blob/get-started.md): Install Blob, write a text file to a local object store from a server route, and check its path, content type, and size.
- [Blob hosts](https://vitehub.dev/raw/docs/blob/hosts.md): Set up host output, development access, Cloudflare R2, S3-compatible storage, and MinIO.
- [Blob media and images](https://vitehub.dev/raw/docs/blob/media.md): Keep alt text, focal points, and crops next to Blob objects, organize them in folders, and serve responsive image variants.
- [Blob server API](https://vitehub.dev/raw/docs/blob/server-api.md): Read, write, list, upload, sign, and validate objects from server code, and check production rules.
- [Browser](https://vitehub.dev/raw/docs/browser.md): Load and control web pages in a Cloudflare browser from your server code, with no browser setup in your app.
- [Browser capability](https://vitehub.dev/raw/docs/browser/agent-capability.md): Give a Provider Agent the agent-browser CLI, a headless Chromium, and the official browser Skill.
- [Browser configuration](https://vitehub.dev/raw/docs/browser/configure.md): Configure the Browser Run binding, the session engine, and remote local development.
- [Run your first Browser Definition](https://vitehub.dev/raw/docs/browser/get-started.md): Define a browser operation, run it by name with Cloudflare Browser Run, and verify the rendered HTML it returns.
- [Browser hosts](https://vitehub.dev/raw/docs/browser/hosts.md): Choose a Browser provider for each host: Cloudflare Browser Run on Workers, or a local Chromium process on trusted Node hosts.
- [Browser limits and errors](https://vitehub.dev/raw/docs/browser/limits-and-errors.md): Know Browser action timeouts, live handoff limits, and engine differences, and check Browser before production.
- [Browser server API](https://vitehub.dev/raw/docs/browser/server-api.md): Define, run, and control browser operations from server code, keep a page session open, and hand off a live session.
- [Channels](https://vitehub.dev/raw/docs/channels.md): Send messages from your server to Slack, Telegram, or any service through a named Channel.
- [Channels capability](https://vitehub.dev/raw/docs/channels/agent-capability.md): Let an Agent send its result through a Channel to a recipient that the application selects.
- [Send through your first Channel](https://vitehub.dev/raw/docs/channels/get-started.md): Define a named Channel, send a local build notification from server code, and inspect the connector receipt.
- [Channels server API](https://vitehub.dev/raw/docs/channels/server-api.md): Send messages through a named Channel from an H3 or Nitro handler, add connectors, and read the delivery receipt.
- [Connections](https://vitehub.dev/raw/docs/connections.md): Connect a Google account or an API key once, then call the provider API from your server.
- [Connections configuration](https://vitehub.dev/raw/docs/connections/configure.md): Configure provider origins, API key Connections, access rules, and Connections options.
- [Connect your first provider account](https://vitehub.dev/raw/docs/connections/get-started.md): Define a Connection, connect a Google account with OAuth, and call the Gmail API to read the account's labels.
- [Connections limits and errors](https://vitehub.dev/raw/docs/connections/limits-and-errors.md): Know how Connections store and encrypt grants, how the OAuth connect flow is secured, and which error codes it returns.
- [Connections server API](https://vitehub.dev/raw/docs/connections/server-api.md): Call a Connection from server code, read its activity, and manage Connections from the CLI.
- [Content](https://vitehub.dev/raw/docs/content.md): Turn Markdown files into pages your app can read, list, and search, and let people edit drafts and publish them.
- [Content capability](https://vitehub.dev/raw/docs/content/agent-capability.md): Let an Agent read, draft, publish, and schedule documents in Content collections, with access checked by your authorize policy.
- [Content CLI](https://vitehub.dev/raw/docs/content/cli.md): List, read, edit, publish, and schedule Content documents from the terminal, with field issues, edit leases, and pinned digests.
- [CMS preset](https://vitehub.dev/raw/docs/content/cms-preset.md): Store editable document collections from one file. ViteHub turns on Workspace, Database, and Blob, adds the Workspace and its history tables, and adds a Database when the app has none.
- [Content configuration](https://vitehub.dev/raw/docs/content/configure.md): Define read-only Sources and editable document collections with defineContent(), choose plugins, and set access.
- [Edit Content in the Console](https://vitehub.dev/raw/docs/content/console.md): Edit, publish, and restore Content documents from the ViteHub Console, and give editors access to only that section.
- [Edit Content together](https://vitehub.dev/raw/docs/content/editing-together.md): Show who has a document open, give one session at a time the edit lease, and refuse writes from everyone else.
- [Read your first Content document](https://vitehub.dev/raw/docs/content/get-started.md): Parse a local Markdown file and read its Content document from a route.
- [Content limits and errors](https://vitehub.dev/raw/docs/content/limits-and-errors.md): Definition, path, collection, history, preview, and access limits for Content, and the errors they raise.
- [Content draft preview](https://vitehub.dev/raw/docs/content/preview.md): Render draft documents through your real pages for one browser with a signed preview cookie, while the public site keeps serving published content.
- [Schedule Content publishing](https://vitehub.dev/raw/docs/content/scheduling.md): Publish reviewed drafts at a later time with content.schedule(), run due schedules from a Schedule Definition on every host, and inspect pending, overdue, and failed schedules.
- [Content SEO](https://vitehub.dev/raw/docs/content/seo.md): Give documents public URLs, per-document SEO fields, head tags for any framework, and a generated sitemap and robots.txt.
- [Content server API](https://vitehub.dev/raw/docs/content/server-api.md): Read documents, navigation, and search results, and save, publish, and inspect document collections from server code.
- [Database](https://vitehub.dev/raw/docs/database.md): Define SQL tables in TypeScript and query them from your server routes with typed results.
- [Database capability](https://vitehub.dev/raw/docs/database/agent-capability.md): Give an Agent guarded SQL query and schema tools and, in write modes, one mutation tool.
- [Database configuration](https://vitehub.dev/raw/docs/database/configure.md): Set Database integration options and define Default and Named Databases.
- [Query your first Database](https://vitehub.dev/raw/docs/database/get-started.md): Create a SQLite notes table with Drizzle and query it from a server route.
- [Database hosts](https://vitehub.dev/raw/docs/database/hosts.md): Select local SQLite, hosted libSQL, Cloudflare D1, or Postgres, read what each host output contains, and check production rules.
- [Database limits and errors](https://vitehub.dev/raw/docs/database/limits-and-errors.md): Read Database error codes, and repair Database configuration and build errors.
- [Database server API](https://vitehub.dev/raw/docs/database/server-api.md): Query a discovered database from server code with a typed Drizzle client.
- [Local development](https://vitehub.dev/raw/docs/development.md): Run ViteHub locally, inspect generated files, and verify the behavior you changed.
- [CLI](https://vitehub.dev/raw/docs/development/cli.md): Run package-owned development workflows through the local Vite config.
- [Console](https://vitehub.dev/raw/docs/development/console.md): Enable the Console, inspect configured primitives, and protect its routes.
- [Definition discovery](https://vitehub.dev/raw/docs/development/definition-discovery.md): Understand how a file location becomes a named ViteHub runtime entry, and check which Definitions the integration found.
- [Generated files](https://vitehub.dev/raw/docs/development/generated-files.md): Inspect ViteHub generated files without making them public authoring surfaces.
- [Vite integrations and Provider Output](https://vitehub.dev/raw/docs/development/integrations-and-output.md): Understand how ViteHub prepares a package for development and deployment.
- [Provisioning](https://vitehub.dev/raw/docs/development/provisioning.md): Create missing provider resources and write non-secret provider ids into local provision state.
- [Troubleshooting](https://vitehub.dev/raw/docs/development/troubleshooting.md): Diagnose common ViteHub development failures from symptoms to proof paths.
- [Verification](https://vitehub.dev/raw/docs/development/verification.md): Choose the right proof tier for ViteHub primitives and provider behavior.
- [Email](https://vitehub.dev/raw/docs/email.md): Send email from your server through Resend or Cloudflare, and write messages as Markdown templates.
- [Email capability](https://vitehub.dev/raw/docs/email/agent-capability.md): Let an Agent send plain-text email from an application-owned sender to allowed recipients.
- [Email configuration](https://vitehub.dev/raw/docs/email/configure.md): Configure the Email Vite Integration, select a driver, and connect another provider.
- [Send your first Email](https://vitehub.dev/raw/docs/email/get-started.md): Install Email, configure Resend with a secret, send a welcome email from server code, and check the delivery result.
- [Email hosts](https://vitehub.dev/raw/docs/email/hosts.md): Understand provider behavior, the development outbox, and Email runtime requirements.
- [Email limits and errors](https://vitehub.dev/raw/docs/email/limits-and-errors.md): Handle Email delivery errors by code, fix runtime, configuration, and build errors, and troubleshoot common failures.
- [Email server API](https://vitehub.dev/raw/docs/email/server-api.md): Send messages, compose dynamic Markdown, and capture email in tests from server code.
- [Env](https://vitehub.dev/raw/docs/env.md): Declare your settings and secrets once, then read them as typed values in browser and server code.
- [App secret](https://vitehub.dev/raw/docs/env/app-secret.md): Configure one root secret and derive every purpose-specific signing secret from it.
- [Env Bridge](https://vitehub.dev/raw/docs/env/bridge.md): Replace application credentials at runtime with scoped access and persistent activity.
- [Env configuration](https://vitehub.dev/raw/docs/env/configure.md): Declare Public Env, Define Env, and Server Env values, their sources, and their types.
- [Read your first environment value](https://vitehub.dev/raw/docs/env/get-started.md): Declare a safe application name and read it from the generated Public Env module.
- [Env limits and errors](https://vitehub.dev/raw/docs/env/limits-and-errors.md): Handle structured Env errors with stable codes and JSON-safe context, and check Env configuration before production.
- [Env server API](https://vitehub.dev/raw/docs/env/server-api.md): Read Public Env and Server Env, load provider-backed values, and inspect Env status.
- [Frameworks and hosts](https://vitehub.dev/raw/docs/frameworks-hosts.md): Choose a framework integration and a deployment preset, and see what ViteHub builds for each host.
- [Cloudflare](https://vitehub.dev/raw/docs/frameworks-hosts/cloudflare.md): Configure Cloudflare Provider Output while keeping ViteHub Definitions and Runtime Helpers host-neutral.
- [Deno](https://vitehub.dev/raw/docs/frameworks-hosts/deno.md): Generate Deno server output for Agent routes and Schedule wake output without making app code Deno-specific.
- [Netlify](https://vitehub.dev/raw/docs/frameworks-hosts/netlify.md): Use the ViteHub package contracts that have explicit Netlify runtime or function output.
- [Nitro and UnJS](https://vitehub.dev/raw/docs/frameworks-hosts/nitro-unjs.md): Understand the narrow boundary between ViteHub, Nitro, and UnJS server runtimes.
- [Node and self-hosted](https://vitehub.dev/raw/docs/frameworks-hosts/node-self-hosted.md): Build a Node.js server with the node preset and choose storage that survives restarts.
- [Nuxt](https://vitehub.dev/raw/docs/frameworks-hosts/nuxt.md): Register ViteHub in a Nuxt application and see what the Nuxt module does differently from the Vite integration.
- [Prepare a production deployment](https://vitehub.dev/raw/docs/frameworks-hosts/production.md): Choose durable providers, protect entry points, and verify recovery before serving application traffic.
- [Runtime and host support](https://vitehub.dev/raw/docs/frameworks-hosts/support-matrix.md): Check which ViteHub contracts exist for each host and how the repository proves them.
- [Vercel](https://vitehub.dev/raw/docs/frameworks-hosts/vercel.md): Generate Vercel Provider Output while preserving ViteHub package boundaries.
- [Introduction](https://vitehub.dev/raw/docs/getting-started.md): Choose the ViteHub layer that matches the first thing you need to build.
- [Give your coding agent ViteHub context](https://vitehub.dev/raw/docs/getting-started/ai-resources.md): Choose the skill, MCP server, page action, or index that gives a coding agent current ViteHub documentation.
- [Add the ViteHub skill](https://vitehub.dev/raw/docs/getting-started/ai-resources/agent-instructions-skills.md): Install the ViteHub coding-agent skill in Claude Code, Cursor, VS Code, Windsurf, or Codex.
- [Copy a page for an LLM](https://vitehub.dev/raw/docs/getting-started/ai-resources/markdown-pages.md): Copy, view, or open any ViteHub docs page as Markdown in ChatGPT, Claude, or another tool.
- [Connect the docs MCP server](https://vitehub.dev/raw/docs/getting-started/ai-resources/mcp-server.md): Let your coding agent list and read ViteHub documentation pages through MCP.
- [Build and deploy](https://vitehub.dev/raw/docs/getting-started/build-and-deploy.md): Find the setup, development tools, and API reference for your application.
- [Built for the Vue ecosystem](https://vitehub.dev/raw/docs/getting-started/built-for-vue.md): Use ViteHub UI Vue components for chat, sessions, files, and Agent inspection, then connect them to your own data.
- [How ViteHub works](https://vitehub.dev/raw/docs/getting-started/concepts.md): Understand the few parts that connect application code, server features, and Agents.
- [First Agent](https://vitehub.dev/raw/docs/getting-started/first-agent.md): Create a project, define a server-side greeting Agent, call it from an H3 route, and see the Agent response.
- [First Server Primitive](https://vitehub.dev/raw/docs/getting-started/first-server-primitive.md): Create a small Vite server, add local KV through the ViteHub integration, and return one stored value from a route.
- [Installation](https://vitehub.dev/raw/docs/getting-started/installation.md): Install the ViteHub framework distribution, select a deployment preset, or choose a direct owner package for advanced composition.
- [Migrate from NuxtHub](https://vitehub.dev/raw/docs/getting-started/migrate-from-nuxthub.md): Move a Nuxt application from NuxtHub KV, Blob, and Database to ViteHub, and see which NuxtHub features have no ViteHub equivalent.
- [Server Primitives](https://vitehub.dev/raw/docs/getting-started/server-primitives.md): Add storage, queues, schedules, email, and other server APIs to a Vite app on any supported host.
- [KV](https://vitehub.dev/raw/docs/kv.md): Save small values such as settings and flags under a key, and read them back from any server route.
- [KV capability](https://vitehub.dev/raw/docs/kv/agent-capability.md): Give an Agent a KV read tool and, in write mode, a tool that puts or deletes one key.
- [KV configuration](https://vitehub.dev/raw/docs/kv/configure.md): Configure the Default KV Store, add named KV Stores, and select the KV driver that each host uses in production.
- [Store your first KV value](https://vitehub.dev/raw/docs/kv/get-started.md): Install KV, write a theme setting to a local KV Store from a server route, and read the same key back.
- [KV hosts](https://vitehub.dev/raw/docs/kv/hosts.md): Keep KV code portable across providers, read keys during development, and know production limits.
- [KV limits and errors](https://vitehub.dev/raw/docs/kv/limits-and-errors.md): Handle KV errors by stable code, and repair KV configuration, runtime, provider, and tool errors before production.
- [KV server API](https://vitehub.dev/raw/docs/kv/server-api.md): Read, write, and delete KV keys from server code with the public imports, the runtime helper, and application teardown.
- [Queue](https://vitehub.dev/raw/docs/queue.md): Send slow work to a queue so your route can reply at once, and run that work later on Cloudflare or Vercel.
- [Queue concepts](https://vitehub.dev/raw/docs/queue/concepts.md): Understand what queue acceptance, delivery, retries, and provider output mean for a Queue Definition.
- [Queue configuration](https://vitehub.dev/raw/docs/queue/configure.md): Configure the Queue Vite Integration, Queue Providers, generated names, and Queue Definitions.
- [Process a welcome job with Queue](https://vitehub.dev/raw/docs/queue/get-started.md): Define a welcome job, enqueue it from a route to Cloudflare Queues, and inspect the Queue Definition to verify delivery.
- [Queue hosts](https://vitehub.dev/raw/docs/queue/hosts.md): Check Queue discovery locally and inspect the Nitro output for Cloudflare and Vercel.
- [Queue limits and errors](https://vitehub.dev/raw/docs/queue/limits-and-errors.md): Handle Queue errors by code, repair Queue configuration errors, and check delivery guarantees before production.
- [Queue server API](https://vitehub.dev/raw/docs/queue/server-api.md): Enqueue Queue Jobs, handle delivery failures, and use the Queue Runtime Helpers from server code.
- [Rate Limit](https://vitehub.dev/raw/docs/rate-limit.md): Limit how many requests each client or user can make to a route, and reject the extra requests with a 429 error.
- [Rate Limit capability](https://vitehub.dev/raw/docs/rate-limit/agent-capability.md): Consume a Rate Limiter before an Agent Invocation starts, choose the identity to limit, and use a custom driver.
- [Guard your first request](https://vitehub.dev/raw/docs/rate-limit/get-started.md): Allow two requests per minute and check that the third returns HTTP 429.
- [Rate Limit hosts](https://vitehub.dev/raw/docs/rate-limit/hosts.md): Inspect the generated Rate Limit manifest and deploy managed Rate Limits to Cloudflare.
- [Rate Limit limits and errors](https://vitehub.dev/raw/docs/rate-limit/limits-and-errors.md): Know the enforcement, identity, and provider limits of Rate Limit before you rely on it in a production deployment.
- [Rate Limit server API](https://vitehub.dev/raw/docs/rate-limit/server-api.md): Require managed Rate Limits, read limiter decisions, and build direct limiters around drivers.
- [Realtime collaboration](https://vitehub.dev/raw/docs/realtime.md): Let several people edit one TipTap document at the same time, and save their changes to a file.
- [Realtime configuration](https://vitehub.dev/raw/docs/realtime/configure.md): Choose the room authority, control saves, and check what each host supports.
- [Create your first collaborative room](https://vitehub.dev/raw/docs/realtime/get-started.md): Connect two TipTap editors to the same document and verify synchronization.
- [Realtime limits and errors](https://vitehub.dev/raw/docs/realtime/limits-and-errors.md): Handle Realtime request errors by code, read room close codes, and repair Realtime configuration.
- [Realtime server API](https://vitehub.dev/raw/docs/realtime/server-api.md): Document adapters, editor codecs, structured documents, identity, authorization, saves, and checkpoints.
- [Package reference](https://vitehub.dev/raw/docs/reference.md): Find the ViteHub package and public import for each feature, from the vite-hub distribution to independent owner packages.
- [Config options](https://vitehub.dev/raw/docs/reference/config-options.md): Reference the main ViteHub Integration Options and where provider choices belong.
- [Doctor rules](https://vitehub.dev/raw/docs/reference/doctor-rules.md): Find ViteHub mistakes in application code with Vite Doctor, add the ViteHub rules, and read what each VHUB rule reports.
- [Errors and diagnostics](https://vitehub.dev/raw/docs/reference/errors-diagnostics.md): Reference ViteHub error codes and the local proof path for each primitive.
- [File conventions](https://vitehub.dev/raw/docs/reference/file-conventions.md): Reference the discovery paths that produce ViteHub Discovered Definitions and Discovery Identity.
- [Import paths](https://vitehub.dev/raw/docs/reference/import-paths.md): Distinguish stable ViteHub imports from generated files, provider modules, and internal package paths.
- [Render your first Markdown template](https://vitehub.dev/raw/docs/reference/markdown-template-tutorial.md): Install the Markdown Template package, bind data, and return rendered Markdown.
- [Markdown templates](https://vitehub.dev/raw/docs/reference/markdown-templates.md): Render deterministic Markdown from explicit data, bounded conditions, and fragments.
- [Provider output](https://vitehub.dev/raw/docs/reference/provider-output.md): Reference generated deployment and runtime artifacts owned by ViteHub package integrations.
- [Runtime Context](https://vitehub.dev/raw/docs/reference/runtime-context.md): Understand the host resources passed into a server operation or Agent request.
- [Runtime events](https://vitehub.dev/raw/docs/reference/runtime-events.md): Reference runtime event, policy, approval, stream, and usage records across ViteHub packages.
- [Runtime Helpers and stable imports](https://vitehub.dev/raw/docs/reference/runtime-helpers.md): Understand which ViteHub imports application code uses at runtime, keep configuration separate, and fix import failures.
- [Sandbox](https://vitehub.dev/raw/docs/sandbox.md): Run a small package as a Sandbox Task in an isolated cloud machine on Vercel or Cloudflare, and use its result in your app.
- [Sandbox capability](https://vitehub.dev/raw/docs/sandbox/agent-capability.md): Let an Agent run allowlisted executables in an isolated sandbox through one sandbox_exec tool.
- [Sandbox concepts](https://vitehub.dev/raw/docs/sandbox/concepts.md): Understand the boundary between a Sandbox Task Definition, its provider runtime, and the application that starts it.
- [Sandbox Task configuration](https://vitehub.dev/raw/docs/sandbox/configure.md): Lay out Sandbox Task package projects, free-form Definitions, entrypoints, and Definition options.
- [Run a package in a Sandbox](https://vitehub.dev/raw/docs/sandbox/get-started.md): Run a package that counts image pixels in Vercel Sandbox and return its JSON result.
- [Sandbox hosts](https://vitehub.dev/raw/docs/sandbox/hosts.md): Sandbox providers, host support, provider options, and Provider Output.
- [Sandbox limits and errors](https://vitehub.dev/raw/docs/sandbox/limits-and-errors.md): Know Sandbox timeouts, cancellation, and session reuse on each provider, and check a Sandbox before you ship it to production.
- [Sandbox server API](https://vitehub.dev/raw/docs/sandbox/server-api.md): Run Sandbox Task Definitions from server code with runSandboxTask(), and read the result, output, and errors of each run.
- [Schedule](https://vitehub.dev/raw/docs/schedule.md): Run server code at set times from files that deploy as cron on Cloudflare, Vercel, Deno, or a long-lived Node process.
- [Schedule configuration](https://vitehub.dev/raw/docs/schedule/configure.md): Configure the Schedule Vite Integration, the Process Runtime, Schedule Definitions, and storage.
- [Run a daily report once with Schedule](https://vitehub.dev/raw/docs/schedule/get-started.md): Declare a UTC schedule and execute one occurrence with the direct runtime API.
- [Schedule hosts](https://vitehub.dev/raw/docs/schedule/hosts.md): Understand Schedule Provider Output, the Process Runtime, development inspection, and production checks.
- [Schedule server API](https://vitehub.dev/raw/docs/schedule/server-api.md): Run Static Schedule Definitions on demand and read Schedule Runs from server code.
- [Shell](https://vitehub.dev/raw/docs/shell.md): Run shell commands from server code on files you choose, with limits on commands, output, and time.
- [Shell configuration](https://vitehub.dev/raw/docs/shell/configure.md): Select a Shell provider and set the runtime, session, and exec options that control what commands an Agent can run.
- [Run your first Shell command](https://vitehub.dev/raw/docs/shell/get-started.md): Search a read-only Workspace with Just Bash and inspect the command output.
- [Shell limits and errors](https://vitehub.dev/raw/docs/shell/limits-and-errors.md): Know the Shell call budget, background process, and command allowlist limits, and check Shell before production.
- [Shell server API](https://vitehub.dev/raw/docs/shell/server-api.md): Import Shell APIs, use Shell sessions, analyze commands, and read Shell Observations.
- [Source](https://vitehub.dev/raw/docs/source.md): Read files and data from your project, a GitHub repository, or your own code without changing them, and serve lists as paged API routes.
- [Source configuration](https://vitehub.dev/raw/docs/source/configure.md): Configure built-in Source loaders, cache policy, and custom loader definitions.
- [Read your first Source](https://vitehub.dev/raw/docs/source/get-started.md): Define a local glob Source, read one known Markdown file through it, and check the result from a server route.
- [Source hosts](https://vitehub.dev/raw/docs/source/hosts.md): Runtime requirements for each Source loader and the routes that need the Vite integration.
- [Source limits and errors](https://vitehub.dev/raw/docs/source/limits-and-errors.md): Path, symlink, secret, cache, and Collection checks for Sources in production.
- [Source server API](https://vitehub.dev/raw/docs/source/server-api.md): Open Source readers, register and combine Sources, cache readers, and expose typed Collections.
- [ViteHub UI](https://vitehub.dev/raw/docs/ui.md): Console-ready Vue components for chat, sessions, Agent runs, and code views.
- [Attachment](https://vitehub.dev/raw/docs/ui/attachment.md): Show a file with its upload state as a row or a tile, with an image preview, actions, sizes, and attachment groups.
- [Attachments](https://vitehub.dev/raw/docs/ui/attachments.md): Validate browser files, preview them, and convert them to AI SDK file parts.
- [Avatar Stack](https://vitehub.dev/raw/docs/ui/avatar-stack.md): Show who is in a document as overlapping avatars, with a count for the rest.
- [Chat App](https://vitehub.dev/raw/docs/ui/blocks/chat-app.md): A complete chat layout with a session list, streamed replies, and a prompt with attachments.
- [Code Review](https://vitehub.dev/raw/docs/ui/blocks/code-review.md): Review an Agent's changes with a file tree, a patch diff for the selected file, and the verification trace.
- [Collaborative Editor](https://vitehub.dev/raw/docs/ui/blocks/collaborative-editor.md): A document editor that shows who is in the room, the connection, the save state, and everyone's carets.
- [Bubble](https://vitehub.dev/raw/docs/ui/bubble.md): Frame message text in one of seven Bubble variants, align it to a side, group Bubbles, and attach reactions.
- [Carets](https://vitehub.dev/raw/docs/ui/carets.md): Style other people's carets and selections in a collaborative TipTap editor.
- [Chat](https://vitehub.dev/raw/docs/ui/chat.md): Render an AI SDK message list that follows streaming output and keeps the reader's scroll position.
- [Chat Message](https://vitehub.dev/raw/docs/ui/chat-message.md): Render one AI SDK UI message as a Message with a user Bubble and customizable part slots.
- [Chat Session](https://vitehub.dev/raw/docs/ui/chat-session.md): Present an application-owned chat session with a title and the same AI SDK message contract.
- [Code Block](https://vitehub.dev/raw/docs/ui/code-block.md): Show code, terminal output, logs, and diffs with a header, line numbers, and a copy button.
- [Code View](https://vitehub.dev/raw/docs/ui/code-view.md): Render syntax-highlighted files, and virtualized lists that mix files and diffs.
- [Connection Status](https://vitehub.dev/raw/docs/ui/connection-status.md): Show whether a realtime editor is connecting, connected, or reconnecting.
- [Diff](https://vitehub.dev/raw/docs/ui/diff.md): Render unified patches, file comparisons, parsed diffs, and merge conflicts with Pierre.
- [File Tree](https://vitehub.dev/raw/docs/ui/file-tree.md): Render Pierre's path-first file tree from Vue, control its expanded and selected state, and keep it accessible.
- [Build your first UI view](https://vitehub.dev/raw/docs/ui/get-started.md): Install ViteHub UI, render a local question and reply with the Chat component in a Nuxt application, and check the result.
- [Installation](https://vitehub.dev/raw/docs/ui/installation.md): Install ViteHub UI in a Nuxt or Vue with Vite application, set the theme, and verify the setup with server rendering.
- [Markdown](https://vitehub.dev/raw/docs/ui/markdown.md): Render streaming assistant Markdown with chat typography, math, and image previews.
- [Marker](https://vitehub.dev/raw/docs/ui/marker.md): Show an inline status, a note, or a labeled separator between conversation turns.
- [Message](https://vitehub.dev/raw/docs/ui/message.md): Lay out one conversation turn with an avatar, a header, content, and a footer.
- [Message Parts](https://vitehub.dev/raw/docs/ui/message-parts.md): Render every AI SDK UIMessage part type, including tools, files, sources, and typed data, with a slot for each type.
- [Message Scroller](https://vitehub.dev/raw/docs/ui/message-scroller.md): Compose headless message scrolling with live-edge following, prepend preservation, and message jumps.
- [Prompt Input](https://vitehub.dev/raw/docs/ui/prompt-input.md): Collect prompt text and file attachments with a submit control that follows the AI SDK chat status.
- [Sync Status](https://vitehub.dev/raw/docs/ui/sync-status.md): Show whether edits are loading, saving, saved, or not saved, with a custom label and an accessible live status.
- [Tool List](https://vitehub.dev/raw/docs/ui/tool-list.md): Render Agent tool contracts with labels, schemas, MCP origin, and call counts.
- [Trace](https://vitehub.dev/raw/docs/ui/trace.md): Show the steps an Agent takes as compact lines that can expand into detail.
- [Workflows](https://vitehub.dev/raw/docs/workflows.md): Run long tasks in steps, get a run id at once, and check the status and result later.
- [Workflow concepts](https://vitehub.dev/raw/docs/workflows/concepts.md): Understand workflow runs, durable steps, retries, and provider state before you design a long-running job.
- [Workflows configuration](https://vitehub.dev/raw/docs/workflows/configure.md): Set Workflow integration options, define Workflows, and add a durable Vercel entry.
- [Start your first Workflow](https://vitehub.dev/raw/docs/workflows/get-started.md): Define a two-step onboarding Workflow, start it from a route, and inspect the run id to follow its progress.
- [Workflows hosts](https://vitehub.dev/raw/docs/workflows/hosts.md): Select a Workflow Provider and its storage for each host: Cloudflare Workflows, Vercel, or OpenWorkflow with Postgres or SQLite.
- [Workflows limits and errors](https://vitehub.dev/raw/docs/workflows/limits-and-errors.md): Throw stable Workflow errors with structured codes, and check a Workflow and its provider before production.
- [Workflows server API](https://vitehub.dev/raw/docs/workflows/server-api.md): Start, defer, inspect, cancel, and resume Workflow Runs from server code.
- [Workspace](https://vitehub.dev/raw/docs/workspace.md): Give your server a folder of files to read and write, with rules for each path and a record of every change.
- [Workspace capability](https://vitehub.dev/raw/docs/workspace/agent-capability.md): Give an Agent Workspace inspection and file mutation tools, plus an optional allowlist of executables for Provider Drivers.
- [Workspaces and Sources](https://vitehub.dev/raw/docs/workspace/concepts.md): Choose a writable file tree, read-only content, or a combination of both.
- [Workspace configuration](https://vitehub.dev/raw/docs/workspace/configure.md): Configure the Workspace Vite integration, Store providers, Workspace Definitions, and Source Bindings.
- [Build your first Workspace](https://vitehub.dev/raw/docs/workspace/get-started.md): Read a mounted Markdown file and write a draft with explicit Workspace access.
- [Workspace hosts](https://vitehub.dev/raw/docs/workspace/hosts.md): Generated Workspace output, types, and Cloudflare Artifacts Store behavior on deployed hosts.
- [Workspace limits and errors](https://vitehub.dev/raw/docs/workspace/limits-and-errors.md): Local Store filesystem checks and recovery after a crashed process leaves lock markers.
- [Workspace server API](https://vitehub.dev/raw/docs/workspace/server-api.md): Read, write, diff, snapshot, sync, and run sessions on a Workspace from server code.

## Trust

Every page below is available as raw markdown.

- [About ViteHub](https://vitehub.dev/raw/about.md): Learn what ViteHub builds, how the project works, and where its public source and documentation live.
- [Contact ViteHub](https://vitehub.dev/raw/contact.md): Choose the right public or private channel for ViteHub support, bugs, security reports, and documentation changes.
- [ViteHub privacy](https://vitehub.dev/raw/privacy.md): Understand what the ViteHub documentation site handles and how that differs from applications built with ViteHub.