agilab streamlit pages

Other Community

Skill notes

Apps-Pages Versus Apps Boundary

Treat apps-pages as app-agnostic analysis sidecars by default. A page should inspect artifacts, manifests, metrics, or settings from the selected active app; it should not own the domain workflow. Before promoting a Streamlit surface as an apps-page, check whether it generates its own dataset, trains a model, runs an optimizer, owns evidence

App Args Forms And Sidebar Controls

Custom app_args_form.py views are app UI, not apps-pages. Use them when an app needs persisted execution fields in ORCHESTRATE. For compact app-specific controls, use agi_env.streamlit_args.render_form with an explicit container such as st.sidebar: render_form(defaults_model, container=st.sidebar).

Session State Rules (Avoid Common Crashes)

Never assign st.session_state["k"] = … after a widget with key="k" was created. Prefer st.session_state.setdefault("k", default) before the widget. Or use widget return values and compute derived state separately. Do not both pre-seed st.session_state[key] and pass a widget default/value/index for the same keyed widget. Pick one source of initialization:

Initialize defaults with setdefault at the top of the page. Render widgets. Read values from widgets, compute derived state, store under different keys.

Project-Scoped State Models

If a page can switch between projects/apps in one Streamlit session, any persisted widget state that belongs to a specific project must use project-scoped keys. Prefer patterns like f"cluster_pool__{app_name}", not "cluster_pool". Apply the same rule to toggles, text inputs, password/auth fields, scheduler/worker fields, and similar per-project controls. Keep one clear source of truth for persisted settings.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ThalesGroup · BSD-3-Clause (see repo LICENSE)
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview agilab-streamlit-pages.preview
# Action Results and Runtime Logs

- Do not classify a page action as failed only because stderr is non-empty.
- Treat action success/failure as a typed result contract first:
  - subprocess return code or raised exception
  - `ActionResult.status`
  - explicit fatal markers in logs such as tracebacks, non-zero exit status,
- Keep log classifiers narrow. Avoid broad predicates such as `"failed" in line`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.