Docs · Docs for 1.0.12
Documentation

Run it, and check it.

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.

Where the work runs

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.

Your tools Claude Code Codex Copilot you keep them a question not your files Your machine the model runs here works with the wifi off hardware you already own we ran the small model on an 8 GB 2020 Air signed · notarised · checkable hands over the work Your other machine runs it when asked over your own link run between two machines Someone else's machine joins with a workspace key answers, never your files anything reaching outside is checked as it runs, not filed away for later In a browser from your own machine today not yet from anywhere else Armore cloud your own provider works today ours is not open yet solid: works today dashed: partly open — each box says what works
Your tools stay where they are. What moves is where the work runs.

In the app

The desktop application. Ten surfaces in two areas, plus five destinations in the left rail.

✓
The in-app walkthrough is written, and it lives on the pages below, not on separate pages. Each page carries a surface toggle at the top: the steps and their order are the same either way, and switching changes only how each one is done. Your choice is remembered as you move through the guide. 21 captures of the shipped v1.0.10 build are in place, and every control name was read out of that bundle rather than recalled.

The eleven guides, and where the in-app walkthrough lives

#PageThe in-app walkthrough
01Install and first run get-started · 5 figures
02Ask about your own files ask-your-files · 2 figures
03Point your AI tools at Armore point-your-tools: pane exists, capture pending (A13, #6459)
04Open the browser view browser-view: ending a session only
05Add a second device add-a-device · 5 figures
06Let another machine do the work share-the-work · 1 figure
07Install a connector connectors · 4 figures
08Verify 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
09The command-line tool No in-app pane, by construction: it is the other surface
10All the commands No in-app pane: a reference for the other surface
11See 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.

Assistant

AskResearchExtractVision DocsYour files

Build & Act

CodeActionsWorkflowsBuild

The left rail

This deviceIntelligenceCollaborationActivitySettings

Things you can do without the command line

The guides

Twelve 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.

01

Install and first run

Download, verify the signature, install, and get through the first launch, including the model download and what it actually costs you.

02

Ask about your own files

Retrieve, then ask grounded on what came back, and the receipt that says where it ran.

03

Point your AI tools at Armore

Keep Claude Code, Codex or Copilot and point them at the model on your own machine.

04

Open the browser view

The same application in a browser tab, served by your own machine on loopback. Off by default.

05

Add a second device

Pairing, the SAS code that makes it safe, and what a relay can and cannot see.

06

Let another machine do the work

A laptop with no model of its own can ask a paired machine that has one.

07

Install a connector

The MCP client compiled into the CLI, its signed catalog, and the sandbox a connector runs in.

08

Verify what you downloaded

Check any artifact against its Sigstore bundle without trusting us, and the two commands that do not work.

09

The command-line tool

All twenty commands, the JSON contract, and what each one refuses to do.

10

All the commands

Every command the binary exposes, read off the shipped binary rather than recalled.

11

See and erase what is stored

armore privacy: list, export, or delete. Its roots are disjoint from the app's.

12

Connect a cloud provider beta

Cloud opens when a key or a Pro entitlement is present, and says who can supply one when neither is. What an administrator connects, what the cloud path means for your text, what each refusal means, and why there is no number on the screen.