CommandCodeAI / CommandCodeAI/desktop

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

Ouverte
#30 5 commentaires 3 réactions 1 personne assignée Voir sur GitHub

@aliarain y travaille déjà.

Depuis le 13/8/2026.

enhancement
Langage dominant
Shell
Étoiles
80
Forks
2
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.