Overview
Sigma user documentation
Sigma reviews pull requests from GitHub. Choose a PR, confirm the launch and read progress and results in the Sigma workspace. You can also read and discuss published findings on the pull request. One GitHub App, Sigma Mnemoverse, posts the reviews.
Access and feedback
On installations with public registration enabled, create a Mnemoverse Account or sign in to start using Sigma; no invitation is needed. Connect the GitHub account linked to your Mnemoverse Account, then choose a repository you administer. If public registration is not enabled, an invitation is still required; follow the maintainer's access instructions.
Your current plan and limits apply. Sigma preserves existing plan rights; if you have no plan, registration uses the configured Free plan. Signing in again does not reset your allowance or renew expired rights. If your plan cannot be confirmed, retry the account check instead of creating another account.
Memory is an optional Beta feature and starts off for new accounts. You can review without connecting Memory. To use it, explicitly connect and enable Memory in Connection. Existing accounts keep their saved Memory preference.
Thank you for trying Sigma. Positive and negative feedback are both welcome: tell us what you were doing, what you expected, what happened, and whether a review was useful.
To send feedback or get help, write to
[email protected], and mention Sigma. If a review is involved, include the
pull request link and the check title. The
Mnemoverse contact page lists the same
address.
Getting started
Open Sigma, create your Mnemoverse Account or sign in; no invitation is needed on public-registration installations. Use your linked GitHub account and allow access to a repository you administer. Follow setup prompts only for missing connections. Under Connect account for reviews, choose Connect account and approve review access if prompted. Memory consent is separate and optional.
Keep your saved connections. You do not need to add the same computer, accounts or repositories again for each review.
- Choose PR. Open Reviews, choose New review, then select a connected repository and an open pull request. Choosing a PR does not start work.
- Confirm launch. Check the PR and commit, configured reviewers, Runs on and Paid by. Maximum for this request is the limit for the whole request, separate from your account allowance. Checking the cost creates no reservation. Choose Start review with the displayed maximum when ready.
- Progress and result. Keep the saved request link. It shows the recorded status, each reviewer's work and links to available results in Sigma. GitHub delivery and Billing are separate: a result can be readable before publication or the final charge is confirmed. Read verified findings first (Reading a review).
If something needs attention, use the action on that step. A connection repair returns to the same PR; a cost retry checks the same selection. Neither starts a review automatically. Changed PRs or conditions need fresh confirmation.
If the response to Start review is lost, check that same saved request. A review or reservation may exist; do not start another. Leaving the page does not cancel work (Limits and budget).
Prefer GitHub? Comment /sigma review on the PR as an alternative. The
caller needs write access (Who may call Sigma).
Saved reviewer modes still apply. On request starts reviews only when asked;
Automatic can also start them after PR events.
With Sigma's gateway executor, the review container has no network. It reads
your code and the change;
it cannot download dependencies, and tests that need the network do not run.
Each review records which checks ran and what could not be read or executed
(Reading a review).
Current availability
Account registration, GitHub repository access and review readiness are separate. A connected account or repository does not guarantee that a review can start: your plan, the selected reviewers and the current service limits still apply.
Connection shows the computers, accounts and repository settings saved for your workspace. A saved computer or provider sign-in is not the same as current readiness: the computer must be available, its sign-in must work and its use must be permitted for the repository. Follow the displayed reason and recovery action if a selected resource needs attention. The review request and result show what actually ran; a setup screen alone does not prove a successful review.
If setup does not finish
Wide tables: scroll horizontally to see more columns.
| What you see | What to do |
|---|---|
| Returning to Sigma or opening an old invitation link | Open Sigma and sign in. Existing members keep their account and plan history. |
| GitHub account does not match | Use the GitHub account linked to your Mnemoverse Account. Check the Signed in as badge on Connection before saving. |
| Plan could not be checked | Retry the account check. If it stays unavailable, contact support; a failed check does not mean you have no plan. |
| Plan expired or access revoked | Use your Account settings or contact support to resolve it. Registering again does not renew rights or remove a suspension. |
| Repository missing or not permitted | Check the App's selected repositories with Manage on GitHub, your GitHub administrator access and your plan's repository limits. An organization owner may need to approve the installation. If it is still excluded, contact support. |
| Repository connected by another account | Ask that account or the Sigma maintainer to resolve the connection; another sign-in does not take it over. |
| Connected repository is not ready for review | Use the displayed action to enable or repair that repository. An empty review list does not by itself mean GitHub needs connecting again. |
| Cost could not be checked or confirmation expired | Stay with the selected PR and use Check cost again or Update confirmation. A cost check does not start work. |
| Start response or request status is unknown | Use Check this request again on the same saved request. A review or reservation may exist; an unavailable status is not proof that nothing started. |
| No check after a review request | Confirm the repository is enabled, a reviewer is Automatic or On request, and the caller has write access. Check for an existing queued run before sending a new request; see Who may call Sigma. |
When asking for help, describe the step and displayed reason; do not include sign-in codes, old invitation secrets or provider credentials.
What Sigma is
- It reviews a snapshot of the pull request's exact head and base commits.
- A producer proposes findings; a fresh verifier checks them. Only confirmed findings count as verified.
- A reviewer is a lineage (Bravo or Charlie) at a version on an executor. Each configured reviewer has its own mode, findings and history, and several reviewers can review the same pull-request state.
- Each reviewer posts one neutral progress check and one review with up to five inline findings. Rules can add a separate Approve or Request changes when its requirements pass.
- For hosted reviews, after a push, an Automatic reviewer reviews the new head and then follows up on its own earlier findings.
What Sigma is not
- Sigma never merges pull requests or edits your code. Its permissions allow reviews and checks, not commits.
- A neutral progress check is not an approval. Branch protection stays with the repository's administrators; Sigma configures no merge gate.
- A configured reviewer is not proof that its login works, that the login belongs to the person reading the page, or that a usage estimate is a bill. Execution and costs are kept separate.
- Creating an Account does not grant access to someone else's repositories. Connecting repositories requires the App installation, current GitHub administrator permissions and your Sigma plan's repository access. Signing in to Mnemoverse, granting GitHub access and authorizing a model provider are separate connections.
Who this documentation is for
The main text is written for a developer who requests and reads reviews in Sigma or GitHub. Three other readers get short callouts where their situation differs:
For coding agents. An agent acting on a review in an automated loop: what to parse, what counts as a finding, what a selector may and may not do.
For maintainers. The person who connects repositories, chooses modes, replies in finding threads and watches the budget.
For operators. The person running an instance: executors and logins, caps, waiting windows, rebinding. Procedures live in the operator runbooks under
docs/runbooks/; this documentation only says what they affect.
How to read this documentation
Earlier review behaviour descriptions were checked against Sigma's deployed code on 8 October 2026. The registration and first-review instructions follow the current source screens, updated on 2 November 2026. Another installation may run older reviewers, other executors, or Comments without Rules. Read the identity and recorded status on the actual run. Not yet available marks behaviour that is planned or designed but not shipped. Historical reviews and checks keep the wording and version they were published with.
Pages
- What Sigma does with your code: what is fetched, what cannot be reviewed, where it runs, what leaves the host, what is kept, the secret guard.
- Reviewers and executors: lineages and versions, the two stages, three execution paths, costs, provider constraints, waiting, choosing one reviewer.
- Modes and requests: Automatic, On request, Off; connecting a repository; explicit requests; permissions; drafts; pushes; catch-up after downtime.
- Reading a review: check titles, notices, the review's layout, severity, verification, the aggregate verdict, what agents can parse and the run page.
- Replies and rechecks: deferral, targeted rechecks, what a push does to open findings.
- Limits and budget: holds, waiting, what the maintainer can do, quotas.
- Glossary: the terms used throughout Sigma.