-
Notifications
You must be signed in to change notification settings - Fork 653
Description
📋 CheckList
- I have searched existing issues to avoid duplicates
- I am using a recently maintained version of Coze Loop
- I have provided all required information
- I understand this is a bug report and not a feature request
- I have submitted this report in English (otherwise it will not be processed)
🐛 Bug Description
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoop’s interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoop’s interface authentication?
🔄 Steps to Reproduce
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoop’s interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoop’s interface authentication?
✅ Expected Behavior
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoop’s interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoop’s interface authentication?
❌ Actual Behavior
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoop’s interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoop’s interface authentication?
🚨 Severity
None
🔧 Component
None
💻 Environment
No response
🔧 Go Environment
No response
📋 Logs
📝 Additional Context
No response