Release history and availability

Website updates — 2 November 2026Copy Anchor Link

• Company pricing now explains the per-company subscription, named users and shared allowance, with a calculator and a comparison.
• Public product and onboarding guides connect the engineering workflow to review, Apply and independent validation.
• Shared navigation, provider identity marks and responsive documentation layouts have been repaired.
• Public Markdown, llms.txt, llms-full.txt and a generated sitemap make published information accessible without running the website interface.

These are website changes, not a claim that every desktop platform or commercial service is released.

Desktop release recordsCopy Anchor Link

The Client availability page reads the release registry for each platform and architecture. A downloadable record must identify its edition, source revision, installer hash and qualified artifact. A Git commit, screenshot or passing source test is not a qualified installer.

If no public artifact is listed, do not substitute a private Owner build or an older installer from another source. Private Owner Codex accounts must not be included in a customer installation.

Before updatingCopy Anchor Link

1. Preserve your projects and any unsaved work.
2. Check platform, architecture and Client edition.
3. Compare the published source revision and SHA-256 with the downloaded artifact.
4. Keep the previous known-good installation until the replacement launches and your project opens correctly.
5. Follow the update and uninstall guide rather than deleting your profile to solve an installation problem.

Service availability is separateCopy Anchor Link

Website sign-in, public engineering AI, purchases, support and downloads have different dependencies and qualification. The availability page reports current public gates. No historical uptime percentage, incident-free claim, release date or response-time guarantee is inferred from that snapshot.