-
Notifications
You must be signed in to change notification settings - Fork 47
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
API-Key for Deepseek is forgotten after every use #34
Comments
Thanks for feedback, I will check it soon. |
you can try the v0.0.9 in which the bug has just fixed. |
you can try the v0.0.9
Thanks! The API-Key is remembered now. And closing the answer window has become possible. Asking PDFs with Deepseek works well. What is the aim of using papersgpt on a collection or subcollection?
|
So do you want to use papersgpt on a collection or subcollection? |
The symbol of papersgpt is shown above collections. If it does not work there, perhaps then it should be removed and only shown, when a PDF is opened. |
Get it. In the Mac backend agent, chatting collection or subcollection of papers is supported, while it is not supported yet on Windows. |
As for you, chatting collection or subcollection of papers would be helpful?
Yes, it could be helpful, but only with a better export of the results, I think. The export (to a note in Zotero?) should include the references in a meaningful way, and that might be difficult to implement, I don't know. At the moment I would be more happy if the features offered would work stable, e.g. mouse control of the answer window, chatting with a pdf. Thank you very much for your efforts!
|
Thanks! If possible, could you record a short video for describing the problem of mouse control? I feel like I'm not quite sure about this issue. |
Hi, I met the same issue, (macOS Monterey Zotero 7 DeepSeek papersgpt 0.0.10) |
Hi, thanks for your plugin! PapersGPT has no problem keeping my API-key for Gemini. But the one for Deepseek is forgotten after every use. Michael (Windows 11, Zotero 7, Deepseek 0.0.8)
The text was updated successfully, but these errors were encountered: