Updates move in deliberate public steps.

Windows, macOS, and Linux downloads are live through stable redirect endpoints.

The current public release keeps distribution straightforward: browser-first downloads, platform notes kept visible, and the release path centered on clarity rather than overpromising background update magic.

Live now · Current release path · Public release

• Stable redirect endpoints back the Windows, macOS, and Linux download buttons.
• Unsigned install guidance stays explicit for both platforms.
• The base app remains lean while optional AI tooling stays separate.

Release metadata points the app toward newer builds without pretending to be a fully silent updater.

Update discovery is already part of the product story, but the site should frame it as metadata awareness and guided upgrade flow, not as a completely signed and invisible patch pipeline.

In production · Current release behavior · Metadata-driven

• Release metadata is checked from openstudio.org.in.
• The messaging stays conservative around background patching.
• The install trust story remains visible during the first public cycle.

Distribution polish, stronger packaging, and a cleaner release narrative come next.

The next visible improvements are about making the release experience sturdier: clearer packaging, refined trust messaging, and a stronger changelog rhythm around public builds.

Planned · Next public iteration · Next release focus

• Tighter version storytelling across downloads and release notes.
• Better packaging and trust cues around installers.
• A cleaner release history surface for public-facing changes.

Windows stable redirect

The public Windows button points to a stable redirect endpoint rather than a hardcoded binary URL in the UI.

macOS stable redirect

The macOS path uses the same stable redirect approach, with manual trust notes kept visible.

Honest AI tooling story

Optional AI runtimes stay separate from the default installer so the base product story stays truthful.