ai-spel/ai-spel-frontend
1
0
Fork 0
Code Issues Pull Requests Actions 14 Packages Projects Releases Wiki Activity

Pause browser local AI behind disabled feature flag
Build and publish frontend / publish (push) Failing after 2s
Details

Browse Source
This commit is contained in:
Ein Anderssono
2026-10-19 13:08:45 +02:00
parent 1444f202c6
commit 3a9d02bc64
6 changed files with 63 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3
View File
@@ -39,3 +39,6 @@ CI needs repository Action secrets named `HARBOR_USERNAME` and `HARBOR_PASSWORD`
The first Argo Application is described in `deploy/argocd/application.yaml`. The backend ingress routes `/api`, `/version`, and health checks to Rust while serving the static client at `/`. Both services share the same origin so the session cookie remains same-origin.
Builds, checks, and runtime verification happen in the pipeline and Kubernetes. Do not run the app, tests, container images, or binaries locally.
# Browser-local AI status
Gemma/Wllama assistance is currently paused. `FEATURE_FLAGS.localAI` in `index.html` is `false`; while disabled, the client does not load the adapter, download model/runtime assets, run local inference, or send local hints. Re-enabling it requires an explicit code change and the normal frontend release pipeline. This does not affect the regular Rust-backed dialogue flow.