mirror of
https://github.com/multica-ai/multica.git
synced 2026-08-03 19:20:07 +02:00
7a66de9f23
Chat auto-titling and chat follow-up suggestions are gated on the server-side LLM layer, which reads MULTICA_LLM_API_KEY / MULTICA_LLM_BASE_URL through os.Getenv. The self-host compose file enumerates backend environment explicitly and has no env_file, and those three vars were not in the list — so setting them in .env did nothing, the container never saw them, and the layer was off on every compose deployment regardless of configuration. .env.example documents them, which made it look configurable. That was survivable while quick actions were generated by the daemon's own provider pass, which needed no server key. MUL-5573 moved generation server- side and removed the daemon path, so on those deployments the feature stopped appearing entirely rather than degrading. Adds the passthrough, and one startup line reporting whether the layer is enabled. Every consumer degrades silently by design, so without that line an unset key is indistinguishable from a broken feature — which is exactly how this surfaced. Helm already supports it through the operator-managed Secret; values.yaml now says so instead of leaving it undocumented. Co-authored-by: multica-agent <github@multica.ai>