---
title: "Cloud setup"
description: "Take a GitHub repository from your first cloud thread to a pull request."
canonical_url: "https://hoplite.sh/docs/quickstart"
markdown_url: "https://hoplite.sh/docs/quickstart.md"
---

# Cloud setup
URL: /docs/quickstart
LLM index: /llms.txt
Description: Take a GitHub repository from your first cloud thread to a pull request.
Related: /docs/agent-ready, /docs/threads/run, /docs/github

# Cloud setup

Connect a repository and run your first coding task in a managed cloud workspace. Hoplite prepares the environment, runs the agent, and keeps the conversation, code changes, and preview together for review.

A cloud thread needs a Hoplite team workspace, a GitHub-backed project, and available billing access. The team workspace owns members, projects, and billing; each cloud thread gets a separate execution workspace for its files and processes. For a backend integration, start with [Build a software factory](/docs/factory). For execution on your own machine, use the [desktop app](/docs/desktop).

## Connect a repository

1. Sign in at [hoplite.sh](https://hoplite.sh) and create or select your workspace.
2. Install the Hoplite GitHub App on the account that owns the repository. Grant it access to that repository.
3. Select the repository to create a project. Check its base branch under **Settings → Project → Repository**.

GitHub sign-in and GitHub repository access are separate: signing in with GitHub does not replace installing the App. A project can bind multiple repositories, each with its own base branch.

Hosted Free enrollment requires a billing address and a non-prepaid card, without a charge at enrollment. See [Billing](/docs/workspace/billing#free-signup-and-pro-trials) for eligibility and plan details.

## Configure execution

Add the commands your repository needs to [`.hoplite/settings.json`](/docs/agent-ready), and add secrets under **Settings → Project → Environment**. Hoplite clones the selected revision and runs setup before the agent begins work.

Project settings can override the repository file. If setup runs an unexpected command, check [configuration precedence](/docs/sandboxes/scripts#how-scripts-resolve).

## Start a thread

Create a thread in the project and select its repository, source branch, and model. To continue an existing PR, select **PRs** in the source picker instead of **Branches**.

Send the task. The activity timeline shows workspace setup followed by agent execution. If setup fails, expand the setup entry for the failing stage and available log output before retrying.

Messages sent during a run can queue for later or steer the active run. See [Run a thread](/docs/threads/run) for the exact keyboard behavior and cancellation rules.

## Review the result

Open **Views → Diff** in the thread to inspect the changed files and patches. The cloud diff compares the thread workspace against its base branch. Use [Preview](/docs/sandboxes/previews) for the running application and inspect verification output in the activity timeline.

If the result needs changes, send a follow-up in the same thread so the agent continues in its existing workspace. See [Review and approve work](/docs/threads/review#review-the-diff).

## Publish the change

Use `/pr` or ask the agent to open a draft PR. The PR panel shows checks, reviews, and unresolved comments. **Attach all comments** brings review feedback into the conversation; **Merge** uses a method allowed by the repository.

[PR autofix and auto-merge](/docs/github#the-review-loop) are separate controls. Check their effective settings before leaving a thread unattended.

## Sitemap

Sitemap discovery is not enabled for this deployment.