Getting started
Hosted Doomer reviews GitHub pull requests for you. Install the GitHub App, choose repositories, and Doomer posts a check and review comments. You do not add a workflow file, install the CLI, or put a model API key in the repository.
What has to be true first
Hosted reviews run only for a project a platform administrator has enabled. There is no signup, plan, or provider picker in the project UI. Team owners cannot read or change the model provider, model ID, or API key.
Open the project and look at the sidebar:
- Repos, Stampy Stamp, PR comment voice, Review tracks, Deprecations, and Service maps appear only after hosted inference is enabled.
- GitHub under Source control, Integration catalog, and Review feedback stay available before that, so a team can prepare connections. Training remains available by its direct URL and does not start hosted reviews. See Custom training.
- Integration catalog lists Google Workspace, Tailscale, Jira, Shortcut, Linear, and GitHub Issues. Search by name or description, filter by tag or connection status, and sort by name or connected first. Google Workspace and Tailscale support multiple independent connections; issue trackers support multiple repository mappings with a shared credential.
- Service maps lives under Reviews. CI / OIDC lives under Administration.
If Repos is missing, ask Doomer to enable hosted inference for the project. Until then, repository switches and review settings are not available.
Owners and admins change these settings. Other members can view them.
Connect GitHub and turn on repositories
- Sign in and open the project.
- Open Repos at
/team/<namespace>/repos. - Choose Install GitHub App. That opens
/github/catalog/install?team=<namespace>and sends you to GitHub. - Grant the repositories you want Doomer to be able to see. If the organization requires approval, a GitHub organization owner must approve the installation.
- Return to Repos. Turn on the repositories that should receive reviews.
- Optional: turn on Automatically turn on new repositories for that installation. Repositories added to the App later are enabled. Existing choices stay as they are.
- Save repository settings.
GitHub decides which repositories the App can access. The switches on Repos decide which of those receive hosted reviews. To add repositories to an existing organization, use Manage installation, then Refresh access. Use Install on a new organization to connect another account. If the App is already installed, GitHub Integration (/team/<namespace>/github) has Connect or reconnect GitHub.
An installation is per GitHub organization or user, not per Doomer project. Repository-access changes apply everywhere that installation is used. Hosted reviews need exactly one enabled Doomer project for that installation. If more than one project has hosted inference enabled, reviews pause until a platform administrator disables the extra project.
Existing installations may need to approve newer App permissions before checks, issue reads, or automatic conversation updates work. Reviews can still be requested; the check explains when an older installation could not update conversations.
Open a pull request
Doomer reviews an open, non-draft pull request in a repository you enabled, when GitHub sends opened, reopened, synchronize, or ready_for_review. Automatic reviews is on by default. Keep a repository enabled and uncheck Automatic reviews in Repos to request reviews only with /doomer run or explicit reruns. Installing the App does not review pull requests that are already open. With automatic reviews on, those run on the next qualifying event, and a worker checks about every 15 minutes for missed webhooks.
On the pull request you should see:
- A Doomer check on the head commit. It starts queued, moves to in progress, then finishes success (no posted findings), neutral (findings), or failure (the review did not finish). This is an App check, not a GitHub Actions workflow.
- An informational review comment. Inline findings sit on the diff. Findings that are not on the diff go in the review body.
The project review page is /review/<project>/<owner>/<repo>/<number>. Hosted runs also show up under Runs at /team/<namespace>/runs.
An owner, organization member, or repository collaborator can comment /doomer run on any open pull request to queue the current head, including when automatic reviews are off or the pull request is a draft. Draft runs post review comments but never dismiss approvals, resolve earlier conversations, approve, or merge. Marking the pull request ready starts the normal review path. Doomer replies when it queues the review or when one is already active. Comments from contributors and other untrusted users are ignored.
What to configure next
| Goal | Where |
|---|---|
| Which findings are posted, and whether a summary comment is included | Repos |
| Wording, review passes, and deprecation warnings | Overrides |
| Automatic approval or merge | Stampy Stamp |
| Linked issues and what the review used | Issue sources and Intent and provenance |
| What Doomer learns from replies | Review feedback |
You do not choose --model-provider, --model, or a repository secret for this path. Local CLI runs and self-managed CI are a separate path and still use your own provider key.