CommandCodeAI / CommandCodeAI/desktop

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

Abierto
#30 5 comentarios 3 reacciones 1 asignado Ver en GitHub

@aliarain ya está trabajando en esto.

Desde el 13/8/2026.

enhancement
Lenguaje dominante
Shell
Estrellas
80
Forks
2
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.