Repository navigation
Ask for API keys before sending the first message - #95
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The chat now explains that OpenAI and Jev API keys are required before the first message. Sending text or selecting an example without keys opens the setup dialog before CopilotKit adds a message or starts an agent request.
The draft survives canceling setup and saving keys, including the chat remount. After setup, the user can send the preserved message; it is not sent automatically. New chat and Clear keys clear the draft. Updated onboarding copy and documentation explain the requirement; shared server credentials remain supported for direct API clients.
Validation: