#Bug Report: useCopilotChatSuggestions with GPT-5 Model
1 messages · Page 1 of 1 (latest)
Error: [Network] Cannot read properties of undefined (reading 'includes') when using gpt-5
Bug Report: useCopilotChatSuggestions with GPT-5 Model
based on the copilot-chat-with-your-data example and the useCopilotChatSuggestions hooks
env: nodejs 21.0.0
"@copilotkit/react-core": "1.10.0",
"@copilotkit/react-ui": "1.10.0",
"@copilotkit/runtime": "1.10.0",
Could you please check if your organisation is verified and able to access gpt 5?
https://platform.openai.com/settings/organization/general
Sorry, maybe I didn't express it clearly. Let me add some details
Only when using the GPT-5 model and the useCopilotChatSuggestions hook does the error occur, and the suggestions don't display, but the conversation functionality works normally.
When switching the model to GPT-4, there are no problems at all.🫡
Yes, to use GPT-5, you need to verify your organization with OpenAI. That's likely why it's failing with GPT-5 but working with other models. You can read more about the verification process here
I've verified it, but the error still persists.
I've created a minimal reproduction on CodeSandbox to demonstrate the issue:
https://codesandbox.io/p/devbox/mmj8l5
The problem only occurs when using useCopilotChatSuggestions with the GPT-5 model. With GPT-4, everything works fine.
Could you please help check if this might be an issue with the useCopilotChatSuggestions hook when using GPT-5?
If so, let me reach out to the appropriate team member who can answer this more accurately.
Thanks a lot! I'll wait for the update. Please let me know if I can provide any more info to help debug.
Just to clarify - are you using your own openai API key for this integration?
Yes, I’m using my own OpenAI API key from my verified organization account.
Thanks for confirming! I've passed your query to the team and will update you once I hear back.
Appreciate it, I’ll keep an eye out for your update 👍
Hi Wap, looks like OpenAI's API changes to GPT5 had some breaking changes. We'll fix the support here, mind opening a github issue and linking here?