affine.earth · download · Affine IDE 0.2.6.5 · β

Affine IDE for macOS β

Affine IDE is the substrate's native macOS client — a Swift 6.4 app that edits, compiles and projects against Affine.Earth with no browser in the path. It is a sovereign peer of the browser client rather than a companion to it: both speak to the same apex at https://affine.earth/language-invariant/mcp, and neither is upstream of the other.

Public beta · macOS Apple silicon

What’s new in this release

Full install notes: wiki · Affine IDE install notes

Download β · AffineIDE-0.2.6.5.dmg 5976.7 KiB · 6120184 bytes · Apple silicon · macOS 14.0 or later

What you are downloading

measured from the file this page links to — 2026-10-07T21:31:44Z
file
AffineIDE-0.2.6.5.dmg
version
0.2.6.5 (build 3300)
size
6120184 bytes (5976.7 KiB)
sha256
4daa481b270542b5f414e1069d19fd22ceb75d225ebfabdd6673c61887051e2b
architecture
arm64 — Apple silicon only, no Intel slice
minimum macOS
14.0 (LC_BUILD_VERSION minos, read from the binary)
signed by
Developer ID Application: Richard Gillespie (WWQQB728U5)
team
WWQQB728U5
notarized
notarized & stapled
how these were taken shasum -a 256 file <binary> otool -l | LC_BUILD_VERSION codesign -dv xcrun stapler validate

Every value above except the last is read off the .dmg at deploy time by cells/xcode/scripts/cell-deploy/deploy-affine-ide-dmg.sh and substituted into this page — none of them is typed by hand. notarized is the verdict of xcrun stapler validate run on the app inside the image at deploy time, and the chip at the top reads prod only from a court sign-off bound to this file's sha256.

Check what you got

The file is served by all nine apex cells. Run this and compare the line it prints to the sha256 above — if they differ, you do not have this file, whatever the page said when you clicked.

shasum -a 256 ~/Downloads/AffineIDE-0.2.6.5.dmg

Expected: 4daa481b270542b5f414e1069d19fd22ceb75d225ebfabdd6673c61887051e2b. The same digest is published beside the .dmg as AffineIDE-0.2.6.5.dmg.sha256, in the format shasum -c reads.

Install

  1. Open AffineIDE-0.2.6.5.dmg.
  2. Drag Affine IDE onto the Applications shortcut in the same window.
  3. Eject the disk image.
  4. Double-click Affine IDE. It opens — this build is notarized and stapled.

First studies (domain first)

  1. Open Study → ATC airspace — live ADS-B on the scope; photographic surface cam on the right; chat narrates the LIVE line.
  2. Protein folding — Mol*-style cartoon, residue strip, Orbit / Pan / Zoom.
  3. If chrome says LIVE surface: KTEB (FAA) · KJFK tracks, that is intentional honesty: KJFK has no public WeatherCam. Use seat KTEB to align, or stay on KJFK tracks with the mismatch labeled. No fake KJFK runway photo.

Longer notes: Affine IDE install notes · wiki.

First open

This build is signed, notarized and stapled. It is signed by Developer ID Application: Richard Gillespie (WWQQB728U5), it has been through Apple's notary service, and the ticket is stapled to the disk image — so it opens by double-clicking on a Mac that has never seen it, with no override and no trip through System Settings, and it does so even if that Mac is offline.

Nothing is wrong with the file. The sha256 above is how you confirm that for yourself, and the signature is checkable without trusting this page:

codesign -dv --verbose=2 /Applications/AffineIDE.app

Double-click it. That is the whole procedure.

There is no Control-click step, no System Settings override and no “Open Anyway”. Gatekeeper checks the stapled ticket and lets it run, offline included. If your Mac does refuse this build, something is wrong with the download rather than with your machine — check the sha256 above against your copy and tell us, because that is a defect on our side.

For the record of what changed: 0.2.1 and earlier were signed but NOT notarized, and on macOS 15 and later Apple removed the Control-click bypass those builds relied on (“users will no longer be able to Control-click to override Gatekeeper” — Updates to runtime protection in macOS Sequoia). Those builds could not be opened on a current Mac by any documented route. This one can, by the only route that should ever have been needed.

Where it connects

Affine IDE talks to the apex over the same door the browser client uses: https://affine.earth/language-invariant/mcp. There is no separate backend, no account, and no telemetry endpoint — the app is a peer on the mesh, and what it sends is what you ask it to send.