You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(desktop): give Linux packages a distinct CookieMonster identity #76
The branded CookieMonster Debian package still installs OpenCode's desktop entry, icons and metadata under ai.opencode.desktop. The branded override changes appId after the Linux configuration has already been built from the upstream ID.
The generated package is named cookiemonster but includes usr/share/applications/ai.opencode.desktop.desktop, usr/share/metainfo/ai.opencode.desktop.metainfo.xml, upstream-named icons and the legacy opencode-desktop.desktop entry. It declares no Conflicts/Replaces relationship. Installing alongside an upstream OpenCode package owning those paths can fail, and the launcher identities collide.
Priority: high. Source is identical in the reviewed CM-Split-v2 commit dafdcd4171466050c984d524ca0d1a09d31f100e and remote V2 configuration. The branded override leaves the previously derived Linux fields intact.
Plugins
WPP provider enabled; the defect is in desktop packaging and also affects generic branded builds.
OpenCode version
CookieMonster 2.0.29-cm.2 (Debian version 2.0.29~cm.2).
Steps to reproduce
Build a branded Linux amd64 Debian package with CM_BRAND=1.
Run dpkg-deb --contents <artifact.deb> and inspect launcher, icon and metainfo paths.
Run dpkg-deb --field <artifact.deb> Package Conflicts Replaces.
The paths and missing relationships above were verified in the generated archive. Actual installation alongside upstream OpenCode has not been attempted.
Expected: CookieMonster's Linux launcher identity is distinct, with an explicit migration path where needed.
Acceptance criteria and verification
Branded Linux executable, desktop entry, icon name, window-class identity and metainfo consistently use CookieMonster's identity.
An archive-content regression check catches upstream identity leaking into a branded package.
Verify installation/removal alongside upstream OpenCode in a disposable environment; neither package overwrites or removes the other's launcher or icons.
Preserve existing CookieMonster profile data and document any launcher migration.
Merged into CM-Split-v2 as 290d7d6353c0c7a4a356af780b5687f2dcfe5cfc through PR #96. Its tree exactly matches reviewed source 68ab9205709350385471eb2d383b3cff3c18e678.
Implemented in PR #96, reviewed source 68ab9205709350385471eb2d383b3cff3c18e678.
CookieMonster Linux executable, launcher, icons, WM_CLASS and metainfo now share a distinct branded identity. The archive-content regression passed. Disposable installation/removal beside official OpenCode 1.19.3 preserved upstream files and the CM profile; the packaged visible renderer used the expected WM_CLASS.
Final verification is deferred at the user's explicit request to finish and close the implementation issues before one final test pass. This closure records implementation completion, not a claim that the final combined/platform checks have passed. Any failure in that pass will be recorded against the relevant issue.
Activity
trmosala commentedon Oct 21, 2026
Merged into
CM-Split-v2as290d7d6353c0c7a4a356af780b5687f2dcfe5cfcthrough PR #96. Its tree exactly matches reviewed source68ab9205709350385471eb2d383b3cff3c18e678.Implemented in PR #96, reviewed source
68ab9205709350385471eb2d383b3cff3c18e678.CookieMonster Linux executable, launcher, icons, WM_CLASS and metainfo now share a distinct branded identity. The archive-content regression passed. Disposable installation/removal beside official OpenCode 1.19.3 preserved upstream files and the CM profile; the packaged visible renderer used the expected WM_CLASS.
Final verification is deferred at the user's explicit request to finish and close the implementation issues before one final test pass. This closure records implementation completion, not a claim that the final combined/platform checks have passed. Any failure in that pass will be recorded against the relevant issue.