Change MXtoAI usages to MXGo

Author: satwikkansal

.coveragerc

@@ -1,12 +1,12 @@
 [run]
-source = mxtoai
+source = mxgo
 omit =
     */tests/*
     */test_*
-    mxtoai/db/alembic/env.py
-    mxtoai/db/alembic/versions/*
-    mxtoai/scheduler_runner.py
-    mxtoai/scripts/run_*.py
+    mxgo/db/alembic/env.py
+    mxgo/db/alembic/versions/*
+    mxgo/scheduler_runner.py
+    mxgo/scripts/run_*.py
     */migrations/*
     */__pycache__/*
     */.*

.env.example

@@ -1,5 +1,5 @@
 # =============================================================================
-# MXTOAI Environment Configuration
+# MXGo Environment Configuration
 # =============================================================================
 # Copy this file to .env and configure your values
 # See README.md and DOCKER_SETUP.md for detailed setup instructions
@@ -40,14 +40,14 @@ HF_TOKEN=your_huggingface_token_here
 # PostgreSQL Database (required)
 DB_HOST=postgres
 DB_PORT=5432
-DB_NAME=mxtoai
-DB_USER=mxtoai
+DB_NAME=mxgo
+DB_USER=mxgo
 DB_PASSWORD=your_secure_db_password
 
 # RabbitMQ Message Queue (required)
 RABBITMQ_HOST=rabbitmq
 RABBITMQ_PORT=5672
-RABBITMQ_USER=mxtoai_user
+RABBITMQ_USER=mxgo_user
 RABBITMQ_PASSWORD=your_rabbitmq_password
 RABBITMQ_VHOST=/
 RABBITMQ_HEARTBEAT=60
@@ -131,17 +131,17 @@ SCHEDULER_API_TIMEOUT=300
 # =============================================================================
 # Model Context Protocol configuration
 
-MXTOAI_ENABLE_MCP=true
-MXTOAI_MCP_CONFIG_PATH=mcp.toml
-MXTOAI_MCP_TIMEOUT=30
+MXGO_ENABLE_MCP=true
+MXGO_MCP_CONFIG_PATH=mcp.toml
+MXGO_MCP_TIMEOUT=30
 
 # =============================================================================
 # 🌐 FRONTEND & EXTERNAL URLS (Optional)
 # =============================================================================
 # Frontend and external service URLs
 
-WHITELIST_SIGNUP_URL=https://mxtoai.com/whitelist
-FRONTEND_URL=https://mxtoai.com/
+WHITELIST_SIGNUP_URL=https://mxgo.ai/whitelist
+FRONTEND_URL=https://mxgo.ai/
 
 # =============================================================================
 # 🧪 DEVELOPMENT & TESTING (Development Only)
@@ -173,8 +173,8 @@ FRONTEND_URL=https://mxtoai.com/
 # RABBITMQ_MANAGEMENT_PORT=15672   # RabbitMQ web UI port (default: 15672)
 
 # Service Authentication Overrides
-# DB_NAME=mxtoai                   # Database name (default: mxtoai)
-# DB_USER=mxtoai                   # Database user (default: mxtoai)
+# DB_NAME=mxgo                   # Database name (default: mxgo)
+# DB_USER=mxgo                   # Database user (default: mxgo)
 # DB_PASSWORD=your_db_password     # Database password (default: docker_changeme_123)
 # REDIS_PASSWORD=your_redis_pass   # Redis password (default: docker_redis_123)
 # RABBITMQ_USER=your_rmq_user      # RabbitMQ user (default: docker_guest)

.github/workflows/tests.yml

@@ -11,7 +11,7 @@ on:
       - '.github/actions/test.yml'
 
 concurrency:
-  group: mxtoai-tests
+  group: mxgo-tests
   cancel-in-progress: false
 
 jobs:
@@ -90,7 +90,7 @@ jobs:
           echo "Created litellm_config.toml and set LITELLM_CONFIG_PATH"
 
       - name: Run tests
-        run: poetry run pytest -v --timeout 180 --cov-report=term-missing:skip-covered --cov-report=html:htmlcov --cov=mxtoai --log-cli-level=INFO --pytest-durations-min=5
+        run: poetry run pytest -v --timeout 180 --cov-report=term-missing:skip-covered --cov-report=html:htmlcov --cov=mxgo --log-cli-level=INFO --pytest-durations-min=5
 
       - name: Upload pytest report
         uses: actions/upload-artifact@v4

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to MXtoAI
+# Contributing to MXGo
 
