Skip to content

[Windows] The CLI cannot start when MINIMAX_DATA_DIR points at a volume without hard-link support (FAT32/exFAT), and the error names a directory instead of the filesystem #619

Open

Description

@Ralle1976

Titel

[Windows] The CLI cannot start when MINIMAX_DATA_DIR points at a volume without hard-link support (FAT32/exFAT), and the error names a directory instead of the filesystem

Product or interface

CLI - headless

Version

0.7.2 (source main @ 3c21163 = tag code-sdk-python-v0.1.1; the release tag v0.7.2 = c6c7f28) — the published npm CLI
@minimax-ai/code@0.7.8 contains the same code path (see "Scope" below).
Node.js v24.18.0, pnpm 9.15.0.

Platform

Windows

OS version and architecture

Windows 11 x64, build 26200

Issue area

File / workspace / path / encoding


Steps to reproduce

MINIMAX_DATA_DIR is a documented way to move the data directory
(README.md, "Accounts and data"; docs/installation.md). Point it at a volume whose
filesystem cannot create hard links — FAT32 or exFAT on a USB stick or SD card, or a network
share — and start the CLI:

# X: must be a FAT32 or exFAT volume (USB stick, SD card, or network share)
$env:MINIMAX_DATA_DIR = 'X:\mcode-data'
mcode exec "print hello"

Control run on an NTFS volume with the identical command:

$env:MINIMAX_DATA_DIR = 'X:\mcode-data-ntfs'
mcode exec "print hello"

To confirm the volume type of the target drive:

Get-CimInstance Win32_LogicalDisk | Select-Object DeviceID, DriveType, FileSystem

The failure happens during startup, before any provider request, so no account, key, or
network access is involved.

Expected and actual behavior

Expected. The CLI either works on such a volume, or it stops with a message that names the
actual cause — for example that the data directory has to live on a local NTFS volume because
the runtime publishes agent and session files through atomic hard links.

Actual. The CLI aborts during startup with a raw Node errno that names neither the
filesystem nor the hard-link operation:

  • ENOTSUP: operation not supported on socket, link '…' -> '…' on a volume whose driver
    reports ERROR_NOT_SUPPORTED (Win32 error 50),
  • EISDIR: illegal operation on a directory, link '…' -> '…' on a Cloud-Files-API volume
    (e.g. a Google Drive mount that reports itself as FAT32).

Both are the same situation — "this filesystem cannot create hard links" — and neither text
lets the user act on it. "on socket" and "illegal operation on a directory" are both wrong:
no socket and no directory are involved.

Redacted error summary

ENOTSUP: operation not supported on socket, link 'X:\mcode-data\v2\migration\manifests\.legacy-agent-bootstrap-import-v1.json.<pid>.<uuid>.publish' -> 'X:\mcode-data\v2\migration\manifests\legacy-agent-bootstrap-import-v1.json'
    at async publishFileIfAbsentWithLabel (packages/local-runtime-v2/src/infra/file/jsonl.ts:313:7)

On a Cloud-Files-API volume the same call reports:

EISDIR: illegal operation on a directory, link 'X:\mcode-data\v2\migration\manifests\.legacy-agent-bootstrap-import-v1.json.<pid>.<uuid>.publish' -> 'X:\mcode-data\v2\migration\manifests\legacy-agent-bootstrap-import-v1.json'

The errno code depends on the filesystem driver, so the portable statement is: the call
fails with a filesystem-specific errno.

Screenshots

(none)

Before submitting

  • I have searched existing issues.
  • I have included my version and removed sensitive information.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions