Running in DJINN

Code + review

DJINN + GitHub

DJINN writes code in a sandbox clone, has it reviewed by a different model family, and opens a pull request. It does not merge its own work.

Live in our own instance today — ask to see it work.

How it connects

01

Sandbox only, never the live tree

Writes happen in a separate clone. The running checkout and the process manager are off-limits, enforced at the tool layer rather than by instruction.

02

Cross-model review is the gate

Code written by one model family is reviewed by another, and a bare pass is not enough — the findings have to be clean. Our last two organs took seven and two rounds to get there.

03

A watcher reviews every PR again

A scheduled job re-reviews open PRs with new commits, so two independent model families see every change.

04

Repo activity digest

A weekday summary of commits, PRs and review state into Slack.

Worth knowing before you wire it

The unauthenticated API allows 60 requests an hour, which a single scan exhausts. A token with no scopes at all raises that to 5,000 — public reads need no permissions.

Documents

GitHub setup and reference.

Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.

  • RunbookThe build → review → merge loop
  • PolicySandbox boundaries
  • ReferenceReview verdicts and merge criteria

Want GitHub wired into your own company brain?

Request accessRequest handbookContact