Skip to content

[Windows] CLI crashes immediately: EUNKNOWN open 'B:\~BUN\locales\en_US.json' #8

Closed

Description

@EvC-graphican

Description

I installed the mammouth CLI on Windows following the official documentation.
When trying to run the command mammouth or even mammouth --version, the process crashes immediately with an EUNKNOWN error pointing to a non-existent path (B:~BUN...).

It seems like the localization files (y18n/yargs) are not correctly bundled in the Windows executable (Bun build).

Plugins

No response

OpenCode version

No response

Steps to reproduce

  1. Install Mammouth on Windows (via PowerShell / Installation Script).
  2. Open PowerShell.
  3. Run mammouth or mammouth --version.

Screenshot and/or share link

W:\httpd\contxt git:[main]
mammouth
ERROR 2026-02-13T08:41:55 +325ms service=default name=Error message=EUNKNOWN: unknown error, open 'B:~BUN\locales\en_US.json' stack=Error: EUNKNOWN: unknown error, open 'B:~BUN\locales\en_US.json'
at readFileSync (unknown)
at _readLocaleFile (../../node_modules/.bun/y18n@5.0.8/node_modules/y18n/build/lib/index.js:135:51)
at __ (../../node_modules/.bun/y18n@5.0.8/node_modules/y18n/build/lib/index.js:24:18)
at positional (../../node_modules/.bun/yargs@18.0.0/node_modules/yargs/build/lib/yargs-factory.js:802:81)
at builder (src/cli/cmd/tui/thread.ts:48:8)
at applyBuilderUpdateUsageAndParse (../../node_modules/.bun/yargs@18.0.0/node_modules/yargs/build/lib/command.js:174:35)
at runCommand (../../node_modules/.bun/yargs@18.0.0/node_modules/yargs/build/lib/command.js:164:36)
at [runYargsParserAndExecuteCommands] (../../node_modules/.bun/yargs@18.0.0/node_modules/yargs/build/lib/yargs-factory.js:1415:93)
at parse (../../node_modules/.bun/yargs@18.0.0/node_modules/yargs/build/lib/yargs-factory.js:704:29)
at src/index.ts:115:13
at asyncModuleEvaluation (native:2)
at processTicksAndRejections (native:7:39) fatal
Error: Unexpected error, check log file at for more details

Operating System

Windows 11

Terminal

PowerShell

Activity

  1. mlgarchery commented on Feb 17, 2026

    @mlgarchery
    Collaborator

    damned, I am not able to reproduce

  2. EvC-graphican commented on Feb 17, 2026

    @EvC-graphican
    Author

    It looks like there is a hard-coded path B:\~BUN in the mammouth.exe, that the installer created.

  3. mlgarchery commented on Apr 28, 2026

    @mlgarchery
    Collaborator

    @EvC-graphican can you upgrade with irm "https://code.mammouth.ai/install.ps1" | iex and see if the issue is still there please ?
    Latest version is v1.4.16

  4. EvC-graphican commented on Apr 29, 2026

    @EvC-graphican
    Author

    @EvC-graphican can you upgrade with irm "https://code.mammouth.ai/install.ps1" | iex and see if the issue is still there please ? Latest version is v1.4.16

    Yes, that seems to work! Thank you.

    Previously, I added a fake drive with an empty Bun locale. That helped me to use the mammoth code as a workaround.

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions