-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“Token not currect, Please checking your Logseq Authorization Setting #23
Comments
Hey @DutchPete What is the options in your browser, what browser you are using, what version of logseq copilot you are using? |
What do you mean by “options”? |
Logseq Market? I release this on the Chrome web store Edge Add-ons and Firefox add-ons. Below is the image of the options page. At the search engine pages which copilot support like Bing You can see the If you can see the options page, fill |
And this is the reason #17 is in the plan. |
Oops, sorry, my mistake, I did install it from the Chrome Web Store. From what I understand, I can now access Logseq from my browser. The big questions:
My apologies for dumb questions, I am a Logseq newbie. |
No worries, that hints to me should hurry up for #17.
|
Close this, since the main issues were fixed. |
This is what my authorization setting looks like:
This is as per your instructions. What am I doing wrong?
The text was updated successfully, but these errors were encountered: