using-streamlit-session-state

To persist variables across Streamlit reruns, use `st.session_state` to store data. This prevents variables from resetting when the script executes top-to-bottom after each user interaction.

Your Streamlit app resets data because the framework reruns scripts top-to-bottom on every interaction. Managing state with `st.session_state` solves this by maintaining persistent data across reruns.

You can share data across multiple pages in a Streamlit app by storing variables in `st.session_state`. This allows multipage applications to access and update the same persistent data.

Streamlit widgets automatically sync with session state when you assign them a `key` parameter. This binds the widget's value directly to `st.session_state` for seamless state management.

The best way to initialize session state in a Streamlit app is organizing state assignments at the top of your script. This initialization pattern ensures clarity and consistent data availability before workflows execute.

You can use callbacks to update Streamlit session state before script reruns. This allows you to manage state changes proactively, ensuring data is updated prior to the script execution cycle.