Skip to main content

​
Connect a repository

  1. Sign in at app.diffraction.sh and select your workspace.
  2. Open Repos (/install) and start the GitHub installation from Diffraction.
  3. Select the repositories to make available and finish GitHub authorization.
  4. Return to Repos and open the connected repository’s settings.
  5. Check the detected application setup. Add configuration if the project needs custom commands, routes, or test data.
Starting from Diffraction binds the installation to your authenticated workspace. GitHub access is verified before saving the connection. Supported Node web apps can use automatic configuration; a diffraction.yml file is no longer required. A connected repository still needs an active developer entitlement, available credits, and working application setup before a review can execute.

​
Automatic reviews

Pull request actions opened, reopened, synchronize, and ready_for_review enter review intake. Diffraction resolves immutable source revisions and evaluates UI impact using changed files and repository trigger rules. Changes that do not need browser review can be skipped. Selected existing tests have their own standing coverage behavior. Each review reports its revision. The GitHub integration maintains a Check and summary with authenticated viewer links instead of posting a separate comment for every finding. A newer commit is new source; old evidence does not cover it.

​
Request another PR review

A person with GitHub write, maintain, or admin permission can post a new PR comment containing:
Diffraction adds a 👀 reaction to the triggering comment after the review workflow is accepted. Text after the mention becomes review-scoped guidance for the planner, browser agent, and analysis. For example:
Guidance is limited to 4,000 characters and applies to that request. It does not change repository configuration or workspace rules. A reaction failure does not cancel an accepted review. Both PR conversation comments and inline review comments are supported. This requests a review of the PR’s current head and uses workspace review credits. A mention inside a quote or code block is ignored, as are bot comments and edits to an existing comment. Duplicate delivery of the same comment does not create another paid request. A new comment is a new request. From an existing hosted PR review, open its rerun control. It starts with the reviewed commit SHA; you can enter another full 40-character SHA in the connected repository and choose Use this commit. The confirmation shows the selected revision and credit cost. This differs from a GitHub comment request, which resolves the PR’s current head. Merely opening or cancelling confirmation starts no work and reserves no credits. Confirmation expires after ten minutes; eligibility and cost are rechecked before dispatch. Repeating the original revision preserves its comparison base; selecting another commit uses its first parent (or itself for a root commit). The confirmed request creates a separate review of that selected revision. Commit/local-source reviews without a PR use a new CLI/MCP request instead of this PR review rerun control.

​
Review each commit

Under Repos → repository → Overview, an administrator can enable Review each commit. It is off by default. New automatic PR reviews enter a per-PR queue in arrival order, keeping each accepted head SHA even if the PR advances. Duplicate webhook deliveries share one queue entry. Credits are reserved when each run begins, and each run has its own credit settlement. Switching this setting off affects new admissions; already queued reviews retain their accepted behavior. Compatible public, same-repository revisions may reuse an application environment after a clean reinstall and restart. Recordings and browser harnesses are fresh. Private repositories and forks use fresh environments. No measured speed or cost improvement is promised for this option. Without this option, stale automatic heads can be superseded by newer PR changes. Manual requests remain separate from the automatic commit queue.

​
Permissions and access

The App uses read access to repository contents and metadata and read/write access to Checks and pull requests for publication. Organization Members: read supports GitHub member suggestions in Team; existing installations may need to accept that permission. GitHub credentials remain outside the reviewed application’s commands. An installation can be removed or suspended independently of workspace membership. Check both when a formerly available repository stops working. Operators maintaining a deployment can use the repository’s GitHub setup reference.