What happened?
用户报告了 iFlow CLI 中的错误
对话历史:
[
{
"uuid": "5ae59153-42f1-4af5-a073-01e316735794",
"parentUuid": null,
"sessionId": "session-812051a6-c5c6-45ac-9a54-98efdacc1b95",
"timestamp": "2026-02... (truncated)
What did you expect to happen?
从 2 月 10 日晚上开始,iFlow CLI 就不能使用 DeepSeek 相关模型了,试了多个设备均不能使用
Client information
CLI Version: 0.5.4
Git Commit: 0242d0e (local modifications)
Operating System: linux v20.19.6
Sandbox Environment: 无沙盒
Model Version: deepseek-v3.2-chat
Memory Usage: 274.8 MB
Session ID: 74d2acd4-6098-4c9e-b674-4b7d4359d143
Platform: linux
Internal Report ID: 5567ecc1-2615-440f-b58c-9429c4a0c5b2
Login information
iFlow 账户和 API key 都试了
Anything else we need to know?
错误详情:
错误 (2026-02-11T01:21:03.248Z):
Error: ✕ [API Error: 生成数据错误: HTTP 错误!状态:401,响应:{"error":{"message":"{"routify_response":{"trace_id":"213d0bd217707728632134964d1275","request_id":"c9736baa69d4424d8a03fe6a75b84df4","success":false,"status ":401,"error_source":"CLIENT_ERROR","error_message":"deepseek-v3.2-thinking not authorized","error_detail":{"errorMessage":"deepseek-v3.2-thinking not authorized"}}}","type":"EngineInternalError","code":"401"}}TraceID:00-3d979a78d994e11355c22d63e62da2d4-25a6b623bd723695-01]