Jupyter AI
11–20 of 37 posts
Re: Jupyter AI
#12Edit: it’s running via a llama.cpp server
Re: Jupyter AI
#13Re: Jupyter AI
#14I've tried a number of notebook AIs, jupyter ai, hex, deepnote, einblick. The one that worked best for me was einblick probably because it's data-aware. For AIs that don't support that you need to be overly specific when writing prompts, which is annoying, and you keep having to rename/reference the correct dataframes and variables (even more annoying).
Re: Jupyter AI
#15Re: Jupyter AI
#16Re: Jupyter AI
#17This is probably the more helpful page as it shows what you can do: https://jupyter-ai.readthedocs.io/en/latest/users/index.html... This is a nice feature! Not huge, but it's great DevEx (MLEngEx...?)
Incorrect API key provided error on jupyter for chatgpt. I'm on a paid account so not sure why...
Re: Jupyter AI
#18Re: Jupyter AI
#19This looks useful, but not quite what I hoped. GPT4 with Code Interpreter is a fun, frustrating experience where you’re writing a dialog about writing some code, sort of like pair programming or a code interview. Compared to a notebook, it’s terrible. The sandbox environment resets if you take a break. There’s also a quota, and if you hit that it forces taking a break, causing a reset. In a notebook, you could rerun…
It lets you pair program with gpt-4 like you are describing. But the source code lives in your local git repo. You can start a new project or work with an existing repo. You can fluidly switch back and forth between a coding chat where you ask gpt to edit the code and your own editor to make edits yourself.
Re: Jupyter AI
#20I've tried a number of notebook AIs, jupyter ai, hex, deepnote, einblick. The one that worked best for me was einblick probably because it's data-aware. For AIs that don't support that you need to be overly specific when writing prompts, which is annoying, and you keep having to rename/reference the correct dataframes and variables (even more annoying).
For louie.ai, we've been going for data-aware from the get-go, and more broadly, doing a LLM-first tool design rethink. In the large, as I look around, it feels super early for the dev community figuring out core genAI notebook tool uses, flows, & assumptions. Likewise, zooming-in on individual feature experiments, current tools feel rough & underpowered relative to what we already know is possible.
We've been forced to question a lot as we've been learning from going operational and experimenting with design. Again, if up for it, would love to chat & exchange notes!