OpenClaw + GitHub Copilot GPT-5.4 Technical Fix Guide Date: 2026-03-07 Overview This guide documents how to make github-copilot/gpt-5.4 work inside OpenClaw when the model already works in OpenCode bu…
Date: 2026-03-07
This guide documents how to make github-copilot/gpt-5.4 work inside OpenClaw when the model already works in OpenCode but fails in OpenClaw.
The final solution requires both:
~/.openclaw/openclaw.jsonThis is necessary because the problem is not only model registration. It is also an OpenClaw transport-routing issue for GitHub Copilot Responses API traffic.
The following errors may appear during debugging:
github-copilot/gpt-5.4 ... not allowed
HTTP 400: bad request: missing Editor-Version header for IDE auth
No API provider registered for api: github-copilot
HTTP 400: model "gpt-5.4" is not accessible via the /chat/completions endpoint
gateway disconnected: closed | idle
There are four distinct problems.
OpenClaw could see the provider, but github-copilot/gpt-5.4 was not fully wired into the active model config path used by the agent defaults.
GitHub Copilot requires IDE-style headers for auth. OpenClaw was sending requests through a generic OpenAI-compatible path, so required headers were not included.
Required headers:
User-Agent: GitHubCopilotChat/0.35.0 Editor-Version: vscode/1.107.0 Editor-Plugin-Version: copilot-chat/0.35.0 Copilot-Integration-Id: vscode-chat
Without them, Copilot returns:
missing Editor-Version header for IDE auth
gpt-5.4 must use the Responses API, not /chat/completions.
So this is wrong for gpt-5.4:
"api":"openai-completions"
This is required instead:
"api":"openai-responses"
openai, not github-copilotEven after changing gpt-5.4 to openai-responses, OpenClaw still fell back to the generic stream path because its embedded runner only activated the Responses transport for provider openai.
That caused OpenClaw to keep hitting /chat/completions for GitHub Copilot GPT-5.4.
~/.openclaw/openclaw.json
/home/water/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/reply-DhtejUNZ.js
~/.openclaw/workspace/ken-patchs/reapply-openclaw-copilot-gpt54-patches.mjs
Update the GitHub Copilot provider block in ~/.openclaw/openclaw.json.
Use:
"baseUrl":"https://api.individual.githubcopilot.com","api":"openai-completions"
Why keep provider API as openai-completions?
github-copilot caused runtime/provider registration failuresSet the gpt-5.4 model entry to:
{"id":"gpt-5.4","name":"GPT-5.4","api":"openai-responses","reasoning":true,"input":["text","image"],"cost":{"input":0,"output":0,"cacheRead":0,"cacheWrite":0},"contextWindow":128000,"maxTokens":64000}
Make sure this exists:
"agents":{"defaults":{"models":{"github-copilot/gpt-5.4":{}}}}
OpenClaw needs to attach Copilot IDE headers before sending provider requests.
In /home/water/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/reply-DhtejUNZ.js, add a wrapper like this near the other provider wrappers:
constGITHUB_COPILOT_IDE_HEADERS={"User-Agent":"GitHubCopilotChat/0.35.0","Editor-Version":"vscode/1.107.0","Editor-Plugin-Version":"copilot-chat/0.35.0","Copilot-Integration-Id":"vscode-chat"};functioncreateGitHubCopilotHeadersWrapper(baseStreamFn){const underlying = baseStreamFn ?? streamSimple;return(model, context, options)=>{returnunderlying(model, context,{...options,headers:{...GITHUB_COPILOT_IDE_HEADERS,...options?.headers }});};}
Then apply it inside the provider wrapper logic:
if(provider ==="github-copilot") agent.streamFn =createGitHubCopilotHeadersWrapper(agent.streamFn);
Find the branch that decides which stream transport to use.
Original behavior:
}elseif(params.model.api ==="openai-responses"&& params.provider ==="openai"){
Replace it with:
}elseif(params.model.api ==="openai-responses"&&(params.provider ==="openai"|| params.provider ==="github-copilot")){
Why this matters:
github-copilot never entered the Responses transport branchstreamSimplestreamSimple hit /chat/completionsAfter this patch:
github-copilot + openai-responses uses the correct Responses transportnode-e"JSON.parse(require('fs').readFileSync('/home/water/.openclaw/openclaw.json','utf8')); console.log('OK')"
node--check"/home/water/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/reply-DhtejUNZ.js"
openclaw gateway restart
github-copilot/gpt-5.4himissing Editor-Version header for IDE auth model "gpt-5.4" is not accessible via the /chat/completions endpoint No API provider registered for api: github-copilot
Because the runtime fix patches the installed OpenClaw bundle, upgrades or reinstalls may overwrite it.
Use the reapply script:
node ~/.openclaw/workspace/ken-patchs/reapply-openclaw-copilot-gpt54-patches.mjs openclaw gateway restart
api: "github-copilot"?That looked tempting, but OpenClaw's runtime path did not have a compatible registered streaming provider for that mode in this setup, which caused runtime/provider registration failures.
openai-completions?Because GitHub Copilot GPT-5.4 is not accessible on /chat/completions. It must go through the Responses API.
OpenCode already handled the GitHub Copilot transport path correctly, including the required Copilot headers and the proper API mode, while OpenClaw needed both config and runtime fixes.
node ~/.openclaw/workspace/ken-patchs/reapply-openclaw-copilot-gpt54-patches.mjs openclaw gateway restart openclaw status
With the config fix and runtime patches in place, github-copilot/gpt-5.4 works in OpenClaw and the gateway remains stable.
微信公众号「极客日志」，在微信中扫描左侧二维码关注。展示文案：极客日志 zeeklog
解析常见 curl 参数并生成 fetch、axios、PHP curl 或 Python requests 示例代码。 在线工具，curl 转代码在线工具，online
将字符串编码和解码为其 Base64 格式表示形式即可。 在线工具，Base64 字符串编码/解码在线工具，online
将字符串、文件或图像转换为其 Base64 表示形式。 在线工具，Base64 文件转换器在线工具，online
将 Markdown（GFM）转为 HTML 片段，浏览器内 marked 解析；与 HTML 转 Markdown 互为补充。 在线工具，Markdown 转 HTML在线工具，online
将 HTML 片段转为 GitHub Flavored Markdown，支持标题、列表、链接、代码块与表格等；浏览器内处理，可链接预填。 在线工具，HTML 转 Markdown在线工具，online
通过删除不必要的空白来缩小和压缩JSON。 在线工具，JSON 压缩在线工具，online