Skip to content
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

jupyternaut capability to answer questions regarding data #1053

Open
sqlreport opened this issue Oct 24, 2024 · 3 comments
Open

jupyternaut capability to answer questions regarding data #1053

sqlreport opened this issue Oct 24, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@sqlreport
Copy link

Problem

Proposed Solution

@sqlreport sqlreport added the enhancement New feature or request label Oct 24, 2024
@krassowski
Copy link
Member

Independently, one user mentioned to me that they would like to be able to include variables names in their message, and that this is one of the critical feature missing in jupyter-ai to make the UX worth it. It feels like:

  • the chat handler @ should complete variable names (this would need to be fetched from active kernel; there already is a way to do this in the kernel messaging protocol using the same mechanism as tab-completion)
  • information about the variable should be included in the message (jupyter-ai could reuse some of the jupyterlab-variable-inspector code here to get it).

I feel that for jupyter-ai use case the primary usage of @ should be for including variables/files and only secondary for including other users (as this is a less common use-case).

@krassowski
Copy link
Member

@krassowski
Copy link
Member

krassowski commented Oct 24, 2024

For contents of the variable inspect_request (in IPython implemented with pinfo) which is part of the kernel messaging protocol could be used too. Maybe we could even add an argument to tell it that that it is for machine rather than human consumption.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants