Docs

[Getting started](#getting-started)[Connecting a repo](#connecting-a-repo)[Live previews](#live-previews)[Troubleshooting](#troubleshooting)[Self-host setup](#self-host-setup)[FAQ](#faq)

Operator guide

# Rondar docs

Get a repository into Rondar, start sessions, inspect previews, and recover from the common failure states.

## Getting started

Project and Settings links below require you to sign in first using your invitation.

01

Request access from the [access page](/access). Access requires an invitation. Open your private link and choose your existing sign-in method (GitHub, or Google when enabled).

02

Connect a supported coding-agent provider in [Settings → Account](/settings). Your provider subscription, usage charges, and rate limits are separate from Rondar.

03

Open [Projects → Add project](/projects?new=1). Choose GitHub to select a repository, Manual to enter its URL, or From scratch for a new project. For GitHub access, first use [Settings → Connections](/settings/connections). Wait for project setup to finish; inspect setup progress if it fails.

04

Create one small session: Projects → choose a ready project → New session. Describe a change you can review. Additional concurrent sessions are optional.

05

Watch the agent work, answer any questions, then review its result, changed files, checks, and pull request. When browser verification is useful, open the session's Preview tab and start a temporary preview. Reviewing one result completes the first-session goal.

## Connecting a repo

Rondar works with any Git repo you have access to. For private GitHub repos, connect a repository account with access in Settings → Connections. Organization restrictions may require additional authorization.

After cloning, a setup agent detects the tech stack and installs dependencies. Setup duration depends on the repository and dependencies. Follow its progress in the project; setup prepares the workspace but does not start or verify a preview server.

## Live previews

A session can create a temporary preview lease on demand from its **Preview** tab. When running, it gets a unique `*.rondar.app` URL pointing at the dev server inside that session's container. The proxy handles HMR WebSockets automatically, and the lease stops after inactivity so unused previews consume no runtime resources.

Preview preparation happens against the session's current workspace. Project setup does not start or verify a preview server, and visiting an expired preview URL does not create a new lease; return to the session's Preview tab to start one.

When an application defines distinct access contexts, the preview agent discovers the names and entry points from that application, prepares safe development data, and exposes the verified modes in the Preview selector. Rondar does not impose a built-in list of roles.

If you are wiring up a new framework, make sure the dev server binds to `0.0.0.0` and not `127.0.0.1`. The container-internal loopback is not reachable from the proxy.

## Troubleshooting

### My session output is blank

failed

Usually a provider-credential problem. Open Settings and confirm the account for the session's coding agent is connected, then try **Restart Session** from the session page. Historical Claude sessions remain readable, but cannot be restarted; choose a supported model for new work.

### My preview will not load

paused

Open the affected session's **Preview** tab and inspect the error or logs. Common causes are binding to `127.0.0.1`, a port collision, or a build step still running.

### I hit a plan limit

queued

Open [Settings → Billing](/settings/billing) to review capacity and upgrade. Running sessions keep going; only new session creation is blocked until you upgrade or one finishes.

### I want to remove my account

stopped

Open [Settings → Account](/settings) → Delete account and follow the confirmation flow. Deletion is permanent.

## Self-host setup

The first-run wizard creates the installation administrator. Operators must configure GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET and register the public callback URL ending in /auth/github/callback with their GitHub OAuth app. Use GITHUB_REDIRECT_URI for an explicit callback URL, or RONDAR_URL for the public base URL. Restart after configuration changes, then [retry setup](/setup).

For a callback or setup failure, check the server logs and verify that the public URL matches the registered callback. Do not share credentials in support requests. Hosted visitors should ask the workspace operator to finish setup, then open their private invitation.

## FAQ

Plan-level questions live on the [Pricing page](/pricing). If you hit something this page does not cover, email [support@rondar.app](mailto:support@rondar.app) and we will answer it here next.