CommandCodeAI / CommandCodeAI/command-code

Provider API: GPT-5.6 Luna returns 403 "Authentication failed" despite docs listing it as available on GOAT plan

未關閉
#736 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

Summary

The Provider API rejects gpt-5.6-luna with 403 permission_error / "Authentication failed. Please check your credentials.", even though the docs state GPT-5.6 Luna is "Available on every plan, including Go" (https://commandcode.ai/docs/resources/pricing-limits). The same API key works fine with GPT-5.6 Sol, DeepSeek V4, Grok, Kimi, Qwen, GLM etc. google/gemini-3.7-flash exhibits the identical wrong error, while models that genuinely require a higher plan (Terra, Gemini 3.5/3.6, Claude family) correctly return MODEL_NOT_IN_PLAN.

Expected Behavior

gpt-5.6-luna works via Provider API on a GOAT plan (or any plan), as documented on https://commandcode.ai/docs/plans/goat (model table + usage estimates) and https://commandcode.ai/docs/resources/pricing-limits ("Available on every plan, including Go").

Actual Behavior

Every request to gpt-5.6-luna returns:

HTTP 403
{"error":{"message":"Authentication failed. Please check your credentials.","type":"permission_error"}}

Note: permission_error / "Authentication failed" is not listed among the documented Provider API error codes (https://commandcode.ai/docs/provider) — the table there only defines 403 upgrade_required. Reproducible over direct connection and via proxy, from multiple regions, repeatedly (also reproduced in earlier weeks, not just today).

Steps to reproduce the issue
curl https://api.commandcode.ai/provider/v1/chat/completions \
  -H "Authorization: Bearer ***" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-5.6-luna","messages":[{"role":"user","content":"hi"}],"max_tokens":16}'

The key IS valid (authenticates fine for other models) and GET /provider/v1/models lists gpt-5.6-luna.

Command Code Version

use API KEY

Operating System

Linux

Terminal/IDE

No response

Shell

No response

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

Docs contradicting observed behavior:

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

首先,重現對 /provider/v1/chat/completions 發出的 curl 請求,並使用同一個 key 將其與一個正常運作的模型進行比較。接著閱讀該 endpoint 所參照的 Provider API 模型清單、方案驗證與錯誤處理路徑,以及連結的定價與 provider 文件。當符合資格的模型回傳文件中所述的回應或正確的文件中所述方案錯誤,而不是 Authentication failed 時,即表示完成。

由索引模型根據 Issue 內容生成。

評估

領域
api, backend
Issue 類型
缺陷
難度
3/5
預估耗時
1-2 天
活躍度
活躍
描述清晰度
基本清楚
新手友好度
52/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。