-Thank you for your interest in contributing to mxtoai, an intelligent email assistant that processes emails automatically using AI.
+Thank you for your interest in contributing to mxgo, an intelligent email assistant that processes emails automatically using AI.
 
 ## Setting up the project
 

DOCKER_SETUP.md

@@ -1,8 +1,8 @@
 # Docker Setup Guide
 
-This guide will help you set up MXTOAI using Docker for easy self-hosting.
+This guide will help you set up MXGo using Docker for easy self-hosting.
 
-MXTOAI uses a simplified Docker architecture with health checks and dependency management built into docker-compose.yml.
+MXGo uses a simplified Docker architecture with health checks and dependency management built into docker-compose.yml.
 
 ## Prerequisites
 
@@ -17,7 +17,7 @@ MXTOAI uses a simplified Docker architecture with health checks and dependency m
 ```bash
 # Clone the repository
 git clone <your-repo-url>
-cd mxtoai
+cd mxgo
 
 # Run the setup script
 chmod +x scripts/setup-local.sh
@@ -156,7 +156,7 @@ docker-compose logs -f api_server
 ```bash
 # Access running container
 docker exec -it api_server bash
-docker exec -it postgres psql -U mxtoai -d mxtoai
+docker exec -it postgres psql -U mxgo -d mxgo
 
 # Check service status
 docker-compose ps

ENV_VARIABLES.md

@@ -1,6 +1,6 @@
 # 🔧 Environment Variables Reference
 
-This document provides a comprehensive guide to all environment variables used in MXTOAI.
+This document provides a comprehensive guide to all environment variables used in MXGo .
 
 ## 📋 Quick Setup Checklist
 
@@ -40,8 +40,8 @@ For a basic working installation, you need:
 |----------|----------|---------|-------------|
 | `DB_HOST` | **Yes** | `postgres` | Database host |
 | `DB_PORT` | No | `5432` | Database port |
-| `DB_NAME` | **Yes** | `mxtoai` | Database name |
-| `DB_USER` | **Yes** | `mxtoai` | Database username |
+| `DB_NAME` | **Yes** | `mxgo` | Database name |
+| `DB_USER` | **Yes** | `mxgo` | Database username |
 | `DB_PASSWORD` | **Yes** | - | Database password |
 
 #### Redis Cache
@@ -116,9 +116,9 @@ For a basic working installation, you need:
 
 | Variable | Required | Default | Description |
 |----------|----------|---------|-------------|
-| `MXTOAI_ENABLE_MCP` | No | `true` | Enable Model Context Protocol tools |
-| `MXTOAI_MCP_CONFIG_PATH` | No | `mcp.toml` | Path to MCP configuration |
-| `MXTOAI_MCP_TIMEOUT` | No | `30` | MCP connection timeout in seconds |
+| `MXGO_ENABLE_MCP` | No | `true` | Enable Model Context Protocol tools |
+| `MXGO_MCP_CONFIG_PATH` | No | `mcp.toml` | Path to MCP configuration |
+| `MXGO_MCP_TIMEOUT` | No | `30` | MCP connection timeout in seconds |
 
 ### 🌐 **Frontend & External URLs**
 
@@ -135,8 +135,8 @@ When using Docker Compose, these services have built-in defaults:
 ```yaml
 # PostgreSQL
 DB_HOST=postgres
-DB_NAME=mxtoai
-DB_USER=mxtoai
+DB_NAME=mxgo
+DB_USER=mxgo
 DB_PASSWORD=docker_changeme_123
 
 # Redis

README.md

@@ -1,15 +1,15 @@
-# 🤖 MXtoAI - Automate any email workflow with AI
+# 🤖 MXGo - Automate any email workflow with AI
 
-> MXtoAI processes emails with advanced AI, handles attachments, and generates smart responses - all running on your own infrastructure.
+> MXGo processes emails with advanced AI, handles attachments, and generates smart responses - all running on your own infrastructure.
 
 [![Docker](https://img.shields.io/badge/Docker-Ready-blue?logo=docker)](https://www.docker.com/)
 [![License](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
 [![Self-Hosted](https://img.shields.io/badge/Self--Hosted-✓-brightgreen)]()
 
 
-## 🎯 What is MXtoAI?
+## 🎯 What is MXGo?
 
-MXtoAI is a powerful, self-hostable email processing system that acts as your intelligent email workflow assistant:
+MXGo is a powerful, self-hostable email processing system that acts as your intelligent email workflow assistant:
 
 ### ✨ **Core Features**
 
@@ -25,7 +25,7 @@ MXtoAI is a powerful, self-hostable email processing system that acts as your in
 - **🔒 Privacy First**: Runs entirely on your infrastructure
 - **🎨 Rich Formatting**: HTML and plain text responses with professional styling
 
-## 🚀 Self-host MXtoAI
+## 🚀 Self-host MXGo
 
 ### Prerequisites
 - [Docker Desktop](https://www.docker.com/products/docker-desktop) installed and running
@@ -36,8 +36,8 @@ MXtoAI is a powerful, self-hostable email processing system that acts as your in
 
 ```bash
 # Clone and start
