-
-
Notifications
You must be signed in to change notification settings - Fork 341
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
Option for auto-learning project root #290
Comments
Hi, our team has been working on the jupytercoder as a chrome extension. It would be amazing if we could integrate this natively into the jupyter notebook. Starcoder has been trained on purpose on some notebook data to incoporate the output of the cell. |
@liyongsea Could you offer some more details on what you want your PR to implement? We can provide helpful guidance to help navigate your team through our code. |
It is basicly a codex link plugin for jupyter notebook. Currently it is implemented as a chrome extension. We use a trick to simulate the input of a user by modifying the DOM
|
@liyongsea We are most certainly open to the idea, and would welcome a PR. But this feature would have to live inside the current labextension code and not as a separate Chrome extension to be used with Jupyter AI. I expect this to be a fairly difficult task, as you would have to use some JupyterLab autocomplete API in addition to streaming LLM responses from the Jupyter AI server extension. I also wanted to emphasize that this is not something we wish to offer by default. We would never want to automatically send the contents of a user's notebook to a remote LLM without their explicit consent. |
Hi @dlqqq thank you for your reply !
This is also our will, because with the chrome extension, we modify directly the DOM, which is very difficult to maintain
It would be nice if you could point us to a starting point. The difficult part in our previous experience, is to find an appropriate way to modify the input cell in the notebook
Totally agree. |
@liyongsea I would highly recommend two resources: The way to do pretty much anything client-side is via the JupyterLab JavaScript API, which unfortunately isn't that well-documented. I think the best way to learn extension development is to look at our source code. Keep in mind the JavaScript entry point is almost always under |
Hi @dlqqq ,
|
Hi @dlqqq |
@liyongsea Please feel free to submit a PR! We welcome all contributions. I can help with the review. |
Problem
Some users would like to automatically invoke
/learn
on their entire project root at server start to make local RAG easier.Proposed Solution
Right now, I think whether this should be implemented is still an open discussion. I personally am against this, as it violates our principle of never implicitly invoking upstream models without an explicit user action.
The text was updated successfully, but these errors were encountered: