AGILAB BSD license is an MLOps toolchain for engineering, powered by the OpenAI API, local GPT-OSS, local Mistral-Instruct, and MLflow. It helps you move from notebooks to production with CLI tooling, optional IDE run configurations, and packaged workers. IDE integrations remain available for teams that rely on them, but they are no longer required.

Docs publishing

• The static site is committed under docs/html and deployed by GitHub Pages directly (no Sphinx build in CI).
• Preferred path: run docs/gen_docs.sh. It builds Sphinx if a config exists; otherwise it syncs src/agilab/resources/help/ into docs/html and ensures an index.html is present.
• CI will deploy the committed docs/html; if it’s empty, the workflow falls back to copying from src/agilab/resources/help/. See documentation.

See also: CHANGELOG.md for recent changes.

• Demo users launch uvx agilab; no repository checkout or IDE is required.
• End users create a uv workspace and launch uv run agilab ; no repository checkout or IDE is required.
• Developers clone this repository and launch install.sh; Pycharm IDE is strongly recommended. Never run uvx inside the cloned checkout—use the uv run … commands or generated wrappers. see below for more details

Quick run (no setup):

uv tool upgrade agilab
uvx -p 3.13 agilab

Note This uvx invocation is meant for demos or smoke tests. Any changes you make inside the cached package will be overwritten on the next run. For development, clone the repository or use a virtual environment. Within a local checkout, stick to uv run …; invoking uvx there replaces your workspace with the published wheel.

• Before launching, quickly inspect the newest installer log for errors.
• Log locations:
  • Windows: C:\Users\<you>\log\install_logs
  • macOS/Linux: $HOME/log/install_logs
• PowerShell (Windows):
  • ($d = "$HOME\log\install_logs"); $f = Get-ChildItem -LiteralPath $d -File | Sort-Object LastWriteTime -Descending | Select-Object -First 1; if ($f) { Write-Host "Log:" $f.FullName; Select-String -LiteralPath $f.FullName -Pattern '(?i)(error|exception|traceback|failed|fatal|denied|missing|not found)' | Select-Object -Last 25 | ForEach-Object { $_.Line } } else { Write-Host "No logs found." }
• Bash (macOS/Linux):
  • dir="$HOME/log/install_logs"; f=$(ls -1t "$dir"/*.log 2>/dev/null | head -1); [ -n "$f" ] && echo "Log: $f" && grep -Eai "error|exception|traceback|failed|fatal|denied|missing|not found" "$f" | tail -n 25 || echo "No logs found."

Prefer to stay offline? Start a local GPT-OSS responses server and switch the “Assistant engine” selector (in the Experiment page sidebar) to GPT-OSS (local):

python -m pip install "agilab[offline]"
python -m pip install transformers torch accelerate  # installs the local backends used by GPT-OSS
python -m gpt_oss.responses_api.serve --inference-backend transformers --checkpoint gpt2 --port 8000

Update the endpoint field if you expose the server on a different port. The sidebar now lets you pick the GPT-OSS backend (stub, transformers, ollama, …), checkpoint, and extra launch flags; the app persists the values in env.envars. The default stub backend is only a connectivity check and returns canned responses—switch to transformers (or another real backend) to receive model-generated code. When GPT-OSS is installed and the endpoint targets localhost, the sidebar automatically launches a local server the first time you switch to GPT-OSS (local) using the configured backend.

Managed workspace (project folder):

mkdir agi-space && cd agi-space
uv init --bare --no-workspace
uv add agilab
uv tool upgrade agilab
uv run agilab

Every IDE run configuration now has a matching shell script under tools/run_configs/. Regenerate them at any time with:

python3 tools/generate_runconfig_scripts.py

The generator groups scripts under tools/run_configs/<group>/ (agilab, apps, components). Each wrapper exports the same environment variables, switches to the correct working directory, and executes the underlying uv command—no IDE required.

git clone https://github.com/ThalesGroup/agilab
cd agilab
./install.sh --apps-repository path/to/your/apps/repository --apps-install --apps-test

git clone https://github.com/ThalesGroup/agilab
cd agilab
# Built-in apps/pages only
powershell.exe -ExecutionPolicy Bypass -File .\install.ps1 -InstallApps

# Or include an external apps repository that contains 'apps' and/or 'apps-pages'
# The repository root must contain either '<repo>\\apps-pages' or '<repo>\\src\\agilab\\apps-pages'.
# Use quotes and backslashes on Windows.
powershell.exe -ExecutionPolicy Bypass -File .\install.ps1 -InstallApps -TestApps -AppsRepository "C:\\path\\to\\your-apps-repo"

• Built-in pages live in this repo at src/agilab/apps-pages and are installed by default.
• To add pages/apps from another repository, pass -AppsRepository "C:\path\to\repo".
  • The installer probes <repo>\apps-pages and <repo>\src\agilab\apps-pages for pages.
  • Similarly for apps: <repo>\apps and <repo>\src\agilab\apps (expects *_project folders).
• Merging rules:
  • Destination bases are src/agilab/apps and src/agilab/apps-pages.
  • If a destination folder already exists and is not a link, it is left as-is (built-in takes precedence).
  • If missing, a link/junction is created to the repository version.
• Environment controls (optional):
  • Limit built-in pages: BUILTIN_PAGES_OVERRIDE="page1,page2" or BUILTIN_PAGES="page1 page2".
  • Limit built-in apps: BUILTIN_APPS_OVERRIDE="app_project1,app_project2" or BUILTIN_APPS.
• Troubleshooting:
  • If you pass -AppsRepository and the repo has no apps-pages, the installer errors out. Omit -AppsRepository to use only built-ins.
  • Use quotes and backslashes in PowerShell paths; e.g., "C:\\Users\\me\\repo".

cd agilab/src/agilab
uv run agilab

• Portions of src/agilab/apps-pages/view_barycentric/src/view_barycentric/view_barycentric.py are adapted from Jean-Luc Parouty’s “barviz / barviz-mod” project (MIT License). See NOTICE and LICENSES/LICENSE-MIT-barviz-mod for details.

• AgiEnv is a singleton. Use instance attributes (env.apps_dir, env.logger, etc.). Class attribute reads (e.g., AgiEnv.apps_dir) proxy to the singleton when initialised; methods/properties are not shadowed. A few helpers are pre‑init safe (AgiEnv.set_env_var, AgiEnv.read_agilab_path, AgiEnv._build_env, AgiEnv.log_info).

• Environment flags (replaces legacy install_type):

  • env.is_source_env: true when running from a source checkout.
  • env.is_worker_env: true in worker-only contexts (e.g., wenv/*_worker).
  • env.is_local_worker: helper flag for home‑scoped worker layouts.

• App constructors (templates + flight_project) ignore unknown kwargs when constructing their Pydantic Args models. This preserves strict validation while making constructors resilient to incidental extras. Configure verbosity via AgiEnv(verbose=…) or logging, not via app Args.