Merge branch 'dev' into fix/open-memory-fork

Author: AnkushMalaker

.github/workflows/robot-tests.yml

@@ -110,10 +110,6 @@ jobs:
         echo "LLM_PROVIDER: $LLM_PROVIDER"
         echo "TRANSCRIPTION_PROVIDER: $TRANSCRIPTION_PROVIDER"
 
-        # Create memory_config.yaml from template (file is gitignored)
-        echo "Creating memory_config.yaml from template..."
-        cp memory_config.yaml.template memory_config.yaml
-
         # Clean any existing test containers for fresh start
         echo "Cleaning up any existing test containers..."
         docker compose -f docker-compose-test.yml down -v || true

Docs/getting-started.md

@@ -342,7 +342,7 @@ curl -X POST "http://localhost:8000/api/process-audio-files" \
 
 **Implementation**: 
 - **Memory System**: `src/advanced_omi_backend/memory/memory_service.py` + `src/advanced_omi_backend/controllers/memory_controller.py`
-- **Configuration**: `memory_config.yaml` + `src/advanced_omi_backend/memory_config_loader.py`
+- **Configuration**: memory settings in `config.yml` (memory section)
 
 ### Authentication & Security
 - **Email Authentication**: Login with email and password
@@ -541,10 +541,10 @@ OPENMEMORY_MCP_URL=http://host.docker.internal:8765
 
 > 🎯 **New to memory configuration?** Read our [Memory Configuration Guide](./memory-configuration-guide.md) for a step-by-step setup guide with examples.
 
-The system uses **centralized configuration** via `memory_config.yaml` for all memory extraction settings. All hardcoded values have been removed from the code to ensure consistent, configurable behavior.
+The system uses **centralized configuration** via `config.yml` for all models (LLM, embeddings, vector store) and memory extraction settings.
 
 ### Configuration File Location
-- **Path**: `backends/advanced-backend/memory_config.yaml`
+- **Path**: repository `config.yml` (override with `CONFIG_FILE` env var)
 - **Hot-reload**: Changes are applied on next processing cycle (no restart required)
 - **Fallback**: If file is missing, system uses safe defaults with environment variables
 
@@ -613,7 +613,7 @@ If you experience JSON parsing errors in fact extraction:
 
 2. **Enable fact extraction** with reliable JSON output:
    ```yaml
-   # In memory_config.yaml
+   # In config.yml (memory section)
    fact_extraction:
      enabled: true  # Safe to enable with GPT-4o
    ```
@@ -727,5 +727,5 @@ curl -H "Authorization: Bearer $ADMIN_TOKEN" \
 - **Connect audio clients** using the WebSocket API
 - **Explore the dashboard** to manage conversations and users
 - **Review the user data architecture** for understanding data organization
-- **Customize memory extraction** by editing `memory_config.yaml`
-- **Monitor processing performance** using debug API endpoints
+- **Customize memory extraction** by editing the `memory` section in `config.yml`
+- **Monitor processing performance** using debug API endpoints

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Chronicle AI Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -4,7 +4,7 @@ Self-hostable AI system that captures audio/video data from OMI devices and othe
 
 ## Quick Start → [Get Started](quickstart.md)
 
-Clone, run setup wizard, start services, access at http://localhost:5173
+Run setup wizard, start services, access at http://localhost:5173
 
 ## Screenshots
 

backends/advanced/.env.template

@@ -82,7 +82,7 @@ SPEECH_INACTIVITY_THRESHOLD_SECONDS=60  # Close conversation after N seconds of
 # When enabled, only creates conversations when enrolled speakers are detected
 # Requires speaker recognition service to be running and speakers to be enrolled
 # Set to "true" to enable, "false" or omit to disable
-RECORD_ONLY_ENROLLED_SPEAKERS=true
+RECORD_ONLY_ENROLLED_SPEAKERS=false
 
 # ========================================
 # DATABASE CONFIGURATION

backends/advanced/Dockerfile

