# Guides

Each guide takes one job from start to finish, with Volobox open beside it: what you need first, numbered steps, how to tell it worked, and where to go next. Pick the one that matches what you want to do; you do not need to read them in order.

## Before you begin

- **A Volobox workspace.** If your team does not have one yet, [request a demo](/demo): we set up your own workspace the same day, followed by a 30-day free trial.
- **The right role for the job.** Guides that change the workspace (connecting a code host, adding a model provider, registering an integration app) need an administrator. Each guide says which permission it needs under **Before you begin**.
- **For developer guides,** a terminal with `curl`, or Node.js, .NET or Python if you want to run the code examples as they are.

## For developers

Build on Volobox from your own code and tools.

- [Make your first API call](/docs/first-api-call): create a personal access token and call the HTTP API with curl, Node.js, C# or Python.
- [Connect an MCP client](/docs/connect-mcp-client): give an AI client access to your Volobox work through the hosted MCP server.
- [Build an OAuth integration](/docs/oauth-integration): sign people in with authorization code and PKCE, or export the audit log as a service.
- [Receive and verify webhooks](/docs/receive-webhooks): get events as they happen and check every delivery's signature.

## For teams that code

Let coding agents take work from a task to a reviewed pull request.

- [From a task to a pull request](/docs/task-to-pull-request): link a repository, assign a task to a coding agent and review what it opens.
- [Write a preview manifest](/docs/write-preview-manifest): describe how your app runs so every branch can be tried, and add checks that run before an agent's pull request opens.
- [Guide coding agents](/docs/guide-coding-agents): tell agents and the AI reviewer how your team works, in the repository and in Volobox.
- [Run coding sessions on your own machine](/docs/own-machine): run sessions on a computer you own, and use your Claude subscription with Claude Code.

## For automation and apps

Automate the work between your systems and build the tools your team is missing.

- [Write a code workflow](/docs/write-code-workflow): a workflow whose steps are JavaScript, rehearsed before it runs for real.
- [Build an app](/docs/build-an-app): describe an app to the Builder, try the draft, and publish it.
- [Call other systems from an app](/docs/call-external-systems): call a REST API with a bound secret, and receive signed webhooks.
- [Create a skill](/docs/create-a-skill): package instructions and reference files for an agent, and add a slash command.
- [Host a pack registry](/docs/host-pack-registry): share library packs between workspaces from your own HTTPS registry.

## For administrators

Connect Volobox to the systems your organization already uses.

- [Connect GitHub](/docs/connect-github), [Connect GitLab](/docs/connect-gitlab) and [Connect Azure DevOps](/docs/connect-azure-devops): register repositories for projects and coding sessions.
- [Set up Microsoft Entra ID sign-in](/docs/entra-id-sign-in): let members sign in with their Microsoft accounts.
- [Add a model provider](/docs/add-model-provider): bring your own model keys and choose the models agents use.

## How the guides are written

- UI labels are in **bold**, exactly as Volobox shows them, and a location is described by the labels you click through.
- Examples use `https://volobox.example.com` for your workspace address. Replace it with your own.
- Tokens and secrets are placeholders such as `$VOLOBOX_TOKEN`, `vbpt_...` or `whsec_...`. Never paste a real secret into a script you share.
- Each page says when it was last checked against the product, at the bottom.

## Related

- [Introduction to Volobox](/docs/introduction)
- [Reference](/docs/reference)
- [Glossary](/docs/glossary)
