New version: Anomaly.OpenCode version 2.0.29 - #452561

Hello Filip Hejmowski (@neriousy),

This PR cannot be merged until you sign the Contributor License Agreement (CLA). More information on this process can be found on the Microsoft Open Source website.

Template: msftbot/needsCLA

@microsoft-github-policy-service agree company="Anomaly"

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

Filip Hejmowski (@neriousy)

OpenCode processes personal and potentially sensitive information, including provider credentials, prompts and source-code context sent to configured model providers, account and payment information for hosted services, and conversation data uploaded through the optional sharing feature.

A product-applicable privacy policy is available, so Windows Package Manager repository policy 1.5.1 requires the manifest to include it:

https://learn.microsoft.com/windows/package-manager/package/windows-package-manager-policies#151

Please add the following to the default locale manifest:

PrivacyUrl: https://opencode.ai/legal/privacy-policy

Please also clarify the catalog migration plan from the existing SST.opencode identifier. Both identifiers represent the same upstream repository and install the opencode command, while SST.opencode remains in the repository with active 1.x update submissions. If Anomaly.OpenCode replaces that package, the old identifier needs a coordinated retirement/removal plan so users do not receive duplicate catalog entries or lose the intended upgrade path.

Related open PRs with the same requested correction:

• New version: Anomaly.OpenCode version 2.0.28 #451573

Drafted with GitHub Copilot assistance.

Template: moderator/triage/authorNudge

Thanks Demitrius Nelon (@denelon)!

PrivacyUrl: Added PrivacyUrl: https://opencode.ai/legal/privacy-policy to all four open submissions:

• New version: Anomaly.OpenCode version 2.0.28 #451573 / New version: Anomaly.OpenCode version 2.0.29 #452561 (Anomaly.OpenCode)
• New version: Anomaly.OpenCode.Desktop version 2.0.28 #451574 / New version: Anomaly.OpenCode.Desktop version 2.0.29 #452562 (Anomaly.OpenCode.Desktop)

Migration from SST.*: Some background: the existing SST.opencode and SST.OpenCodeDesktop packages were set up and maintained by community members. They aren't affiliated with us, and we've never published to those identifiers. OpenCode is now developed by Anomaly (https://anoma.ly, repo: https://github.com/anomalyco/opencode). These Anomaly.OpenCode* submissions are the first official manifests, and they're published automatically by our release workflow.

Going forward, we'd like these to be the only official identifiers:

• Anomaly.OpenCode replaces SST.opencode
• Anomaly.OpenCode.Desktop replaces SST.OpenCodeDesktop

Our proposed plan:

1. Merge the Anomaly.OpenCode* packages as the official ones.
2. After that, retire SST.opencode and SST.OpenCodeDesktop. We can open the removal PRs ourselves, or follow whatever process you prefer
3. Update our install docs to point to the new identifiers, with a note for existing users to run winget uninstall SST.opencode / SST.OpenCodeDesktop before installing the new packages.

If there's a better way to keep the upgrade path working for existing SST.* users, we're happy to do that. Just let us know what you'd recommend.

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

This PR being merged would be very much appreciated as version 2.0 of Opencode has brought several fixes that are crucial for the user. Just thought to drop this comment here. I'm not part of the devs team. I'm just a simple user that wants this released soon. Thank you for your great work.

Demitrius Nelon (@denelon) friendly nudge: the PrivacyUrl and SST.opencode migration points were addressed above, is anything else blocking this from being merged?

Validation has completed.

Template: msftbot/validationCompleted

2. After that, retire SST.opencode and SST.OpenCodeDesktop. We can open the removal PRs ourselves, or follow whatever process you prefer

Should I remove the SST.opencode package, or move the existing manifests of SST.opencode to the Anomaly.OpenCode package? I'll remove my automation on the old package anyway.

EDIT: In any way the users using the SST.opencode package wouldn't be automatically updated to Anomaly.OpenCode AFAIK.

EDIT2: OK I saw #472459

Does this mean we should soon see Opencode v2 in Winget?

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

I see the application in Winget now. Thank you.

Not to be a negative Nelly, but now it needs to be brought up to the latest version.

Yup - we disabled our PRs while waiting on approval.
a new v2 release coming out shortly and i'll resume the winget Prs shortly

Excellent news. Thank you

Seems the CLI is still stuck at 2.0.29 and the desktop app didn't get bumped to 2.3.0 either.