About AGILab

This page maps the built-in AGILab web pages and shows how they fit together.

The main web interface exposes one navigation surface for:

  • Core pages (Project, Orchestrate, Pipeline, Analysis), and

  • Page bundles (optional dashboards launched from Analysis).

How pages are presented

  • Core pages and page bundles both appear as “pages” in the UI, with a consistent layout and navigation.

  • The key difference is runtime: core pages run inside the main AGILab web interface, while page bundles run in a sidecar web process and are embedded back into the UI.

Core pages

  • PROJECT — PROJECT: inspect and modify project sources and settings.

  • ORCHESTRATE — ORCHESTRATE: install workers, generate distributions, and run pipelines.

  • PIPELINE — PIPELINE: iterate in lab_steps.toml and run snippets against exported data.

  • ANALYSIS — ANALYSIS: discover, configure, and launch page bundles.

Core page tour

Every built-in page now exposes direct documentation access from the sidebar, so you can reopen the relevant guide without navigating back to the landing page first.

Overview screenshot montage of the PROJECT, ORCHESTRATE, PIPELINE, and ANALYSIS Streamlit pages.

A compact visual tour of the four built-in Streamlit pages that structure the AGILAB workflow.

Page bundles (apps-pages)

Page bundles are optional dashboards stored under ${AGILAB_PAGES_ABS} (default: src/agilab/apps-pages). They are enabled per project via [pages].view_module in app_settings.toml.

First-time navigation

Use this as a page map, not as the newcomer proof path:

  1. Open PROJECT (Project) to inspect or select the target project.

  2. Use ORCHESTRATE (Orchestrate) to install dependencies, build distributions, configure distributed workers when needed, and generate a run snippet.

  3. Move to PIPELINE (Pipeline) to import or iterate that generated step in lab_steps.toml.

  4. Open ANALYSIS (Analysis) to configure and launch page bundles for deeper views.

See also