MiniMax Code Common Issues

This page applies to common startup and unresponsive-app issues in current MiniMax Code versions. Windows clients after 3.0.48 no longer depend on OpenCode, so troubleshooting steps for older OpenCode / daemon behavior are not used as the basis for current versions.

Startup Failure - Type 1

If you see utility exited before ready (code=9) during startup, this currently affects some macOS x64 (Intel) users.

Workaround: download and reinstall the macOS Intel x64 v3.1.1 build.

Platform	Mainland China	Global
macOS Intel x64	Download v3.1.1	Download v3.1.1

Windows Browser Launch Failure

If Desktop login shows Failed to open: 找不到应用程序。 (0x800401F5) or returns no_default_browser, Windows usually does not have a usable default browser or the browser association is broken. Workaround:

Install a browser such as Edge or Chrome.
Set it as the Windows default browser.
Restart MiniMax Code and try again.

If it still fails, reassign the Windows web browser association in Default apps and retry. You can also open the login page directly in your browser: https://agent.minimax.io/login?sso=1

General Issues

MiniMax Code fails to start

If MiniMax Code shows a startup error, first check whether the issue is caused by an older installer.

Startup issues caused by official packaging builds have been fixed in newer versions. Download the latest official installer and reinstall MiniMax Code.

Platform	Mainland China	Global
macOS Apple silicon	Download v3.1.1	Download v3.1.1
macOS Intel	Download v3.1.1	Download v3.1.1
Windows 64-bit	Download v3.1.1	Download v3.1.1

MiniMax Code is not responding

If the app freezes, a request stays pending for a long time, or the page stops producing output, check the following in order:

Confirm that your network connection is working.
If you installed the Mainland China version and the issue looks like a timeout, check whether your computer is connected to a proxy.
Check the service status indicator at the bottom of the app.
Fully quit and restart the app.
If the issue continues, upload logs from Settings and contact support.

MiniMax Code service fails to start

If you see a “service startup failed” dialog, first check for leftover processes, then check whether .mavis and .minimax exist and look valid in the current user’s home directory.

End leftover processes first

Windows:

Open Task Manager.
Search for minimax.
End the related processes.
Wait about 10 seconds.
Restart the app.

macOS:

Open Activity Monitor.
Search for minimax.
Force quit the related processes.
Wait about 10 seconds.
Restart the app.

Check user data directories

If the service still fails to start after restarting, check .mavis and .minimax under the current user’s home directory. Windows PowerShell:

Test-Path "$env:USERPROFILE\.mavis"
Test-Path "$env:USERPROFILE\.minimax"
Get-ChildItem -Force "$env:USERPROFILE\.mavis" -ErrorAction SilentlyContinue | Select-Object -First 5
Get-ChildItem -Force "$env:USERPROFILE\.minimax" -ErrorAction SilentlyContinue | Select-Object -First 5

macOS Terminal:

ls -la ~/.mavis ~/.minimax

If either directory is missing, empty, clearly corrupted, or contains abnormal data, back it up first, then delete .mavis and .minimax and restart the app.

Back up and delete data directories

Windows PowerShell:

$backupRoot = Join-Path $env:USERPROFILE ("minimax-data-backup-" + (Get-Date -Format "yyyyMMdd-HHmmss"))
New-Item -ItemType Directory -Path $backupRoot | Out-Null

if (Test-Path "$env:USERPROFILE\.mavis") {
  Copy-Item -Recurse -Force "$env:USERPROFILE\.mavis" $backupRoot
}

if (Test-Path "$env:USERPROFILE\.minimax") {
  Copy-Item -Recurse -Force "$env:USERPROFILE\.minimax" $backupRoot
}

Remove-Item -Recurse -Force "$env:USERPROFILE\.mavis", "$env:USERPROFILE\.minimax" -ErrorAction SilentlyContinue

macOS Terminal:

backup="$HOME/minimax-data-backup-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$backup"
[ -e "$HOME/.mavis" ] && cp -a "$HOME/.mavis" "$backup/"
[ -e "$HOME/.minimax" ] && cp -a "$HOME/.minimax" "$backup/"
rm -rf "$HOME/.mavis" "$HOME/.minimax"

Back up the directories before deleting them. .mavis and .minimax may contain local settings, cache data, or session-related data.

Restart the app after deletion. MiniMax Code will regenerate the required data directories. If the issue still continues, upload logs from Settings and contact support. The login redirect may be blocked by a proxy or system policy. Open the login link directly in your browser:

Mainland China: https://agent.minimaxi.com/login?sso=1
Global: https://agent.minimax.io/login?sso=1

