Jupyter-AI considers only local filesystem creating misalignment with ContentsManager #1192
Open
Description
Description
Jupyter-server uses jupyter_server.services.contents.manager.ContentsManager
for interactions with the filesystem. This gives users the ability to attach external file systems to Jupyter, for example hosted on object storage (i.e. S3 or HDFS).
Now when using Jupyter-AI, the /generate
and @file
methods, will try to read from local filesystem. However, when an non-local Contents-Manager is used, the files never show up in the JupyterLab UI.
Reproduce
Not really relevant
Expected behavior
- For the UI to show contents generated by Jupyter-AI commands, such as
/export
and/generate
. - For the
@file
context provider to load files shown in the UI.
Activity
dlqqq commentedon Jan 7, 2025
@MaicoTimmerman Thank you for opening an issue for this. I agree this ought to be fixed; JupyterLab extensions should be expected to have strong integrations with the rest of the JupyterLab ecosystem.
I've added this to the Jupyter AI v3 milestone for us to track. I'll keep this in mind as I continue to iterate on the chat command design for v3.