You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Marimo’s runtime-aware AI is powerful, but I’m concerned about using it in notebooks that import credentials, read env vars, or create authenticated clients.
It would be useful to have a way to mark variables, env vars, outputs, or objects as unavailable to AI assistants / marimo pair.
This is currently the main thing preventing me from using Marimo as a daily driver alongside or instead of my IDE + AI workflow, because many of my notebooks interact with credentialed services.
Main ask: let users benefit from runtime-aware AI without exposing every live variable, credentialed object, or sensitive output to the model/agent.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Marimo’s runtime-aware AI is powerful, but I’m concerned about using it in notebooks that import credentials, read env vars, or create authenticated clients.
It would be useful to have a way to mark variables, env vars, outputs, or objects as unavailable to AI assistants /
marimo pair.Is this an active exploration topic?
Possible API:
Or config:
This is currently the main thing preventing me from using Marimo as a daily driver alongside or instead of my IDE + AI workflow, because many of my notebooks interact with credentialed services.
Main ask: let users benefit from runtime-aware AI without exposing every live variable, credentialed object, or sensitive output to the model/agent.
Beta Was this translation helpful? Give feedback.
All reactions