Lucio Lelii
bb5621f559
The backend now accepts a credentialId for both the interaction simulator and the bias judge, but nothing in the UI could provide one - a credential-requiring provider chosen either way would always fail, short of coincidentally reusing a credential from elsewhere in the same execution. openLLMDescriptorSettings (the one dialog shared by both the simulator and the bias judge picker) stays as it is, tests included. A new openLLMDescriptorSettingsWithCredential wraps it: once a provider and model are chosen, if LlmProviderService.listCapabilities() says that provider requiresCredential, a second dialog lists the user's saved credentials for it (ExecutionVaultCredentialsService.listForProvider). Two separate modals rather than one field folded into the first, since NodeSettingsDialogService only ever holds one dialog open at a time - stacking a "create credential" flow inside this one was not attempted, matching the pre-existing, already documented gap that there is nowhere in the app to manage credentials outside of creating them. simulateExecution() in task-execution-viewer.ts also now surfaces a rejected simulation's error message instead of failing silently. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .vscode | ||
| docker | ||
| docs | ||
| public | ||
| src | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .postcssrc.json | ||
| CITATION.cff | ||
| Dockerfile | ||
| LICENSE | ||
| LICENSE-ADDENDUM | ||
| NOTICE | ||
| README.md | ||
| angular.json | ||
| components.json | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
README.md
HumAInFlow
This project was generated using Angular CLI version 21.0.3.
Development server
To start a local development server, run:
ng serveOnce the server is running, open your browser and navigate to
http://localhost:4200/. The application will automatically
reload whenever you modify any of the source files.
Code scaffolding
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-nameFor a complete list of available schematics (such as
components, directives, or
pipes), run:
ng generate --helpBuilding
To build the project run:
ng buildThis will compile your project and store the build artifacts in the
dist/ directory. By default, the production build optimizes
your application for performance and speed.
Running unit tests
To execute unit tests with the Vitest test runner, use the following command:
ng testRunning end-to-end tests
For end-to-end (e2e) testing, run:
ng e2eAngular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Additional Resources
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.
BUILD DOCKER IMAGE
docker buildx build –platform linux/amd64,linux/arm64 -t luciolelii/humainflow-gui:latest . –push
License
Copyright (C) 2025-2026 Lucio Lelii — ISTI-CNR.
HumAIn Flow is released under the GNU Affero General Public License v3.0 or later (LICENSE), with an additional attribution term under section 7(b) of that license (LICENSE-ADDENDUM).
In practice this means:
you may use, study, modify and redistribute it freely;
if you run a modified version as a network service, you must offer its source to the users of that service;
any work based on it must keep the attribution below, both in the source and where the interface shows its legal notices:
Based on HumAIn Flow, originally developed by Lucio Lelii (ISTI-CNR) — https://github.com/luciolelii/humanaiFlow-angular
If you use HumAIn Flow in academic work, please cite it — see CITATION.cff.