Problem
Settings on the Configuration tab (e.g., Estimated Performance toggle, Deployment Mode) are stored only in Streamlit session state, which is lost when the browser tab is closed or refreshed. Users have to reconfigure their preferences every time they reload the UI.
Expected Behavior
Configuration tab settings should persist across browser resets so users don't need to reconfigure them each session.
Possible Approaches
- Use Streamlit's
st.query_params to encode lightweight settings in the URL
- Persist settings to a backend endpoint (e.g.,
/api/v1/settings) backed by the database or a config file
- Use browser local storage via a Streamlit component
Settings Affected
- Deployment Mode (Simulator / Production)
- Estimated Performance toggle (enable/disable roofline estimation)
- Any future configuration options added to this tab
Problem
Settings on the Configuration tab (e.g., Estimated Performance toggle, Deployment Mode) are stored only in Streamlit session state, which is lost when the browser tab is closed or refreshed. Users have to reconfigure their preferences every time they reload the UI.
Expected Behavior
Configuration tab settings should persist across browser resets so users don't need to reconfigure them each session.
Possible Approaches
st.query_paramsto encode lightweight settings in the URL/api/v1/settings) backed by the database or a config fileSettings Affected