CommandCodeAI / CommandCodeAI/desktop

[Feedback]: Migrate desktop app from Electron to Tauri/Wails for better performance and resource usage

Aperta
#30 5 commenti 3 reazioni 1 assegnatario Vedi su GitHub

@aliarain ci sta già lavorando.

Dal 13/8/2026.

enhancement
Lingua principale
Shell
Stelle
80
Fork
2
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

What problem are you trying to solve?

The current Electron-based desktop app consumes a significant amount of system memory (RAM) and results in large installer/executable sizes due to shipping a full Chromium browser and Node.js instance.

Additionally, Electron applications often experience graphical glitches and compatibility issues on Linux-based systems, especially when using tiling window managers (e.g., Hyprland, i3, Sway).

What would improve it?

onsider rewriting or migrating the desktop application to Tauri (Rust) or Wails (Go).

Benefits of this change:

  1. Significantly lower memory usage: Uses the native system web engine instead of bundling Chromium.
  2. Smaller app size: Executables are much smaller (often just a few megabytes).
  3. Better performance: Heavy tasks run on Rust or Go instead of Node.js (which is more optimised for desktop gui usage making it faster).
  4. Improved Linux compatibility: Better integration with Linux desktop environments and tiling window managers, reducing graphical glitches.

While migrating web frameworks involves effort, the long-term gains in performance, security, and user experience would be substantial.

I think it'll be a nice switch up and I to be honest y'all could be one of the first desktop harness built on Rust, making it different from the competence, while making it better usage for user experience.

What do you do today?

No response

Product area

None

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.