-git clone https://github.com/mxtoai/mxtoai-core.git
-cd mxtoai
+git clone https://github.com/mxgo/mxgo-core.git
+cd mxgo
 
 # Automated setup and start
 ./scripts/setup-local.sh && ./scripts/start-local.sh
@@ -101,7 +101,7 @@ The system processes emails asynchronously and can send responses via your confi
 
 ### Environment Variables
 
-MXtoAI uses a clean, organized environment configuration system:
+MXGo uses a clean, organized environment configuration system:
 
 #### 🚀 **Quick Setup**
 1. **Copy the template**: `cp .env.example .env`
@@ -233,22 +233,22 @@ cp .env.example .env
 # Edit .env with local service settings
 
 # Run database migrations
-cd mxtoai/db
+cd mxgo/db
 poetry run alembic upgrade head
 cd ../..
 
 # Start services (3 separate terminals)
 poetry run python run_api.py                           # API Server
-poetry run dramatiq mxtoai.tasks --watch ./            # Worker
-poetry run python -m mxtoai.scheduler_runner          # Scheduler
+poetry run dramatiq mxgo.tasks --watch ./            # Worker
+poetry run python -m mxgo.scheduler_runner          # Scheduler
 ```
 
 ## 📁 Repository Structure
 
 ```mermaid
 graph TD
-    A["MXtoAI Repository"] --> B["docker/"]
-    A --> C["mxtoai/"]
+    A["MXGo Repository"] --> B["docker/"]
+    A --> C["mxgo/"]
     A --> D["scripts/"]
     A --> E["tests/"]
     A --> F["docusaurus-site/"]
@@ -290,7 +290,7 @@ graph TD
 | Directory | Purpose | Key Files |
 |-----------|---------|-----------|
 | `🐳 docker/` | Container configurations | Dockerfiles, init scripts |
-| `🤖 mxtoai/` | Core application code | agents, tools, database models |
+| `🤖 mxgo/` | Core application code | agents, tools, database models |
 | `📋 scripts/` | Setup & deployment | setup-local.sh, start-local.sh |
 | `🧪 tests/` | Test suite | Unit tests, load tests |
 | `📖 docusaurus-site/` | Documentation website | Docs, guides, examples |
@@ -308,7 +308,7 @@ graph TD
 
 ### Multiple AI Model Support
 
-MXtoAI supports load balancing across multiple AI providers:
+MXGo supports load balancing across multiple AI providers:
 
 - OpenAI GPT models
 - Azure OpenAI
@@ -381,14 +381,14 @@ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
 ## 🌟 Support
 
 - **📖 Documentation**: [DOCKER_SETUP.md](DOCKER_SETUP.md)