@@ -35,7 +35,7 @@ COPY . .
 
 # Copy configuration files if they exist, otherwise they will be created from templates at runtime
 # The files are expected to exist, but we handle the case where they don't gracefully
-COPY memory_config.yaml* ./
+
 COPY diarization_config.json* ./
 
 

backends/advanced/Dockerfile.k8s

@@ -34,7 +34,7 @@ RUN uv sync --extra deepgram
 COPY . .
 
 # Copy memory config (created by init.sh from template)
-COPY memory_config.yaml ./
+
 
 # Copy and make K8s startup scripts executable
 COPY start-k8s.sh start-workers.sh ./

backends/advanced/Docs/README.md

@@ -13,7 +13,7 @@ Welcome to chronicle! This guide provides the optimal reading sequence to unders
 - What the system does (voice → memories)
 - Key features and capabilities
 - Basic setup and configuration
-- **Code References**: `src/advanced_omi_backend/main.py`, `memory_config.yaml`, `docker-compose.yml`
+- **Code References**: `src/advanced_omi_backend/main.py`, `config.yml`, `docker-compose.yml`
 
 ### 2. **[System Architecture](./architecture.md)** 
 **Read second** - Complete technical architecture with diagrams
@@ -70,12 +70,12 @@ Welcome to chronicle! This guide provides the optimal reading sequence to unders
 
 ## 🔍 **Configuration & Customization**
 
-### 6. **Configuration File** → `../memory_config.yaml`
+### 6. **Configuration File** → `../config.yml`
 **Central configuration for all extraction**
 - Memory extraction settings and prompts
 - Quality control and debug settings
 - **Code References**:
-  - `src/advanced_omi_backend/memory_config_loader.py` (config loading)
+  - `src/advanced_omi_backend/model_registry.py` (config loading)
   - `src/advanced_omi_backend/memory/memory_service.py` (config usage)
 
 ---
@@ -86,11 +86,11 @@ Welcome to chronicle! This guide provides the optimal reading sequence to unders
 1. [quickstart.md](./quickstart.md) - System overview
 2. [architecture.md](./architecture.md) - Technical architecture  
 3. `src/advanced_omi_backend/main.py` - Core imports and setup
-4. `memory_config.yaml` - Configuration overview
+4. `config.yml` - Configuration overview
 
 ### **"I want to work on memory extraction"**
 1. [memories.md](./memories.md) - Memory system details
-2. `../memory_config.yaml` - Memory configuration
+2. `../config.yml` - Models and memory configuration
 3. `src/advanced_omi_backend/memory/memory_service.py` - Implementation
 4. `src/advanced_omi_backend/controllers/memory_controller.py` - Processing triggers
 
@@ -128,9 +128,9 @@ backends/advanced-backend/
 │   ├── controllers/               # Business logic controllers
 │   ├── memory/
 │   │   └── memory_service.py      # Memory system (Mem0)
-│   └── memory_config_loader.py    # Configuration loading
+│   └── model_registry.py          # Configuration loading
 │
