[bug] auth login --console on Windows: browser URL is truncated at &, so needapikey=true is dropped and no API key is created
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- git, node.js, powershell, typescript
- Área
- authentication, cli
Línea de trabajo
Start with the browser-opening code path that runs cmd /c start on Windows, which builds the console-login URL and is the source of the unquoted &needapikey=true truncation. Then look at the console-login flow that decides whether to request an API key, and at the non-TTY branch of bl auth login --console that exits and closes the callback port. Done when the URL reaches the browser intact with needapikey=true, and a non-TTY login either waits for completion or prints a clear instruction.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Environment
- CLI: bl 2.1.0
- Skill: 2.1.0
- Node: v24.21.0 (npm 11.19.0)
- OS: Windows 11 家庭版 (Chinese), build 26200, PowerShell 7.6.6
- Region: cn-beijing (domestic,
bailian.console.aliyun.com)
Reproduce
-
On a Windows machine with no model API key configured (
bl auth status→authenticated: false), run:bl auth login --console -
The CLI tries to open the browser via
cmd /c start <url>; the URL contains&needapikey=true, whichcmdtreats as a command separator.
Expected
The browser opens the full console-login URL (including needapikey=true) and an ordinary API key is created and stored, so model commands work afterwards.
Actual
stderr:
Could not open the default browser (Command failed: cmd /c start https://bailian.console.aliyun.com/console-login?notice=127.0.0.1:49309?state=<state>&needapikey=true
'needapikey' 不是内部或外部命令,也不是可运行的程序或批处理文件。
). Open this URL manually:
The console page still reports “CLI 登录成功”, and bl auth status becomes authenticated: true, but only a console-session token is stored — no model API key is written to ~/.bailian/config.json (top-level keys stay access_token / workspace_id / console_site / console_region / console_switch_agent). Model commands keep failing:
bl text chat --message "hello"
Error: No API key found.
Two separate problems on Windows/agent environments:
cmd /c start <url>is not quoted, so the URL is cut at the first&and&needapikey=truenever reaches the console page.- In a non-TTY environment (agent/CI),
bl auth login --consoleprints the URL, then immediately says “This process keeps the local port open for the console … (or wait for idle timeout)” and exits right away, so the local callback port is gone before the user can finish the login.
Note: the printed URL also reads ...?notice=127.0.0.1:<port>?state=<state>&needapikey=true — notice appears to embed a second ? where & would be expected; combined with (1) this makes the truncation hard to notice.
Full output
Could not open the default browser (Command failed: cmd /c start https://bailian.console.aliyun.com/console-login?notice=127.0.0.1:54675?state=<state>&needapikey=true
'needapikey' 不是内部或外部命令,也不是可运行的程序或批处理文件。
). Open this URL manually:
https://bailian.console.aliyun.com/console-login?notice=127.0.0.1:54675?state=<state>&needapikey=true
This process keeps the local port open for the console; press Ctrl+C when finished (or wait for idle timeout).
Config saved to C:\Users\<user>\.bailian\config.json
{
"authenticated": true,
"config": "default",
"config_file": "C:\\Users\\<user>\\.bailian\\config.json",
"console": { "source": "config", "masked": "[REDACTED]", "region": "cn-beijing", "site": "domestic" }
}
Already tried
bl --version(2.1.0) matches the installed skill version (2.1.0) and the latest npm version — no upgrade pending- Re-ran
bl auth login --consoleseveral times (also with--timeout 900); the process still exits immediately in a non-TTY session - Opening the printed URL manually does complete the console-session handshake, but the stored credential still has no API key
- Workaround that worked: use the console's one-click script (
https://bailian.aliyun.com/api-key.ps1, run withKEY/REGION/WORKSPACEenv vars), which decodes theo1_…key and runsbl auth login --config default --api-key <plain> --base-url https://<workspace>.<region>.maas.aliyuncs.com
Suggested fixes
- Quote the URL and pass an explicit title when opening the browser on Windows, e.g.
cmd /c start "" "<url>"(or useStart-Process), so&is not treated as a separator. - In a non-TTY environment, either keep the callback port open until the login completes / times out, or detect the non-TTY case and print “complete this login in an interactive terminal, or use
--api-key”. - Make
auth status/ the success page distinguish “console session only” from “model API key configured”, so users don't believe setup finished while model commands still fail withNo API key found.
Notes
- Frequency: always (Windows 11, PowerShell; reproduced 3×)
- Invoked via: coding agent (non-TTY) on Windows; the same command in an interactive terminal still loses
needapikey=truebecause of (1) - Secrets: API keys and console tokens are redacted as
[REDACTED]
- Lenguaje dominante
- TypeScript
- Estrellas
- 527
- Forks
- 33
- Merge medio
- 6 h 11 min
- PR fusionados (30 d)
- 26
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de modelstudioai/cli
-
[bug]: speech recognize --timeout 未作用于临时 OSS 上传(固定 120 秒)Posiblemente ocupada @hopelynd la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
modelstudioai/cli#243 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
modelstudioai/cli#242 ·
Los mantenedores suelen responder en 1 día
-
[bug] vision describe: default base URL is the Coding Plan endpoint → HTTP 404 for all VL/OCR modelsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
modelstudioai/cli#241 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[bug] bl update: darwin-arm64 binary ships invalid ad-hoc signature, killed by macOS (Killed: 9)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
modelstudioai/cli#223 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 57/100
modelstudioai/cli#239 ·
Los mantenedores suelen responder en 1 día
Todos los issues de modelstudioai/cli
Issues similares
-
./collections should export setUmbracoVersion and setAllowFilePathUploads for in-process consumersAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
umbraco/Umbraco-CMS-MCP-Dev#563 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
afk-ok area:data-quality importer size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
enorm-labs/event-junkie#3166 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
alunduil/projects-v2-sync#21 ·