> ## Documentation Index
> Fetch the complete documentation index at: https://developers.reintersect.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Previews and versions

> Preview a version on your own development install, open pull request previews in the playground, and publish to production.

> Reintersect apps are in developer preview. Names and limits can still change before general
> release.

Every deploy creates a version. A version is either a preview, which only development installs run,
or the published production version, which workspace installs run.

| | Preview | Production |
| - | - | - |
| Created by | `reintersect dev`, `reintersect deploy --preview`, the [agent builder](/agent-builder), or the [GitHub Action](/ci) on a pull request | `reintersect deploy`, the GitHub Action on the default branch or a tag, approving a publish request, or a rollback |
| Runs on | Development installs that pick it | Workspace installs (and development installs that pick it) |
| Environment variables | Preview values | Production values |
| Signing secret (hosted) | A secret derived from the app's, bound only to previews | The app's signing secret |
| Status | Preview | Published, then Superseded by the next one |

## Who moves to a new preview

A preview never moves a workspace install. It moves at most one development install, so a
teammate's preview or a pull request never takes over yours:

| Who deployed the preview | Development installs that move to it |
| - | - |
| You, with `reintersect dev` or `deploy --preview` | Only yours. |
| The agent builder, for you | Only yours. |
| A pull request, through the GitHub Action | None. |

Deploying the same code and manifest as an existing preview, for example one a pull request already
built, moves your own development install onto that preview instead of creating another version. A
new development install starts on the published version, or on your own newest preview when there is
no published version.

## The playground

The playground (**Settings → Developer → Apps → your app**, or the link the CLI prints) renders your
blocks through your development install, in interactive, read-only and agent text modes, and lets you
try your references by pasting a URL. A version picker shows which version your development install
runs and lets you switch it to any recent preview or the published version.

A playground link for a specific version, such as the one the GitHub Action comments on a pull request,
opens with "This link opens vN. Your dev install runs vM." and a **Run vN** button. It never switches
your install without that click.

## Production

A production deploy publishes the new version at once and supersedes the previous one. Installs move
to it when it asks for no more access than they approved; otherwise they stay on their version until
an admin approves. See [Publishing new versions](/concepts/install-and-consent#publishing-new-versions).

Production moves development installs too, under the same access rule, so after a production deploy
your development install runs the published version until your next preview.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.