ankle.website
ANKLE SETUP.EXE — canonical public distribution
One shareable link · current verified releases

Get ANKLE.

Three downloads. No wallet, no store, no waiting. Get the Mac workspace, the browser overlay, or the website widget. Each is versioned and checksum-published.

↓ ANKLE.app 1.0.39 (59.0 MB) ↓ Extension 1.6.15 (140 KB) </> Widget embed 2.1.12

No wallet is required. App sign-in uses your ANKLE account and browser-extension handoff; financial and token rails are not part of installation.

The older combined Field Kit is a compatibility snapshot; current components ship separately.

1. Install the macOS app

ANKLE.APP 1.0.39 — DIRECT PREVIEW
strict code-sign check passednot notarized58,978,390 bytes

Version 1.0.39 requires Apple silicon and macOS 12 or newer. It is ad-hoc signed and hash-published, but not Apple-notarized and not distributed through the App Store. Gatekeeper will warn on first launch.

Download ANKLE.app 1.0.39 Checksum Update manifest
  1. Download the ZIP and verify its SHA-256 if you want byte-level proof.
  2. Unzip it, then drag ANKLE.app into /Applications.
  3. On first launch, right-click ANKLE and choose Open. Confirm the macOS warning only if the filename and checksum match this page.
  4. Install and sign in to the browser extension, then use connect browser extension in the app. The token is transferred through a nonce-bound local bridge and stored in Keychain, not in a URL.
Current limit: Intel Macs are not supported. Because the build has no Apple Developer ID or notarization ticket, double-click alone may be blocked. Right-click → Open is the expected first-launch path.
Updates, failure recovery, rollback, and uninstall
  • The built-in updater requires the exact HTTPS manifest, byte count, SHA-256, safe ZIP paths, bundle ID, arm64 architecture, version, and strict code signature before replacement.
  • If verification or session handoff fails, the current app stays installed and signed in. Failed replacement restores the previous app.
  • A successful update keeps the prior build at /Applications/.ANKLE.previous for rollback.
  • To uninstall, quit ANKLE and move /Applications/ANKLE.app to Trash. Optional local recovery state remains in ~/Library/Application Support/ANKLE; version-scoped sessions remain in Keychain until removed through Keychain Access.
Release note: what 1.0.39 adds

This release opens signed .ankl World capsules offline and independently verifies their manifest, snapshot, media, key fingerprint, and signature before display. The app also keeps Keychain-backed auth, neutral-route continuity, local tools, and rollback-gated app and extension updates.

2. Install the @command browser extension

ANKLE BROWSER EXTENSION 1.6.15 — MANIFEST V3
current releasemanual / developer package

Download version 1.6.15 for Chromium or Brave, unzip it, and use the browser-specific instructions below. Firefox and Safari remain on their separately packaged 1.6.12 builds.

Chrome / Brave ZIP Firefox ZIP Safari source ZIP Release manifest

Chrome / Brave

  1. Unzip the Chromium package.
  2. Open chrome://extensions or brave://extensions.
  3. Turn on Developer mode, choose Load unpacked, and select the unzipped folder containing manifest.json.
  4. Pin ANKLE, open its popup, and pair at aleqth.com/ext-signin.

Firefox / Safari

Firefox 128+: open about:debugging#/runtime/this-firefox, choose Load Temporary Add-on, and select manifest.json. The temporary install disappears when Firefox restarts.

Safari: install Xcode, run the bundled Safari Web Extension packaging command, sign the generated app with your Apple Developer team, run it once, then enable ANKLE in Safari Settings → Extensions. The ZIP itself is not a signed Safari app.

Permissions: what the extension can access

The content script loads on webpages so the overlay can open there. That gives the extension broad technical access to page content. Ordinary page text is not automatically submitted, but user-invoked capture, remix, SURF, clipboard, history, and tab features can inspect or send the material they act on.

  • Required: active tab, extension storage, right-click menus, and downloads.
  • Site access: ANKLE/aleqth hosts for account and API work; a content script on all URLs for the page overlay and user-invoked page actions.
  • Optional, requested from the popup: notifications, all tabs, bookmarks, history, clipboard read, and clipboard write. Leave them off unless you need the named feature.
  • User-submitted image/video saves pass fail-closed media checks before ANKLE keeps them. This does not mean the extension is independently store-reviewed or sandboxed by a browser marketplace.
