- Your data stays on your device
- The interface and the API both run on a loopback address. Configuration, backups and state are written on your machine.
- The local service is not a control plane for anything outside it.
-
- A key only goes where it has to
- An API key is written to the one file the target agent needs to work: its own configuration, or OneAgent's environment file.
- Keys never appear in the OneAgent profile, logs, screenshots, web analytics events, or command-line arguments.
- Where it lands depends on the agent and the operating system. These are the common ones:
-
- ~/.codex/config.toml
- ~/.claude/settings.json
- ~/.config/opencode/opencode.jsonc
- ~/.config/kilo/kilo.jsonc
- ~/.oneagent/
-
- The launcher lists the real paths before and after every write.
-
- A backup comes before any change
- Before modifying existing configuration, OneAgent writes a timestamped backup.
- Configuration directories and files holding a key are readable only by the current user. The cleanroom check confirms the real user directory was untouched by the test run.
-
- Every channel ships the same package
- This site, GitHub Releases, a file host and an internal drive all distribute the identical official build. For a given version, the contents and the SHA-256 match.
- Channels do not repackage, append promotional content, or re-sign.
- Third-party agent binaries are not redistributed by OneAgent. They come from the official installer, a mirror with written permission, or your own manual install.
-
- Current release evidence
- {publishedTarget && publishedArtifact ? (
- <>
- These values come from the published release metadata on GitHub Releases, so you can check each one against the release page itself.
-
- - Channel:
technical-preview-unsigned
- - Version:
{preview?.version}
- - Platform: {publishedTarget.platformLabel} {publishedTarget.archLabel}
- - SHA-256:
{publishedArtifact.sha256}
- - Signing and notarisation: not yet complete, so this is not stable.
-
- Whether the build was native, and whether a cleanroom run passed, is recorded by the release process — this page does not assert it on the release process's behalf.
- >
- ) : (
- No artifact has been published on this channel yet, so there is no digest here to check.
- )}
-
-
-
The stable gate
-
Each platform reaches stable on its own once it qualifies, without waiting for the others.
-
- - macOS: Developer ID signature, notarisation, stapled ticket
- - Windows: a valid Authenticode signature
- - Every platform: a native build and cleanroom evidence
-
-
-
Explicitly out of scope
-
These are not part of the product, and will not be added as features:
-
- - VPNs, proxy nodes, or instructions for getting around network restrictions
- - Shared API keys, a unified model gateway, reselling models or API access
- - Unauthorised agent binaries and channel-customised packages
- - Describing an unsigned preview as stable or as security-certified
-
-
-