Skip to content

Added OOBE key check on first run#1953

Open
avdeshjadon wants to merge 1 commit intomicrosoft:mainfrom
avdeshjadon:fix/oobe-check-keys-on-first-run
Open

Added OOBE key check on first run#1953
avdeshjadon wants to merge 1 commit intomicrosoft:mainfrom
avdeshjadon:fix/oobe-check-keys-on-first-run

Conversation

@avdeshjadon
Copy link

added a check on first run to see if the required api keys are set. if they're missing, it shows a dialog with what keys are needed and a button to open the setup docs.

Closes #1892

@avdeshjadon
Copy link
Author

@microsoft-github-policy-service agree

1 similar comment
@avdeshjadon
Copy link
Author

@microsoft-github-policy-service agree

@robgruen robgruen changed the title fix: add oobe key check on first run Added OOBE key check on first run Mar 2, 2026
if (result.response === 0) {
shell.openExternal(
"https://github.com/microsoft/TypeAgent/blob/main/ts/README.md",
);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's exit the application after the user selects "open external." When I did the main app continued to execute and throw an error which was a bit unexpected and a lesser user experience. If the user hits "continue anyway" I think it's ok to fail like this.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Need OOBE experience

2 participants