Update, rollback, and uninstall
  • Unpacked Chrome/Brave installs do not auto-update. Download the next version, load or replace the stable folder, then click Reload on the ANKLE extension card.
  • ANKLE.app can verify and prepare a new folder at ~/Desktop/ANKLE Field Kit/Chrome Extension; it preserves Chrome Extension.previous before replacement.
  • To roll back, load the previous verified folder. To uninstall, choose Remove on the browser extension page and delete the unpacked folder if you no longer need it.
  • If pairing fails, confirm the popup says signed in, reopen ext-signin, then retry the app connection. Tokens are never supposed to appear in the callback URL.

3. Install or embed the @command widget

ANKLE @COMMAND WIDGET KIT 2.1.12 — IMMUTABLE + SRI-PINNED
2 verified assets37,414 bytes

Download widget kit 2.1.12 for its README, manifest, standard widget, terminal build, and example. Or paste one versioned script tag directly into your page. Load only one runtime per page.

Download widget kit Checksum Release manifest Live demo

Standard widget

<script src="https://aleqth.com/atcmd/releases/2.1.12/atcmd-widget.js"
  integrity="sha256-8IAUH+qgck1H0tGU8BkvTNITZR9HmaDjyNbwc9qZqpY="
  crossorigin="anonymous"></script>

Extension-parity terminal

<script src="https://aleqth.com/atcmd/releases/2.1.12/ankle-terminal.js"
  integrity="sha256-lYp7PYT8VsDK0RHZJ/lfKEib733nemWAVFCy1olUBZM="
  crossorigin="anonymous"></script>
  • Use the @ button or Alt+K to open the widget.
  • Versioned URLs are immutable. Floating /atcmd/widget.js routes deliberately trade byte-pinning for automatic minor updates.
  • Third-party embeds stay public-only: they do not receive an end-user bearer token or silently redirect the host page into sign-in.
  • To roll back, pin an earlier immutable release and its matching SRI. To uninstall, remove the script tag and any host-page button you added.

Verify the current files

These values were checked against the live downloads and the saved release shelf. A different byte count or SHA-256 means you do not have this release.

ComponentVersion / requirementsBytesSHA-256
macOS app1.0.39 · arm64 · macOS 12+58,978,3902ab5be924e3d8e6a0f4762d2ee71ffae24f89020c3fbbc9ef9107d89bc9061d9
Chrome / Brave1.6.15 · Manifest V3139,8705d4c0941fe4b88f9f1da54c0e8ad68cdbd81752444a2e7bf48b08101a2aec77c
Firefox1.6.12 · Firefox 128+143,497a105165f39358e868137a0fc99bf2394860b0ad56a3acf6e6e18e0df6e26ae09
Safari source1.6.12 · Xcode/signing required143,897c6bd66d38fa636c905dd332d95150d000b6645ec4e932ea06e6fa02b16f81c83
@command widget2.1.12 · standard + terminal37,969062236fc7c593d8799eec43dee3544f239f58ed48f02d3c55138bd2c7e79a394

Full machine-readable release index

Release notes, privacy, and current limits

KNOWN LIMITS
  • The macOS app is Apple-silicon-only, ad-hoc signed, and not notarized.
  • Chromium/Brave installs are unpacked developer installs with manual reloads.
  • Firefox is temporary without Mozilla signing; Safari is source until you convert and sign it.
  • The extension content script runs broadly so @command can appear on pages. Optional history, tabs, bookmarks, and clipboard access are separate toggles.
  • Third-party widgets are public-only. Account identity stays on exact ANKLE origins.
  • Installation does not enable wallets, tokens, trading, signing, payments, or production access.
SECURITY EXPECTATIONS
  • Use only HTTPS links on this page.
  • Match the exact version, byte count, and SHA-256.
  • Keep optional browser permissions off until needed.
  • Never paste an app token into a URL, issue, or chat.
  • Pin versioned widget assets with the published SRI.
  • Use browser/app removal and preserved previous folders to roll back.

Privacy · Terms · Acceptable use