Add a new plugin to provide IMagicProvider#5
Add a new plugin to provide IMagicProvider#5Zsailer merged 6 commits intojupyter-ai-contrib:mainfrom
IMagicProvider#5Conversation
IMagicProviderIMagicProvider
|
This is great! Thank you @jtpio. This makes sense to me. For context, I'm hoping to make the backend more general to other "intelligence" features. The design here is pretty straightforward but powerful. The client POST's to the server, which has access to agents + models. The Jupyter event that comes back is a list of JupyterLab commands that drive the UI. In summary, "natural language prompt to JupyterLab commands". JupyterLab commands just need to be passed to the LLM as context. This simple bridge can be used by all sorts JupyterLab activities. What I'd really like to do is offer a way for JupyterLab plugins to register (1) JupyterLab commands and (2) custom input schemas with server-side agents that will be passed to models as context. That way, any plugin can easily register new UX it brings and offer it to the agents + LLMs for usage. I say all this to say, this API will probably change a bit going forward. As long as you're okay with this being a little experimental for now, I think exposing this token is great! |
|
Thanks @Zsailer, sounds good!
I think it's fine, all of this is still in early stages anyway. The main motivation is to allow for not having to depend on a specific backend to enable the AI features, for example:
|
|
This is great @jtpio. If you would like to pull this out of draft state, I can review, merge and release. |
|
Sure, I pushed a couple more changes. But this is probably the kind of thing that is still likely to change quickly anyway, so happy to iterate on it. Also feel free to make some edits to the PR directly if needed. |
e431e9d to
89f9b37
Compare
89f9b37 to
cdf2d3f
Compare
This should help with #4
Currently the extension relies on making a request to
/api/ai/magic.This PR moves the request part to a separate plugin, so it can more easily swapped by other extensions.