uv-native workflow (uv add / uv run)

[mstarodub]

Description

uv already gives us reproducibility with lockfiles, so the --sandbox feature of marimo and hiding away uv isn't helpful if one already uses the modern uv interfaces.

Instead, it would be good if marimo's dependency handling was aware of 1. uv projects (uv init/ uv add, refer to astral-sh/uv#9219) and 2. ephemeral uv environments (uv run).

These are the workflows to reproduce:

uv init .
uv add marimo torch
uv run marimo edit 

Then, inside marimo, make a new file, in a new cell, type: import numpy.
Observe the "install with" / missing dependency popup showing.
pip is selected as default. It should be uv, and running "install" should uv addinside the current project.

Simply running
uv run --with marimo --with torch marimo edit
from the terminal, then once again importing numpy in a new cell inside the notebook.
Clicking install on the popup should absolutely not install anything, since the environment is supposed to be ephemeral. I am not sure what the right behaviour here should be. Perhaps it would be possible to dynamically modify that ephemeral uv environment?

Suggested solution

see above

Alternative

No response

Additional context

No response