Armore Edge is a desktop app, a browser view served by your own machine, and a command-line tool. These pages cover all three — and every command on them was run against a shipped build before it was written down.
Your tools stay where they are. Your machine does the work, another machine you own can take it on, and a person you work with can join the same workspace.
The desktop application. Ten surfaces in two areas, plus five destinations in the left rail.
| # | Page | The in-app walkthrough |
|---|---|---|
| 01 | Install and first run | get-started · 5 figures |
| 02 | Ask about your own files | ask-your-files · 2 figures |
| 03 | Point your AI tools at Armore | point-your-tools — pane exists, capture pending (A13, #6459) |
| 04 | Open the browser view | browser-view — ending a session only |
| 05 | Add a second device | add-a-device · 5 figures |
| 06 | Let another machine do the work | share-the-work · 1 figure |
| 07 | Install a connector | connectors · 4 figures |
| 08 | Verify what you downloaded | No in-app pane, by construction — you verify the installer before you trust the app, so the check cannot live inside it |
| 09 | The command-line tool | No in-app pane, by construction — it is the other surface |
| 10 | All the commands | No in-app pane — a reference for the other surface |
| 11 | See and erase what is stored | privacy · 5 figures |
03 is honestly partial. Starting the browser view is running a server from a shell — the URL, the port, the token — and there is no app version of that because there is no app version of running a server. Ending a session is the one part the app does, and that is the only part its toggle offers.
The numbers match the command-line track below, and 06 and 07 are missing
from this list deliberately — signature verification is something you do
to the installer before you trust it, so it is not a screen
inside the app, and the command-line tool is the other track. There is no
Verify signature control and no verify-blob anywhere in
the shipped bundle; we checked rather than assumed.
Invite a device or
Join a workspace, on the Collaboration surface.Export all to a folder…Delete all data…. ⚠️ Scoped to the app: data kept by the
command-line tool lives under a different root and is not touched.Revoke all web sessions, on
the Collaboration surface.
Eight pages, and each one covers both surfaces — the app and the command line.
Use the toggle at the top of a page to switch; the steps and their order are the same
either way. The command-line tool has twenty commands with --json on
every one, built to be driven by agents. Every command on these pages was run
against a shipped build before it was written down.
Download, verify the signature, install, and get through the first launch — including the model download and what it actually costs you.
Retrieve, then ask grounded on what came back — and the receipt that says where it ran.
Keep Claude Code, Codex or Copilot and point them at the model on your own machine.
The same application in a browser tab, served by your own machine on loopback. Off by default.
Pairing, the SAS code that makes it safe, and what a relay can and cannot see.
A laptop with no model of its own can ask a paired machine that has one.
The MCP client compiled into the CLI, its signed catalog, and the sandbox a connector runs in.
Check any artifact against its Sigstore bundle without trusting us — and the two commands that do not work.
All twenty commands, the JSON contract, and what each one refuses to do.
Every command the binary exposes, read off the shipped binary rather than recalled.
armore privacy — list, export, or delete. Its roots are disjoint
from the app's.