♻️ Reproduction Steps
- Try copilotkit popup component with wrong runtimeUrl parameter, ui throws error and you cannot continue your work at the other sides of the ui without a valid and up copilotkit runtime.
- In production, it always try to connect/reconnect to the runtimeUrl in an infinite loop, and the browser's console displays lots of errors.
✅ Expected Behavior
CopilotKit popup component (and the other copilotkit components) should display only one slient connection error in the browser's console, and the developer should be able to continue to his work with react ui without seeing any error at the ui.
If possible, CopilotKit popup component should display itself without correct runtimeUrl by displaying labels and its initial.
❌ Actual Behavior
The saas app ui displays one big "agent not found" or "fetch failed" error in development mode.
𝌚 CopilotKit Version
@copilotkit/react-core@1.50.1
@copilotkit/react-textarea@1.50.1
@copilotkit/react-ui@1.50.1
@copilotkit/runtime@1.50.1
📄 Logs (Optional)
♻️ Reproduction Steps
✅ Expected Behavior
CopilotKit popup component (and the other copilotkit components) should display only one slient connection error in the browser's console, and the developer should be able to continue to his work with react ui without seeing any error at the ui.
If possible, CopilotKit popup component should display itself without correct runtimeUrl by displaying labels and its initial.
❌ Actual Behavior
The saas app ui displays one big "agent not found" or "fetch failed" error in development mode.
𝌚 CopilotKit Version
📄 Logs (Optional)