Local AI Architecture Deep Dive / Part 2
The Backend Bridge: Connecting Web to Local Intelligence
Discover how the Signal Share Super Suite bridges the gap between a standard web browser and powerful local AI inference engines like LM Studio and Ollama.
1. Node.js Orchestration
While the Signal Share frontend runs in your browser, it cannot directly control your operating system or talk to local servers without bypassing security restrictions. To solve this, we use a Local Bridge Server written in Node.js.
2. The LLM API Pipeline
The backend module chatbot.js handles the intelligence fallback. It attempts to connect to local servers in a prioritized sequence:
- LM Studio (Port 1234): The primary high-performance engine for Transformers.
- Ollama (Port 11434): A robust fallback for lightweight Llama or Mistral models.
- Heuristic Fallback: A safety net that provides basic "Standby" responses if no AI server is detected.
3. The PowerShell Media Bridge
One of the most powerful features of the Signal Share AI is its ability to control your hardware. We use PowerShell scripts triggered by the Node.js server to interact with the Windows Runtime (WinRT) media controls.
This allows the AI to perform physical actions on your computer that a normal website simply cannot do, effectively turning the Companion into a system-level assistant.