Bring the desktop app into the fork (Tauri + Electron, fully branded)

Open
#960 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
electron, github-actions, tauri, typescript
Domain
ci-cd, desktop, release

Research direction

Start by comparing upstream v1.2.20 packages/desktop, packages/desktop-electron, packages/app, and packages/ui with this fork. The issue also names the opencode/altimate CLI sidecar, altimate-backend provider, branding surfaces, updater configuration, and CI publish workflow. Done means the fork has branded Tauri/Electron desktop apps with no OpenCode leaks and a publish-ready signed auto-update pipeline.

Written by the indexing model from the issue text.

Description

The fork was created from OpenCode without the desktop app. We want a fully-functional, fully-branded Altimate Code desktop app that exposes everything the fork has built, with no OpenCode branding leaks, and a publish-ready CI pipeline.

Scope
  • Adopt the Tauri desktop shell (packages/desktop, primary) + Electron shell (packages/desktop-electron, secondary) and the SolidJS web UI (packages/app, packages/ui) from upstream v1.2.20.
  • Bundle our opencode/altimate CLI as the Tauri sidecar so all server-side fork capabilities (SQL, dbt, FinOps, warehouse, altimate-core, the Altimate gateway) are exposed automatically.
  • Rebrand every user-facing surface to Altimate Code (names, icons, colors, deep-link scheme, updater endpoints + key) — zero OpenCode leaks.
  • Feature the Altimate LLM Gateway (altimate-backend) provider and remove the OpenCode Zen onboarding.
  • Keep future upstream merges branded (un-skip packages, branding rules, altimate_change markers).
  • Add a CI publish workflow (signed, auto-updating) — ready for org secrets.
Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.