Steam Linux Startup Notes

If you start HagiCode Desktop from Steam for Linux, the default launch path currently prioritizes startup compatibility over preserving Electron’s default sandbox protection.

This is not presented as the ideal long-term technical fix. It is the current compatibility fallback for the unresolved conflict between the Steam sandbox and the Electron sandbox during startup.

Start with the short version

Think of the current behavior as two startup choices:

1. Default Steam launch: compatibility first, launches with --disable-setuid-sandbox -no-sandbox, and avoids the known startup conflict more reliably, but does not keep Electron’s default sandbox.
2. Manual direct launch of hagicode-desktop: requires you to enter the actual install directory and start the desktop binary yourself, which avoids the Steam launcher flags and preserves Electron’s default sandbox.

The default Steam path is not risk-free

--disable-setuid-sandbox -no-sandbox is the current compatibility path, but it also removes one of Electron’s default runtime protection layers.

Why the default Steam launch disables Electron sandboxing

On Linux, Steam introduces its own sandbox layer around the application environment. When HagiCode Desktop starts as an Electron application inside that environment, keeping Electron sandboxing enabled in the default way can currently lead to a sandbox conflict and startup crashes.

That is why the current default Steam launch path appends --disable-setuid-sandbox -no-sandbox. The goal is straightforward:

• keep the app launchable inside Steam
• avoid the immediate startup crash path
• use a compatibility default while a cleaner technical resolution is still unavailable

Current status

The team does not yet have a clearer technical fix that keeps Electron’s default sandbox enabled inside the Steam sandbox environment while still avoiding the current startup failures.

Startup choice A: use the default Steam launch

If your priority is “open the app from Steam and get in reliably,” stay with the default Steam startup path.

Its characteristics are:

• it matches the current packaged default behavior
• it does not require you to inspect the install directory
• it automatically uses the compatibility flags --disable-setuid-sandbox -no-sandbox
• the trade-off is that Electron’s default sandbox is not preserved

This path fits users who:

• want the standard Steam launch experience
• value startup reliability first
• do not want to manage a manual launch command

Startup choice B: launch hagicode-desktop directly

If your priority is preserving Electron’s default sandbox behavior, do not use the default Steam launcher path for that startup. Instead, go to the installed HagiCode Desktop directory and run the hagicode-desktop binary directly.

Use this general process:

1. Locate the actual HagiCode Desktop install directory inside your Steam library
2. Enter the directory that contains the hagicode-desktop binary
3. Run hagicode-desktop directly
4. Avoid starting that session through Steam’s default launch button

Why this preserves the default Electron sandbox

When you launch hagicode-desktop directly, you avoid the default Steam startup path and its compatibility flags, so the app starts in Electron’s default mode instead of inheriting --disable-setuid-sandbox -no-sandbox.

This guidance stays path-agnostic on purpose

There is no single install path that is correct for every Linux distribution, Steam library location, or custom user setup. The stable instruction is to find your own install directory first and launch hagicode-desktop from there.

How to choose

Use this rule of thumb:

• if you want the most compatible “launch from Steam” path, choose Default Steam launch
• if you want to preserve Electron’s default sandbox, choose Manual direct launch of hagicode-desktop

This is a trade-off between the compatibility-first default and the sandbox-preserving manual path, not a claim that one choice is universally correct for every user.