# Concepts

ViteHub adds server features to Vite applications and lets Agents use selected features through Capabilities. These pages explain the terms that connect those two paths.

For setup and API options, go to [Server primitives](https://vitehub.dev/docs/getting-started/server-primitives), [Agents](https://vitehub.dev/docs/agents), [Capabilities](https://vitehub.dev/docs/agents/capabilities), or [Reference](https://vitehub.dev/docs/reference).

## Start here

| Page | Read it when |
| --- | --- |
| [Server primitives](https://vitehub.dev/docs/getting-started/server-primitives) | You need storage, background work, auth, isolated execution, or another server feature. |
| [Agents](https://vitehub.dev/docs/agents) | You need a named actor that runs with a model, coding provider, or application code. |

## Core vocabulary

| Page | Defines |
| --- | --- |
| [Definition discovery](https://vitehub.dev/docs/getting-started/concepts/definitions-and-discovery) | How ViteHub finds and names a definition file. |
| [Agent Invocations](https://vitehub.dev/docs/agents/invocations#what-happens-during-an-invocation) | What ViteHub resolves and records for one Agent request. |
| [Capabilities](https://vitehub.dev/docs/agents/capabilities#choose-the-api-by-its-caller) | How an Agent receives a selected ability. |
| [Workspace and Sources](https://vitehub.dev/docs/getting-started/concepts/workspace-and-sources) | How a writable file tree differs from the read-only content mounted into it. |
| [Auth Users and Agent Invokers](https://vitehub.dev/docs/getting-started/concepts/auth-users-and-agent-invokers) | How application identity becomes trusted invocation identity. |
| [Channels](https://vitehub.dev/docs/agents/channels#channels-and-invocations) | How messages and delivery facts reach an Agent. |

## Runtime execution

| Page | Defines |
| --- | --- |
| [Runtime Context](https://vitehub.dev/docs/getting-started/concepts/runtime-context) | The host resources available to a server operation or Agent request. |
| [Runtime Helpers and stable imports](https://vitehub.dev/docs/getting-started/concepts/runtime-helpers-and-stable-imports) | The imports application code uses to call ViteHub. |
| [Runtime policy, approvals, and traces](https://vitehub.dev/docs/getting-started/concepts/runtime-policy-approvals-and-traces) | The records that explain whether work ran, waited, or failed. |

## Host and build model

| Page | Defines |
| --- | --- |
| [Vite Integrations and Provider Output](https://vitehub.dev/docs/getting-started/concepts/vite-integrations-and-provider-output) | How ViteHub prepares a package for development and deployment. |

## Next steps

Open [Installation](https://vitehub.dev/docs/getting-started/installation) for a runnable project. If you already know what you need, go to [Server primitives](https://vitehub.dev/docs/getting-started/server-primitives) or [Agents](https://vitehub.dev/docs/agents).