Skip to content

Jupyter-AI considers only local filesystem creating misalignment with ContentsManager #1192

Open
@MaicoTimmerman

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

dlqqq commented on Jan 7, 2025

@dlqqq
Member

@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.

added this to the v3.0.0 milestone on Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Jupyter-AI considers only local filesystem creating misalignment with ContentsManager · Issue #1192 · jupyterlab/jupyter-ai