Your engineering
agent.Remembers.

Careful pull request reviews in GitHub.
Sigma checks potential issues and brings
the evidence back to your code.

01 / A closer lookInside the pull request

From our own codebase.

A second look.
A real catch.

An early Sigma review on our Memory MCP Server: a missing ownership check, the author’s fix, and a recheck — all in one public thread.

Shortened here for readability.
The full reasoning and discussion are public.

Sigma Charlie v426 Sep 2026

The finding Summary

Anyone could open an issue with the expected title. The release workflow could then adopt it as its own tracker.

The author’s fixdfd072f

Check who opened it.

issue?.user?.type === "Bot" &&
issue?.user?.login ===
  "github-actions[bot]" &&

Added checks · excerpt from isWaveIssue

Sigma · Rechecked

“Agent-adjudicated outcome: fixed.”

02 / In your workflowGitHub → Sigma → GitHub

One repository. One pull request.
A useful place to begin.

01
Follow your invitation.
Sign in with the GitHub account named in your invitation.
02
Choose a repository.
Start with reviews on request. You choose when Sigma takes a look.
03
Ask for a review.
Comment /sigma review on a pull request. The result comes back to GitHub.

03 / Closed beta

A small group. Real projects.

Tell us what you’d like to try.
We’ll be in touch when there’s a place.

A request does not grant access automatically.

For your first visit, open your invitation link.