[FEAT] / Marimo New Notebook Generation Support

[simonprovost]

💡 Feature Request

Welcome to the Auctus Search feature request hub! 🎉

Hey there, before you jump in, take a quick sec to check out the
important stuff below—it’ll help us keep the magic flowing smoothly.

Important

Before you proceed, please confirm the following:

• I’ve checked the API docs and confirmed this feature doesn’t already exist (no duplicates, please!).
• I’ve scoured the existing issues to make sure this hasn’t been requested before.
• I get that feature requests are reviewed periodically and might take a little time—patience is key!

---

Describe the Feature Request

Marimo is one of the most promiment new alternative to Jupyter notebook.

https://marimo.io/

It would be fantastic to have dynamic support for notebook manager solutions, such as abstract interfaces that co-implement the needs for Auctus Search but in a Jupyter-format, Marimo-format, and others. Hence, all of them residing based on a general parent abstract classes managing all notebook solutions.

Describe Preferred Solution

This would be done mostly to implement the support for Marimo primarily. As a result, we could ensure that the community surrounding Marimo and the Jupyter notebook could be using Auctus Search. However, I believe it should not be as binary-focused.

Such a feature should welcome abstraction over any prospective notebook solutions, allowing Auctus Search to remain sustainable in the long run. If other notebook managers enter the market, we will be able to quickly adapt and support them based on what Auctus requires viz-notebook-related.

Describe Alternatives

N/A

Related Code

N/A

Additional Context

N/A

If the feature request is approved, would you be willing to submit a PR?

• Yes
• No

(No worries if you’re new to this—we’ll guide you every step of the way! 🤝)