deft hamlet
Background:
So I use openclaw onboarding --install-daemon do the guided installation and choose github copilot as provider, run auth and input the 8-digit code on Github, and set to gpt-5-mini (i am copilot pro user, can use, and it has properly reply my message once ||only||)
Situation:
First conversation
- me
- @bot hi
- bot
- LLM request failed: provider rejected the request schema or tool payload.
Action: backup and clear authorization-related folder and re-authourized
Second conversation
- me
- @bot hi
- bot
- Missing API key for the selected provider on the gateway. Configure provider auth, then try again.
Action: restart gateway
Third conversation
- me
- @bot hi
- bot
- [bootstrap things] (the "succeed reply")
- me
- @bot [reply with the settings]
- bot
- LLM request failed: provider rejected the request schema or tool payload.
Afterwards it only reply with this
Error message:
22:47:09 [agent/embedded] embedded run agent end: runId=<REDACTED_RUN_ID> isError=true model=gpt-5-mini provider=github-copilot error=LLM request failed: provider rejected the request schema or tool payload. rawError=400 The encrypted content for item <REDACTED_ITEM_ID> could not be verified. Reason: Encrypted content item_id did not match the target item id.
22:47:09 [agent/embedded] auth profile failure state updated: runId=<REDACTED_RUN_ID> profile=<REDACTED_PROFILE_HASH> provider=github-copilot reason=format window=cooldown reused=false
22:47:09 [agent/embedded] embedded run failover decision: runId=<REDACTED_RUN_ID> stage=assistant decision=surface_error reason=format from=github-copilot/gpt-5-mini profile=<REDACTED_PROFILE_HASH> rawError=400 The encrypted content for item <REDACTED_ITEM_ID> could not be verified. Reason: Encrypted content item_id did not match the target item id.
I would like to know how to solve this "Encrypted content item_id did not match the target item id."
mint gust