anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #5044] OpenCode Desktop app #11219

New Issue
Closed
opened 2026-02-16 18:16:01 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:16:01 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/5044

State: closed
Merged: Yes

Adds @opencode-ai/desktop to @opencode-ai/tauri, with CI setup for building and uploading assets as debug artifacts and as release assets. The Tauri app embeds the opencode binary as a sidecar, and runs it as a child process.
A summary of changes in no particular order:

  • @opencode-ai/desktop is now consumable as a library, exporting both runtime code and config
    • I've given the package it's own /vite export so that any plugins and config can be shared between its consumers' Vite configs
  • Running bun tauri dev in packages/tauri will now performing the following preparation steps:
    • An opencode binary for the specified target will be searched for in packages/opencode/dist/{target}/bin
    • If no binary is found, bun run build --single will be used to build the binary for the current target (this doesn't yet support building a specific target)
    • The binary will be copied into packages/tauri/src-tauri/binaries
  • CI now builds Desktop for x86_64-apple-darwin, aarch64-apple-darwin, x86_64-pc-windows-msvc, and x86_64-unknown-linux-gnu
    • This happens after the CLI release completes
    • packages/tauri/scripts/prepare.ts is used to download the opencode binary for the specified target
    • The updater currently uses OS dialogs for checking for updates on startup, see here for how to have more control over it
    • The updater currently sources updates from GitHub releases, this can be changed to be your own domain or update server
    • The version number from the app is being pulled from packages/tauri/package.json

Pending tasks and questions:

  • tauri-action will require a releaseId to upload assets to, right now I have it set to create a draft release
  • Should the CI flow be redesigned so that release doesn't complete until the desktop app is ready?
  • Generate a public/provide key for the updater
  • macOS Codesigning: Requires APPLE_CERTIFICATE and APPLE_CERTIFICATE_PASSWORD
  • macOS Notarization: Requires APPLE_API_ISSUER, APPLE_API_KEY, and the contents of the corresponding private key
**Original Pull Request:** https://github.com/anomalyco/opencode/pull/5044 **State:** closed **Merged:** Yes --- Adds `@opencode-ai/desktop` to `@opencode-ai/tauri`, with CI setup for building and uploading assets as debug artifacts and as release assets. The Tauri app embeds the `opencode` binary as a [sidecar](https://tauri.app/develop/sidecar), and runs it as a child process. A summary of changes in no particular order: - `@opencode-ai/desktop` is now consumable as a library, exporting both runtime code and config - I've given the package it's own `/vite` export so that any plugins and config can be shared between its consumers' Vite configs - Running `bun tauri dev` in `packages/tauri` will now performing the following preparation steps: - An `opencode` binary for the specified target will be searched for in `packages/opencode/dist/{target}/bin` - If no binary is found, `bun run build --single` will be used to build the binary for the current target (this doesn't yet support building a specific target) - The binary will be copied into `packages/tauri/src-tauri/binaries` - CI now builds Desktop for `x86_64-apple-darwin`, `aarch64-apple-darwin`, `x86_64-pc-windows-msvc`, and `x86_64-unknown-linux-gnu` - This happens after the CLI release completes - `packages/tauri/scripts/prepare.ts` is used to download the `opencode` binary for the specified target - The updater currently uses OS dialogs for checking for updates on startup, [see here](https://tauri.app/plugin/updater/#checking-for-updates) for how to have more control over it - The updater currently sources updates from GitHub releases, this can be changed to be your own domain or update server - The version number from the app is being pulled from `packages/tauri/package.json` Pending tasks and questions: - [ ] `tauri-action` will require a `releaseId` to upload assets to, right now I have it set to create a draft release - [ ] Should the CI flow be redesigned so that release doesn't complete until the desktop app is ready? - [x] Generate a public/provide key [for the updater](https://tauri.app/plugin/updater/#signing-updates) - [x] [macOS Codesigning](https://tauri.app/distribute/sign/macos/#signing): Requires `APPLE_CERTIFICATE` and `APPLE_CERTIFICATE_PASSWORD` - [x] [macOS Notarization](https://tauri.app/distribute/sign/macos/#notarization): Requires `APPLE_API_ISSUER`, `APPLE_API_KEY`, and the contents of the corresponding private key
yindo added the pull-request label 2026-02-16 18:16:01 -05:00
yindo closed this issue 2026-02-16 18:16:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#11219
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?