-- **🐛 Issues**: [GitHub Issues](https://github.com/your-org/mxtoai/issues)
-- **💬 Discussions**: [GitHub Discussions](https://github.com/your-org/mxtoai/discussions)
+- **🐛 Issues**: [GitHub Issues](https://github.com/your-org/mxgo/issues)
+- **💬 Discussions**: [GitHub Discussions](https://github.com/your-org/mxgo/discussions)
 
 ---
 
 <div align="center">
 
-**⭐ Star this repo if MXtoAI helps you!**
+**⭐ Star this repo if MXGo helps you!**
 
 Made with ❤️ for the open source community
 

add-new-tool.md

@@ -1,10 +1,10 @@
-# Guide to Adding New Tools in MxToAi
+# Guide to Adding New Tools in MXGo
 
-This guide outlines the process for adding new tools to the MxToAi email assistant. It covers architecture considerations, database integration, testing approaches, and best practices based on real implementation experience.
+This guide outlines the process for adding new tools to the MXGo email assistant. It covers architecture considerations, database integration, testing approaches, and best practices based on real implementation experience.
 
 ## 1. Tool Architecture Overview
 
-MxToAi uses the `smolagents` framework for tool implementation, allowing the AI agent to access specialized functionality. Each tool should:
+MXGo uses the `smolagents` framework for tool implementation, allowing the AI agent to access specialized functionality. Each tool should:
 
 - Have a clear, single responsibility
 - Be properly integrated with the agent's capabilities
@@ -54,16 +54,17 @@ For tools that interact with the database:
 - Use the `DbConnection` class for database access
 
 ```python
-from mxtoai.db import init_db_connection
+from mxgo.db import init_db_connection
 
 # Initialize at module level for reuse
 db_connection = init_db_connection()
 
+
 # In your tool:
 def forward(self, ...):
     with db_connection.get_session() as session:
-        # Perform database operations
-        # ...
+# Perform database operations
+# ...
 ```
 
 ### 2.2 Handling Data Models
@@ -78,7 +79,7 @@ When working with database models:
 # Example of a hybrid approach
 try:
     # Try ORM approach first (good for testing)
-    from mxtoai.models import YourModel
+    from mxgo.models import YourModel
 
     model = YourModel(...)
     session.add(model)
@@ -120,10 +121,11 @@ class ToolInput(BaseModel):
 Implement robust error handling:
 
 ```python
-from mxtoai.utils import get_logger
+from mxgo.utils import get_logger
 
 logger = get_logger(__name__)
 
+
 def forward(self, ...):
     try:
         # Implementation
@@ -222,7 +224,7 @@ Ensure your tool integrates properly with the email agent:
 
 ### 7.1 Code Organization
 
-- Keep tool implementation in its own module in the `mxtoai/tools/` directory
+- Keep tool implementation in its own module in the `mxgo/tools/` directory
 - Use clear, descriptive names for classes and methods
 - Document public APIs thoroughly with docstrings
 
@@ -250,7 +252,7 @@ Ensure your tool integrates properly with the email agent:
 
 Here's a simplified version of adding a scheduled tasks tool:
 
-1. **Create the tool file** at `mxtoai/tools/scheduled_tasks_tool.py`
+1. **Create the tool file** at `mxgo/tools/scheduled_tasks_tool.py`
 2. **Implement the tool class** with necessary functionality:
    - Input validation
    - Database operations
@@ -273,7 +275,7 @@ Here's a simplified version of adding a scheduled tasks tool:
 
 ## 10. Conclusion
 
-Adding new tools to MxToAi requires careful planning, implementation, and testing. Following these guidelines will help ensure that your tool integrates smoothly with the existing system and provides reliable functionality.
+Adding new tools to MXGo requires careful planning, implementation, and testing. Following these guidelines will help ensure that your tool integrates smoothly with the existing system and provides reliable functionality.
 
 Remember to:
 - Keep the tool focused on a specific task

docker-compose.yml

@@ -3,8 +3,8 @@ services:
     image: postgres:16-alpine
     container_name: postgres
     environment:
-      POSTGRES_DB: ${DB_NAME:-mxtoai}
-      POSTGRES_USER: ${DB_USER:-mxtoai}
+      POSTGRES_DB: ${DB_NAME:-mxgo}
+      POSTGRES_USER: ${DB_USER:-mxgo}
       POSTGRES_PASSWORD: ${DB_PASSWORD:-docker_changeme_123}
     ports:
       - "${DB_PORT:-5432}:5432"
@@ -13,7 +13,7 @@ services:
       - ./docker/init-db.sh:/docker-entrypoint-initdb.d/init-db.sh
     restart: unless-stopped
     healthcheck:
-      test: ["CMD-SHELL", "pg_isready -U ${DB_USER:-mxtoai} -d ${DB_NAME:-mxtoai}"]
+      test: ["CMD-SHELL", "pg_isready -U ${DB_USER:-mxgo} -d ${DB_NAME:-mxgo}"]
       interval: 10s
       timeout: 5s
       retries: 5
@@ -125,4 +125,4 @@ volumes:
 
 networks:
   default:
-    name: mxtoai_network
+    name: mxgo_network