After logging in, choose to open the MiniMax Code app.

Windows Issues

Installation or update fails because the file path is too long

An overly long installation path can cause installation or updates to fail on Windows. The installer may report that MiniMax Code cannot be closed and ask you to close it manually before clicking Retry.

Windows installer unable to close MiniMax Code, with Task Manager on the right (Chinese UI)

Why this happens

Traditional Win32 file operations have a MAX_PATH limit of 260 characters, including the terminating null character. This applies to the full path: the installation directory, nested folders, and file name. Some resources in older releases used deeply nested folders or long directory names. Combined with a long installation directory, these paths can hit the limit and cause installation, uninstallation, or in-place updates to fail. The internal resource layout has been shortened to address this issue. However, long-path files left by an older installation can still block its uninstaller, so running a newer installer over the existing installation may also fail. Reinstalling into a shorter directory leaves more room for the paths inside the app.

Workaround

Cancel the failed installation or update, and quit any open MiniMax Code app.
Download the latest Windows installer from the official download page.
Run the installer again. When choosing the installation location, select a shorter path with fewer nested folders, such as C:\MiniMaxCode, and complete the installation.
Launch MiniMax Code and check that it works normally.

In one reported case, trying a newer installer alone did not help. The user reported success after following the advice to change the installation directory and reinstall. If a newer installer still shows the same message, try the steps above.

A MiniMax-related process in Task Manager may belong to the installer or updater. Ending that process interrupts installation. Check what each process is doing before ending it, rather than stopping every process with MiniMax in its name.

If installation still fails, send support a screenshot of the error, your Windows version, the installer version, and the full installation path.

The window flashes and exits after double-clicking

A common verified cause is abnormal ACL permissions in the Windows installation directory, which prevents the Chromium / Electron renderer sandbox from starting. Typical signals:

Check	Result
Crash source	`render_process_gone`
Crash reason	`crashed`
exit code	`-2147483645`, also known as `0x80000003 / EXCEPTION_BREAKPOINT`
Crash stage	renderer process startup

Temporary confirmation

Start the app from PowerShell with --no-sandbox:

& "C:\Users\Admin\AppData\Local\Programs\MiniMax Internal Code\MiniMax Internal Code.exe" --no-sandbox

If the app opens with --no-sandbox but exits when launched normally, the issue is likely in the Chromium renderer sandbox permission chain.

Use --no-sandbox only for temporary verification or temporary access. It is not recommended for long-term use because it weakens Electron renderer security isolation.

Fix

Repair the installation directory ACL, then start the app normally:

icacls "C:\Users\Admin\AppData\Local\Programs\MiniMax Internal Code" /reset /T /C
icacls "C:\Users\Admin\AppData\Local\Programs\MiniMax Internal Code" /grant "*S-1-15-2-2:(OI)(CI)(RX)" /T /C

Parameter reference:

Parameter	Meaning
`S-1-15-2-2`	Windows AppContainer-related identity
`RX`	Read + Execute permission
`(OI)(CI)`	Inherit permissions to child files and directories
`/T /C`	Process recursively and continue on errors

If MiniMax Code is installed in another directory, replace the path in the command. For example:

icacls "D:\MiniMax Code" /grant "*S-1-15-2-2:(OI)(CI)(RX)" /T /C

macOS Issues

render-process-gone on startup (exitCode=5)

After starting the app, you may see a “Page encountered an error” dialog with the following details:

kind=render-process-gone
reason=crashed
exitCode=5

macOS startup error dialog showing render-process-gone, crashed, and exitCode=5 (Chinese UI)

One confirmed cause: system version compatibility mode

In a case involving macOS 12.7.6 and MiniMax Code 3.0.74, crash dumps confirmed that app subprocesses read the compatibility version 10.16.0, triggered Chromium’s system version check, and exited. Both the page process and the local service process may fail during startup in this situation. SYSTEM_VERSION_COMPAT controls macOS system version compatibility behavior. When set to 1, relevant system interfaces may return a compatibility version for older software; setting it to 0 disables this behavior. The variable’s actual value and configuration source have not been confirmed in this case, and the user has not yet reported the result of disabling compatibility mode on the affected machine.

exitCode=5 alone does not identify the cause. The steps below help investigate system version compatibility issues; other crashes still require logs and crash dumps to diagnose.

Start with a one-time launch comparison

