Preview Environments for Repositories
A preview environment prepares your repository so new threads can start with its dependencies already installed. Each thread gets its own running environment, so you can work on different changes and open their previews at the same time.
Choose a repository
Section titled “Choose a repository”Workspace owners and admins who belong to the Space can configure its preview environment.
- Open Space settings → Details.
- Under Preview environment, select Choose repository and choose a GitHub repository. If prompted, add a GitHub connection to the Space first.
- Select Set up environment to start from scratch. To use a snapshot saved for this repository, select Reuse snapshot and choose its source Space.
The preview repository is independent of Space Context. You can keep Type, Google Drive, or Notion as your context source while running a GitHub repository. If your context source is GitHub, Use context repository selects that repository for the preview environment too.
If Type finds a saved environment for the same repository through the same GitHub connection in another Space you can access within your workspace, it can reuse it immediately. You can choose a different source with Reuse snapshot. The picker lists Spaces you can access that have a saved snapshot for the same GitHub repository, including through another connection. New threads use the selected snapshot with this Space’s environment variables.
Complete setup in chat
Section titled “Complete setup in chat”Type.com opens a setup thread with a short request and an attachment containing the detailed setup instructions. The agent reads the repository, installs dependencies, configures development services, and determines how to start the app. It asks you for missing information as needed.
When credentials are needed, use the secure input form in the thread and select Save and continue. Don’t paste secrets into chat or commit them to the repository. You can manage saved values in Space settings → Environment variables.
The agent verifies a representative workflow by running the app, the same way it verifies code changes. For an app with authentication, this includes logging in and using the app, not just reaching its login page. It looks for supported development login instructions in the repository and asks for help if it needs credentials or an action from you.
After verification and the blueprint pull request are complete, the agent saves the environment automatically. A Preview environment saved card confirms success in the thread. If setup is blocked, answer the agent’s question or provide the missing configuration, then continue in the same thread.
Open a preview
Section titled “Open a preview”When the preview becomes ready, Type.com opens it in split view. You can also choose New tab → Open preview environment in split view when the Space has a configured preview environment.
Use the preview’s back, forward, and reload controls to navigate. Keep feedback and follow-up changes in the same thread. To compare two changes, start separate threads and open each thread’s preview.
A new thread uses the saved environment as its starting point and starts its own app services. The snapshot saves setup work; it doesn’t mean the app is already running in every new thread.
Keep the setup recipe in your repository
Section titled “Keep the setup recipe in your repository”During setup, the agent creates or updates .type/blueprint.yaml and any supporting scripts, then opens a pull request and links it in the thread. Merge that pull request to keep the verified setup recipe with your code.
Future setups check .type/blueprint.yaml first. If it isn’t present, they check .devin/blueprint.yaml as a compatible starting point. The agent verifies and adapts the recipe to the current repository rather than assuming an older setup still works.
The blueprint describes how to reproduce setup and verification. It should contain instructions and variable names, not secret values. In Space settings → Details → Preview environment, select More preview options → View blueprint to read or download the saved recipe.
Update or rebuild
Section titled “Update or rebuild”Use Open setup thread to return to an unfinished setup. Under More preview options, Restart setup starts a fresh setup attempt. After an environment has been saved, Rebuild environment prepares and verifies an updated version.
While a rebuild is in progress, new threads continue using the previously saved environment. Once the replacement is saved, new threads use it. Existing threads keep their current environment.
Rebuild when changes to dependencies, services, or setup instructions need to become part of the starting environment for future threads.