CommandCodeAI / CommandCodeAI/desktop

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

Open
#30 5 comments 3 reactions 1 assignee View on GitHub

@aliarain is already working on this.

Since Aug 13, 2026.

enhancement
Dominant language
Shell
Stars
80
Forks
2
PR merge metrics
No merged PRs in 30d

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

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.