Quit MiniMax Code completely. If any processes remain, identify and end only those belonging to the app in Activity Monitor.
Open Terminal and explicitly disable compatibility mode for this launch:
SYSTEM_VERSION_COMPAT=0 "/Applications/MiniMax Code.app/Contents/MacOS/MiniMax Code"
Replace the path if the app is installed elsewhere. Keep Terminal open while observing the startup result. This setting applies only to this launch and its child processes; it does not change system configuration or delete app data.
If the app starts successfully, check where SYSTEM_VERSION_COMPAT=1 is set in the original launch environment, such as shell configuration, a launch script, or the login session environment. Prefer removing or adjusting that source. Preserve the original configuration until its purpose is understood, as older software may depend on compatibility mode.

If the one-time comparison works and you also want to use this setting when launching from Finder or the Dock, follow these steps in Terminal. No sudo is required. First, query and record the original value. No output usually means the variable is not set in this login session:

launchctl getenv SYSTEM_VERSION_COMPAT

Then set and query it. The second command should print 0:

launchctl setenv SYSTEM_VERSION_COMPAT 0
launchctl getenv SYSTEM_VERSION_COMPAT

Quit the app completely and start it again. The setting affects subsequent processes that inherit this environment; existing processes are not updated. Terminal and graphical launches may use different environments, and shell configuration or launch scripts may override the variable. The setting is not guaranteed to persist after logout or restart. For a lasting change, locate and adjust the original configuration source.

This setting applies to the current user’s login session and may affect other apps launched in the same environment. Older software that depends on compatibility version numbers may be affected. It is not a permanent or all-users system-wide setting.

To undo the change: if the variable was originally unset, run launchctl unsetenv SYSTEM_VERSION_COMPAT. If it had a value, restore it with launchctl setenv SYSTEM_VERSION_COMPAT ORIGINAL_VALUE, replacing ORIGINAL_VALUE with the recorded value. Then quit and restart the affected apps completely.

If the app still crashes

Do not clear app data based solely on this error code. Click “Upload logs” in the dialog (or upload from Settings if accessible), and provide support with the Upload ID, app version, macOS version, launch method, and the one-time launch comparison result. If crash dumps are needed, follow support’s instructions. Do not publish raw logs or dumps publicly.

Startup or service abnormalities

For the render-process-gone error above, start with its dedicated section. For other macOS startup or service issues, follow “MiniMax Code service fails to start” under General Issues: end related minimax processes in Activity Monitor, then check, back up, and delete ~/.mavis and ~/.minimax if needed before restarting the app.

Upload logs

If support needs to investigate further, upload logs from app Settings and include the following information:

Information	Example
Operating system	Windows / macOS
App version	For example, `3.1.1`
Installation source	Mainland China version / Global version / inside build
Symptom	Unresponsive / crash on startup / service startup failure
Proxy in use	Yes / No

Get Started

Core Workflows

Desktop Features

Agent Capabilities

Automation & Remote

Models & Account

Help

Common Issues

Startup Failure - Type 1

Windows Browser Launch Failure

General Issues

MiniMax Code fails to start

MiniMax Code is not responding

MiniMax Code service fails to start

End leftover processes first

Check user data directories

Back up and delete data directories

Windows Issues

Installation or update fails because the file path is too long

Why this happens

Workaround

The window flashes and exits after double-clicking

Temporary confirmation

Fix

macOS Issues

render-process-gone on startup (exitCode=5)

One confirmed cause: system version compatibility mode

Start with a one-time launch comparison

If the app still crashes

Startup or service abnormalities

Upload logs

​Startup Failure - Type 1

​Windows Browser Launch Failure

​General Issues

​MiniMax Code fails to start

​MiniMax Code is not responding

​MiniMax Code service fails to start

​End leftover processes first

​Check user data directories

​Back up and delete data directories

​The login button does not respond

​Windows Issues

​Installation or update fails because the file path is too long

​Why this happens

​Workaround

​The window flashes and exits after double-clicking

​Temporary confirmation

​Fix

​macOS Issues

​render-process-gone on startup (exitCode=5)

​One confirmed cause: system version compatibility mode

​Start with a one-time launch comparison

​Disable compatibility mode for the current user’s login session

​If the app still crashes

​Startup or service abnormalities

​Upload logs

Startup Failure - Type 1

Windows Browser Launch Failure

General Issues

MiniMax Code fails to start

MiniMax Code is not responding

MiniMax Code service fails to start

End leftover processes first

Check user data directories

Back up and delete data directories

The login button does not respond

Windows Issues

Installation or update fails because the file path is too long

Why this happens

Workaround

The window flashes and exits after double-clicking

Temporary confirmation

Fix

macOS Issues

render-process-gone on startup (exitCode=5)

One confirmed cause: system version compatibility mode

Start with a one-time launch comparison

Disable compatibility mode for the current user’s login session

If the app still crashes

Startup or service abnormalities

Upload logs