NEONDIFFNeonDiff
sign in
public paid BYO Mac beta // exact beta.75 download and production checkout

NeonDiff // native Mac beta

your first review.
one Mac app.

A local-first public paid BYO Mac beta. Your review worker runs on your Mac; model-bound context goes only to the provider or local endpoint you choose.

release truth
Mac artifact
beta.75 · build 11079
checkout
production live
public launch
paid BYO beta
public paid BYO Mac beta

Customer-owned GitHub App. Native setup. No hidden operator repair.

This public beta is available without an invitation. It is paid for every desktop repository. A customer can install their own GitHub App or select an exact server-verified compatible existing local agent. NeonDiff either keeps the new private key in Keychain or reuses the matched local agent without copying its credential, then verifies only the selected Review Target before useful work. The official managed-App is a later convenience path and is not included in this beta.

  1. 01Select a detected account and bot on an existing Mac; NeonDiff restores it without moving secrets
  2. 02Initialize Local Config only on a clean install (never force-overwrites an existing config)
  3. 03Store the customer-owned GitHub App ID and private key in Keychain for a new bot
  4. 04Or reuse the exact matched local agent without copying its credential
  5. 05Add one owner/repo and apply the repository allowlist for a new bot
  6. 06Quit and relaunch safely: NeonDiff restores the same pending bot and config path
  7. 07Choose one Review Target without rewriting the worker's other repositories
  8. 08New bot: Verify App Access for that exact target before running a scoped dry review
  9. 09Existing bot: Verify existing access; NeonDiff refreshes the matched worker's live API entitlement without asking for its Activation Key

Public beta available // exact signed download, production activation, and customer-owned GitHub setup

existing setup

Reuse an existing local agent

Select an exact compatible NeonDiff agent already configured on this Mac. The native app restores the matching account, bot, repository, provider, and entitlement without copying its GitHub private key.

A paid NeonDiff Activation Key and verified Provider Key are still required before useful review work.

[ Download NeonDiff 1.1.0-beta.75 ]
new setup

Set up your own GitHub App

Create and install a customer-owned GitHub App, store its private key in Keychain, choose a repository, and verify exact access before the first dry review.

If setup is interrupted, relaunch returns to that same pending bot instead of selecting an older local bot or creating another config directory.

After verified purchase fulfillment, the NeonDiff Activation Key is retrieved once and stored by the native app in Keychain. It is separate from your Provider Key.

[ Choose a paid plan ][ Download NeonDiff 1.1.0-beta.75 ]

customer path

from download
to first review.

No terminal or configuration-file ceremony in the normal Mac journey. Every screen names one next action and preserves progress for retry.

  1. 01

    Download and launch

    Install the exact signed and notarized Mac release.

  2. 02

    Activate the paid beta

    Complete verified checkout and store the one-time NeonDiff Activation Key in Keychain.

  3. 03

    Connect GitHub

    Use your customer-owned GitHub App or select a compatible existing local agent.

  4. 04

    Choose repositories

    Select only the repositories NeonDiff should review.

  5. 05

    Verify provider

    Store a Provider Key in Keychain or choose a local model.

  6. 06

    Run a dry review

    Inspect the first result before anything is posted.

  7. 07

    Enable live reviews

    Opt in only after the dry result looks right.

Mac requirements

Download NeonDiff 1.1.0-beta.75 build 11079 for Apple Silicon Macs running macOS 14 or later. SHA-256:b46b3fe2899f4797edc7853f8684dec029c787aeae350e145925a1d01778b171

Keys stay distinct

A NeonDiff Activation Key proves paid entitlement. A Provider Key authenticates only to the model provider you select. Neither belongs in a URL, analytics event, log, or browser storage.

Recovery and support

Entitlement loss fails closed. Replacement activation, manual signed update, rollback, and relaunch were exercised against beta.75. If an Activation Key is lost or revoked unexpectedly, contact support with the account email and checkout session ID—never the key itself.

→ contact support