Desktop release
Download Nucleus
The unified console build is prepared locally, but a public production download must be signed and independently verified before it is distributed.
The download will not silently fall back to an unsigned or unverified executable. Required evidence: clean dependency install, build and tests, software bill of materials, security scan, Windows code signing, artifact digest, and distribution receipt.
What is included
- Governed mission command center and receipts.
- Protected direct browser and local code builder with versions.
- Active model usage and provider-cost view.
- Plugin, API, MCP, hosting, exchange, and shadow-economy workspaces.
Availability
The public download control will activate after release evidence and a signed artifact exist. Until then, the console is available only as a verified local build in the owner environment.
Open the local Builder safely
- 1 · Launch the desktop shellOwner authority is issued only to the local Nucleus window created for that launch.
- 2 · Select BuilderCreate a local draft version, inspect its metadata, and run only the checks you explicitly request.
- 3 · Draft a deploy missionPreview and production deployment remain separate approval-gated steps.
If the local bridge is already running, these views can display the console without receiving owner authority. Use the desktop shell for any approved local mutation.
The nucleus-action-os plugin product must pass package validation and owner approval before installation or marketplace publication. This page does not install it.