-├── memory_config.yaml             # 📋 Central configuration
+├── config.yml                     # 📋 Central configuration
 ├── MEMORY_DEBUG_IMPLEMENTATION.md # Debug system details
 ```
 
@@ -147,8 +147,8 @@ backends/advanced-backend/
 - **Memories**: `src/advanced_omi_backend/memory/memory_service.py` → Mem0 → Qdrant
 
 ### **Configuration**
-- **Loading**: `src/advanced_omi_backend/memory_config_loader.py`
-- **File**: `memory_config.yaml`
+- **Loading**: `src/advanced_omi_backend/model_registry.py`
+- **File**: `config.yml`
 - **Usage**: `src/advanced_omi_backend/memory/memory_service.py`
 
 ### **Authentication**
@@ -162,7 +162,7 @@ backends/advanced-backend/
 
 1. **Follow the references**: Each doc links to specific code files and line numbers
 2. **Use the debug API**: `GET /api/debug/memory/stats` shows live system status
-3. **Check configuration first**: Many behaviors are controlled by `memory_config.yaml`
+3. **Check configuration first**: Many behaviors are controlled by `config.yml`
 4. **Understand the memory pipeline**: Memories (end-of-conversation)
 5. **Test with curl**: All API endpoints have curl examples in the docs
 
@@ -175,23 +175,23 @@ backends/advanced-backend/
 1. **Set up the system**: Follow [quickstart.md](./quickstart.md) to get everything running
 2. **Test the API**: Use the curl examples in the documentation to test endpoints
 3. **Explore the debug system**: Check `GET /api/debug/memory/stats` to see live data
-4. **Modify configuration**: Edit `memory_config.yaml` to see how it affects extraction
+4. **Modify configuration**: Edit `config.yml` (memory section) to see how it affects extraction
 5. **Read the code**: Start with `src/advanced_omi_backend/main.py` and follow the references in each doc
 
 ### **Contributing Guidelines**
 
 - **Add code references**: When updating docs, include file paths and line numbers
 - **Test your changes**: Use the debug API to verify your modifications work
-- **Update configuration**: Add new settings to `memory_config.yaml` when needed
+- **Update configuration**: Add new settings to `config.yml` when needed
 - **Follow the architecture**: Keep memories in their respective services
 
 ### **Getting Help**
 
 - **Debug API**: `GET /api/debug/memory/*` endpoints show real-time system status
-- **Configuration**: Check `memory_config.yaml` for behavior controls
+- **Configuration**: Check `config.yml` for behavior controls
 - **Logs**: Check Docker logs with `docker compose logs chronicle-backend`
 - **Documentation**: Each doc file links to relevant code sections
 
 ---
 
-This documentation structure ensures you understand both the **big picture** and **implementation details** in a logical progression!
+This documentation structure ensures you understand both the **big picture** and **implementation details** in a logical progression!

backends/advanced/Docs/contribution.md

@@ -1,12 +1,12 @@
   1. Docs/quickstart.md (15 min)
   2. Docs/architecture.md (20 min)
   3. main.py - just the imports and WebSocket sections (15 min)
-  4. memory_config.yaml (10 min)
+  4. config.yml (memory section) (10 min)
 
   🔧 "I want to work on memory extraction"
 
   1. Docs/quickstart.md → Docs/memories.md
-  2. memory_config.yaml (memory_extraction section)
+  2. config.yml (memory.extraction section)
   3. main.py lines 1047-1065 (trigger)
   4. main.py lines 1163-1195 (processing)
   5. src/memory/memory_service.py
@@ -32,4 +32,4 @@
   Data Flow
 
   Audio → Transcription → Dual Processing
-                        └─ Memory Pipeline (end-of-conversation)
+                        └─ Memory Pipeline (end-of-conversation)

backends/advanced/Docs/memories.md

@@ -10,7 +10,7 @@ This document explains how to configure and customize the memory service in the
 - **Repository Layer**: `src/advanced_omi_backend/conversation_repository.py` (clean data access)
 - **Processing Manager**: `src/advanced_omi_backend/processors.py` (MemoryProcessor class)
 - **Conversation Management**: `src/advanced_omi_backend/conversation_manager.py` (lifecycle coordination)
-- **Configuration**: `memory_config.yaml` + `src/memory_config_loader.py`
+- **Configuration**: `config.yml` (memory section) + `src/model_registry.py`
 
 ## Overview
 
@@ -180,7 +180,7 @@ OPENAI_MODEL=gpt-5-mini  # Recommended for reliable JSON output
 # OPENAI_MODEL=gpt-3.5-turbo  # Budget option
 ```
 
-Or configure via `memory_config.yaml`:
+Or configure via `config.yml` (memory block):
 
 ```yaml
 memory_extraction:
@@ -674,4 +674,4 @@ The new architecture ensures proper user isolation and simplifies admin debuggin
 
 Both load all user memories and view all memories are helpful
 Both views complement each other - the debug view helps you understand how the system is working, while the clean view
-helps you understand what content is being stored.
+helps you understand what content is being stored.