agilab-streamlit-pages

To prevent Streamlit session state leaks, enforce guarded state initialization and consistent widget keys within each page. This ensures isolated page boundaries and stops unintended reruns or duplicate keys across modular app surfaces.

Structure scalable Streamlit apps by separating main app code from apps-pages directories and using modular page composition. Enforcing explicit frontmatter metadata and consistent page patterns prevents UI glitches and improves reliability across projects.

Streamlit throws duplicate widget key errors during reruns when page boundaries are unclear and keys are not safely managed. Applying stable widget key management and session-state safety patterns resolves these UI glitches.

Yes, these Streamlit page patterns directly target AGILAB projects containing main_page.py, pages/*, and apps-pages/*/src files. The guidance enforces safe state initialization and modular app surfaces across these specific project structures.

Add argument forms and diagnostics to Streamlit pages by applying documented reusable page composition patterns. Utilizing app_args_form.py views and modular components ensures reliable UI diagnostics rendering and clear state boundaries.

Explicit frontmatter metadata in Streamlit pages is needed when enforcing consistent page patterns and governance across AGILAB projects. It ensures safe session-state initialization, stable widget keys, and reliable modular app surfaces.