Skip to content

[Feature]: No Linux support is simply unreasonable. #102

Closed as not planned
Closed as not planned

Description

@enihcam

Problem / 你遇到的问题

No linux.

Proposed solution / 期望方案

Linux.

Platform / 平台

Linux desktop support

Additional context / 补充信息

I've searched existing issues, but the voice needs to be louder.

Before submitting / 提交前确认

  • I have searched existing issues.

Activity

  1. reneleonhardt commented on Jun 30, 2026

    @reneleonhardt

    Linux is very diverse, could you specify which distribution support would be desired?
    Ubuntu or Fedora?
    KDE or Gnome?
    X11 or Wayland?
    Native packages or Flatpak?

  2. SuarezPM commented on Jul 1, 2026

    @SuarezPM

    Linux is very diverse, could you specify which distribution support would be desired? Ubuntu or Fedora? KDE or Gnome? X11 or Wayland? Native packages or Flatpak?

    CachyOS
    KDE plasma 6
    Wayland
    Native packages

  3. enihcam commented on Jul 1, 2026

    @enihcam
    Author

    Linux is very diverse, could you specify which distribution support would be desired? Ubuntu or Fedora? KDE or Gnome? X11 or Wayland? Native packages or Flatpak?

    1. For me, Arch-based first, e.g. CachyOS.
    2. It should be universal, so KDE/Gnome/LXQT/COSMIC/HYPRLAND etc. do not actually matter, but strongly prefer Qt6 or GTK3+ (please DON'T build upon Qt5 or Gtk4).
    3. Don't worry. Let the communities do the packaging for you, and NO Flatpak please.
  4. abderaouflatr commented on Jul 1, 2026

    @abderaouflatr

    @reneleonhardt To answer your question on diversity, here is a concrete data point from a daily driver DevOps/IT Management setup.

    Adding my strong support for this feature. The lack of a native Linux client severely breaks the workflow for developers and IT managers who rely on local homelab integrations, native terminal commands, and seamless file system access. Switching to a dual-boot (Windows) just to use the desktop client defeats the purpose of an integrated AI coding assistant.

    Technical Environment Requirements

    Here are the specific technical requirements for my environment to help guide the packaging:

    • Distribution: Ubuntu 26.04 LTS (Debian-based)
    • Display Server: Wayland
    • Desktop Environment: GNOME (Ubuntu Default)
    • Kernel: 7.0.0-22-generic
    • Hardware: AMD Ryzen 5 5600H with Radeon Graphics (Dell G15)
    • Preferred Packaging: A native .deb package would be ideal for deeper system integration, but a universally containerized format like an AppImage or Flatpak would be perfectly fine as a starting point to cover the widest range of distributions.

    Agentic Workflows & Token Efficiency

    Beyond convenience, running the M3 agent on Linux provides massive API token efficiency gains over Windows.

    • The Windows Overhead: When the agent uses tools to execute local terminal commands, search directories, or edit files, Windows PowerShell requires verbose syntax, complex pathing, and outputs massive tables with whitespace padding that heavily inflates the context window.
    • The Linux Advantage: In contrast, native Linux Bash commands and standard stdout are dense and clean. Running agentic workflows natively on Ubuntu prevents token bloat and significantly reduces API usage during multi-step tool calls.

    Linux is the native home for most backend, cloud networking, and DevOps work. Releasing a Linux build (even just targeting Ubuntu/Wayland initially) would instantly unlock a massive demographic of power users. Happy to help test any early Alpha/Beta Linux builds!

  5. added
    desktopMiniMax Code desktop app
    needs-triageAwaiting maintainer assessment
    and removed
    desktopMiniMax Code desktop app
    on Sep 19, 2026
  6. hetaoBackend commented on Sep 21, 2026

    @hetaoBackend
    Collaborator

    This was generated by AI during triage.

    Linux desktop is genuinely our most-requested item — consolidating the Linux asks here (#51, #107, #122 point this way).

    Current state:

    • Standalone CLI works on Linux today: npm i -g @minimax-ai/code, then mcode in any terminal — full agent capability, BYOK included.
    • Desktop (Electron) Linux build: under evaluation; the main cost is not the Electron shell but the platform-integration surface (IM bridges, updater, native deps). No committed date yet — updates will land on this issue.
  7. hradec commented on Sep 25, 2026

    @hradec

    Making the desktop app with electron is the best solution, since it doesn't matter what linux distro/version it runs on... what matters is the glibc version of the distro, and as a rule of thumb, you want to use the oldest possible glibc supported by chromium/electron so the app stays compatible with all possible distros/versions that electron runs on.

    If you build for glibc 2.31, the desktop app will run on distros as old as debian 11.

    Just be carefull: electronuserland/builder — electron-builder's own Docker image — is now based on buildpack-deps:22.04, i.e. glibc 2.35. If you use it, you silently raise your floor to Debian 12 / Ubuntu 22.04 and lose Debian 11 and Ubuntu 20.04. Pin your own base image if you need the wider range:

    FROM ubuntu:20.04
    # node 20/22 from nodesource, build-essential, python3, git, plus
    # libgtk-3-dev libnss3-dev libgbm-dev libasound2-dev libxkbcommon-dev ... for any native deps
    

    Locking the build image on ubuntu:20.04 guarantees the .appimage will run on every possible linux distro with versions that came at the same time and after debian 11. (start of 2021)

    Also, make sure to set the toolsets: { appimage: "1.0.3" } in the electron-builder.yml, so the appimage will work on distros with libfuse2 (older distros) and libfuse3(newer distros)!

    my 2 cents.

  8. hetaoBackend commented on Oct 19, 2026

    @hetaoBackend
    Collaborator

    Closing as part of a backlog cleanup: this issue was filed more than a month ago against an older release, and the codebase has changed substantially since then. If it still reproduces on the latest version, please open a new issue with the current version and reproduction steps. Thank you for the report!

    批量清理积压:该 issue 创建已超过一个月,针对的是较旧版本,代码已有较大变化。如果在最新版本上仍能复现,欢迎附上当前版本号和复现步骤重新提交 issue。感谢反馈!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    desktopMiniMax Code desktop appenhancementNew feature or requestneeds-triageAwaiting maintainer assessment

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions