Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: CLI hard-fails on startup when ALL_PROXY=socks5://…

Open Beginner friendly
  • Is something wrong?
#393 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript
Domain
cli, networking

Research direction

Start in packages/tui/src/cli/network-proxy.ts, especially validateProxyValue() and resolveTuiProxyConfiguration(), then reproduce with ALL_PROXY set to a SOCKS5 URL. The work is done when mcode no longer exits during startup and the chosen unsupported-proxy behavior is covered by an appropriate check.

Written by the indexing model from the issue text.

Description

bug needs-triage tui
Product or interface

CLI - interactive TUI

Version

Node.js v24.x, pnpm 9.12.0 (not required to reproduce the preflight alone).

Platform

Windows

OS version and architecture

Windows 11 x64 (build 26200)

Issue area

Startup / install / update

Desktop log upload ID (optional)

No response

Steps to reproduce

  1. Set ALL_PROXY to a SOCKS5 URL in your shell:
    export ALL_PROXY=socks5://127.0.0.1:1080

  2. Run the CLI:
    mcode

  3. Observe: process throws immediately before the TUI loads.

No credentials, keys, or project files required — any invocation reproduces it.

Expected and actual behavior

Expected:
CLI starts normally. If SOCKS5 tunneling is unsupported, it should either
warn and fall back to direct mode, or document the limitation — but not crash.

Actual:
Process exits before start with:
Error: ALL_PROXY must be an http:// or https:// URL.

Root cause: packages/tui/src/cli/network-proxy.ts → validateProxyValue()
(line 88) hard-throws for any scheme other than http: or https:.
Users with a system-wide SOCKS5 proxy set via ALL_PROXY cannot launch
mcode at all.

Related: #82 (different layer — that is Electron/undici UnsupportedProxyProtocol
mid-request; this bug is CLI bootstrap validation, triggered before any
network call is made).

Redacted error summary
Error: ALL_PROXY must be an http:// or https:// URL.
    at validateProxyValue (packages/tui/src/cli/network-proxy.ts:89)
    at resolveTuiProxyConfiguration (packages/tui/src/cli/network-proxy.ts:40)
Screenshots

No response

Before submitting
  • I have searched existing issues.
  • I have included my version and removed sensitive information.
Dominant language
TypeScript
Stars
1.9k
Forks
226
Avg merge
3h 32m
Merged PRs (30d)
122

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MiniMax-AI/minimax-code

All issues in MiniMax-AI/minimax-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.