Platform and Build Status

The public 1.0 platform matrix is frozen, but no target has been promoted to formal support. Packaging configuration, component resources, and source-level build entry points do not replace release acceptance for the final installer bytes.

A “GA target” becomes supported and downloadable only after the same final-RC bytes pass signing, notarization, installation, upgrade, data-migration, and core-workflow gates. Ubuntu uses a separate Preview entry point and stream; it is not part of macOS stable support. Other repository build entry points are engineering capabilities, not public compatibility commitments.

Platform-specific differences

• The native terminal and local MCP Servers launch platform processes; behavior depends on the operating system and local permissions.
• Legacy .doc reading is currently available only on macOS through system conversion capabilities; .ppt and .xls are not supported.
• Image-generation credentials use Mac Keychain in signed macOS builds. Development builds and other platforms use different credential backends.
• Complete process-tree isolation for external stdio MCP Servers on Windows cannot yet be presented as a verified guarantee.
• Scheduled Automation runs only while the application and Core Server are running; it is not an operating-system background service.
• Whether native notifications appear depends on platform support and the user's system-notification settings.

Checks before installation

1. Check Downloads & Platforms on the website. While its buttons are disabled, there is no website-approved public installer.
2. After release, match the publisher, filename, architecture, and SHA-256 against the Release Manifest.
3. Read Known Issues, especially the limitations related to models, MCP, the browser, Office, and Automation.
4. Do not copy installation directories, component caches, or internal application files from another platform as an installation method.