The shell the family runs inside.
PrimeForge Desktop is the local application every other PrimeForge product runs in: the installer, the updates, the local data store, and the one gateway allowed to reach outside your machine.
It is the ground floor of the four-layer stack — the runtime everything else is written against. Installing it is how a PrimeForge product arrives on a machine, and keeping it installed is how that product keeps its data local.
PRE-RELEASEWindows is in development — see what each platform needs below.
A local runtime, with an application around it.
Most of what Desktop does is invisible on purpose. It is the part of the architecture a person actually installs.
Every PrimeForge product needs the same handful of things: somewhere to keep its data, a way to run multi-step work in the background, a route to a model when one is genuinely needed, and a way to update itself. Building those five times over would produce five different answers, five update mechanisms and five places for data to leak out of.
Desktop is that shared answer. It holds the installer and the updater, the local data store, the agent and task orchestration that runs work as local jobs, and the LocalAgentGateway — the single controlled point where anything is allowed to leave the machine, carrying only the context a specific task needs.
That last part is the reason the rest is shaped the way it is. If a product can only reach the network through one component, then permissions, quotas, logging and provider failover all have exactly one place to live, and swapping a model becomes configuration rather than a rewrite.
Five things it is for.
- 01
One shell, every product
Install once. Every PrimeForge product runs inside it, sharing the same updates, the same settings and the same local store — rather than being several separate installs with several separate update mechanisms to forget about.
- 02
Your data stays on your disk
The local store is a file on your machine. Records, conversations and analysis live there, backed up like anything else you own. Nothing has to be uploaded for the application to work.
- 03
One controlled exit point
The LocalAgentGateway is the only component allowed to reach the network — routing, quotas, session reuse, logging and fallback in a single place you can inspect. Workflows are written against it, not against a vendor SDK.
- 04
Runs on the plan you already pay for
Point the gateway at your own Claude or ChatGPT and Codex subscription, at a local model, or at a direct API key as a fallback. We do not resell metered tokens, so there is no second meter running behind your work.
- 05
Install and run
No implementation phase, no configuration consultancy, and no requirement to understand the architecture underneath. Updates arrive in the shell rather than as a project.
What each platform needs.
Whatever the download button decided you were running, this table is the whole truth.
| Platform | Minimum OS | Architecture | Status |
|---|---|---|---|
| macOS | macOS 14 Sonoma or later | Apple silicon and Intel | Pre-release — not published yet |
| Windows | Windows 11 | — | In development |
The products are what you came for.
Desktop is how they reach your machine and stay on it. What runs inside is the part worth choosing.