9 Commits

Author	SHA1	Message	Date
emily	6b3724b765	edited the way api keys are handled. ... Since API keys are now loaded from the auth server, this means that there is a delay between starting the software, loading the keys, and loading all the module files. Due to nodejs running Async, the modules are being loaded BEFORE the api keys have been returned from the auth server. So now the api keys are being set inside the module every time the module is being called. This has absolutely no impact on performance, or security, plus, this was the easiest solution, especially as it required no big changes to the rest of the code	2026-01-14 03:01:30 +01:00
emily	b511b75db7	did some cli output cleanup, and fixed the test pipeline aswell as added a few tests	2025-12-16 18:15:40 +01:00
MikeHughes-BIN	04b2457ca3	Changes to the LLMs to return a Promise (outp path) and main now calls the export process	2025-12-15 17:58:03 +01:00
MikeHughes-BIN	ec57411992	Refactor document generation to output HTML format and update system instructions for clarity	2025-12-15 13:53:14 +01:00
MikeHughes-BIN	53508b175a	changed Display name	2025-12-11 13:27:00 +01:00
MikeHughes-BIN	3af038d195	Multiple AI models implemented - chatgpt, llama	2025-12-11 12:41:11 +01:00
MikeHughes-BIN	425e24853e	Similar to the Gemini LLM we now have a ChatGPT REST call. The API Key is still missing	2025-12-04 10:58:50 +01:00
emily	474e587ff2	Added functionality to group modules for frontend	2025-11-24 12:53:05 +01:00
MikeHughes-BIN	a1d804f463	Test created and changes to gemini.js file	2025-11-18 19:16:51 +01:00