Switch to a monorepo structure?

[jtpio]

For now having a simple directory structure which follows the extension template is enough.

However in the long run it may be more convenient to switch to a monorepo structure, and place all frontend packages under the packages folder.

Some ideas for new packages that could be developed in this repo:

• run LLMs locally in the browser: Leverage a Code-tuned SLM in-browser #24
• agents framework for integration with something like jupyterlab-magic-wand: Magic wand support #34

[jtpio]

Some ideas for new packages that could be developed in this repo:

But depending on whether these packages should be generic enough so they can be reused in Jupyter AI too, maybe they could also live in different repos (and different orgs). To be discussed.

[brichet]

That would indeed be a good idea to switch to a monorepo structure.

I wonder if we should keep it simple, one extension and one package containing everything to build a frontend agent (provider registry, settings model, tools registry,...) or split it in several extensions (e.g. a main extension with the chat, one for the default providers...) and/or packages (agent manager, tool registry, provider registry...)

[brichet]

In any case we could indeed integrate browser LLM https://github.com/jtpio/jupyterlab-browser-ai in a new package.