codegraphcontext 0.1.23__tar.gz → 0.1.27__tar.gz

{codegraphcontext-0.1.23/src/codegraphcontext.egg-info → codegraphcontext-0.1.27}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codegraphcontext
-Version: 0.1.23
+Version: 0.1.27
 Summary: An MCP server that indexes local code into a graph database to provide context to AI assistants.
 Author-email: Shashank Shekhar Singh <shashankshekharsingh1205@gmail.com>
 License: MIT License
@@ -82,7 +82,7 @@ Dynamic: license-file
 
 
 
-A powerful **MCP server** and **CLI tool** that indexes local code into a graph database to provide context to AI assistants and developers. Use it as a standalone CLI for code analysis or connect it to your favorite AI IDE via MCP.
+A powerful **MCP server** and **CLI toolkit** that indexes local code into a graph database to provide context to AI assistants and developers. Use it as a standalone CLI for comprehensive code analysis or connect it to your favorite AI IDE via MCP for AI-powered code understanding.
 
 ### Indexing a codebase
 ![Indexing using an MCP client](https://github.com/Shashankss1205/CodeGraphContext/blob/main/images/Indexing.gif)
@@ -91,7 +91,7 @@ A powerful **MCP server** and **CLI tool** that indexes local code into a graph
 ![Using the MCP server](https://github.com/Shashankss1205/CodeGraphContext/blob/main/images/Usecase.gif)
 
 ## Project Details
-- **Version:** 0.1.23
+- **Version:** 0.1.27
 - **Authors:** Shashank Shekhar Singh <shashankshekharsingh1205@gmail.com>
 - **License:** MIT License (See [LICENSE](LICENSE) for details)
 - **Website:** [CodeGraphContext](http://codegraphcontext.vercel.app/)
@@ -103,11 +103,12 @@ A powerful **MCP server** and **CLI tool** that indexes local code into a graph
 
 -   **Code Indexing:** Analyzes code and builds a knowledge graph of its components.
 -   **Relationship Analysis:** Query for callers, callees, class hierarchies, call chains and more.
--   **Live Updates:** Watches local files for changes and automatically updates the graph.
+-   **Live File Watching:** Watch directories for changes and automatically update the graph in real-time (`cgc watch`).
 -   **Interactive Setup:** A user-friendly command-line wizard for easy setup.
--   **Dual Mode:** Works as a standalone **CLI tool** for developers and as an **MCP server** for AI agents.
+-   **Dual Mode:** Works as a standalone **CLI toolkit** for developers and as an **MCP server** for AI agents.
 -   **Multi-Language Support:** Full support for 11 programming languages.
--   **Flexible Database Backend:** Choose between Neo4j or FalkorDB Lite.
+-   **Flexible Database Backend:** FalkorDB Lite (default, inbuilt for Unix and through WSL for Windows) or Neo4j (all platforms via Docker/native).
+
 
 ## Supported Programming Languages
 
@@ -124,6 +125,7 @@ CodeGraphContext provides comprehensive parsing and analysis for the following l
 - **Rust** (`.rs`)
 - **Ruby** (`.rb`)
 - **PHP** (`.php`)
+- **Kotlin** (`.kt`) - Full support for classes, objects, companions, functions, and coroutines
 
 Each language parser extracts functions, classes, methods, parameters, inheritance relationships, function calls, and imports to build a comprehensive code graph.
 
@@ -131,27 +133,33 @@ Each language parser extracts functions, classes, methods, parameters, inheritan
 
 CodeGraphContext supports two graph database backends:
 
-### Neo4j (Default)
-- **Production-ready** and widely used graph database
-- Supports local instances (via Docker or native installation) and cloud hosting (Neo4j AuraDB)
-- Full Cypher query support for advanced graph analytics
-- Recommended for most use cases
-
-### FalkorDB Lite
+### FalkorDB Lite (Default for Unix/Linux/macOS)
 - **Lightweight** in-memory graph database
 - **No external dependencies** - runs entirely in-process
+- **Inbuilt and enabled by default** for Unix-based systems (Linux, macOS)
 - Available for **Python 3.12+** only
-- Perfect for quick testing and development
-- Automatically installed when using Python 3.12 or higher
+- Perfect for quick testing, development, and most use cases
+- Automatically installed and configured when using Python 3.12 or higher on Unix systems
+
 > ⚠️ **Windows Users:**  
 > FalkorDB Lite / redislite is **not supported on Windows**.  
-> You have two options:  
+> You have three options:  
 > 1. Run the project under **WSL (Windows Subsystem for Linux)**: [WSL Install](https://learn.microsoft.com/en-us/windows/wsl/install)  
-> 2. Skip FalkorDB and use **Neo4j** directly as your graph database.
+> 2. Use **Docker** to run the project in a containerized Linux environment  
+> 3. Use **Neo4j** directly as your graph database (see below)
 
+### Neo4j (Available for All Platforms)
+- **Production-ready** and widely used graph database
+- **Available on all operating systems**: Windows, Linux, macOS
+- Can be installed via:
+  - **Docker** (recommended, cross-platform)
+  - **WSL** (for Windows users)
+  - **Native installation** (dedicated command for each OS)
+- Supports local instances and cloud hosting (Neo4j AuraDB)
+- Full Cypher query support for advanced graph analytics
+- Recommended for Windows users and production deployments
 
-The `cgc neo4j setup` wizard helps you configure neo4j database backend while the falkordb database is
-supported inherently (enabled by default).
+The `cgc neo4j setup` wizard helps you configure the Neo4j database backend, while FalkorDB Lite is enabled by default on Unix systems with no configuration needed.
 
 ## Used By
 
@@ -184,9 +192,31 @@ If you’re using CodeGraphContext in your project, feel free to open a PR and a
 
 ## Getting Started
 
+### 📋 Understanding CodeGraphContext Modes
+
+CodeGraphContext operates in **two modes**, and you can use either or both:
+
+#### 🛠️ Mode 1: CLI Toolkit (Standalone)
+Use CodeGraphContext as a **powerful command-line toolkit** for code analysis:
+- Index and analyze codebases directly from your terminal
+- Query code relationships, find dead code, analyze complexity
+- Visualize code graphs and dependencies
+- Perfect for developers who want direct control via CLI commands
+
+#### 🤖 Mode 2: MCP Server (AI-Powered)
+Use CodeGraphContext as an **MCP server** for AI assistants:
+- Connect to AI IDEs (VS Code, Cursor, Windsurf, Claude, etc.)
+- Let AI agents query your codebase using natural language
+- Automatic code understanding and relationship analysis
+- Perfect for AI-assisted development workflows
+
+**You can use both modes!** Install once, then use CLI commands directly OR connect to your AI assistant.
+
+---
+
+### Installation (Both Modes)
+
 1.  **Install:** `pip install codegraphcontext`
-2.  **Setup:** `cgc mcp setup`
-    This command configures your IDE to work with CodeGraphContext. To configure a Neo4j database, use `cgc neo4j setup`.
 
     <details>
     <summary>⚙️ Troubleshooting: In case, command <code>cgc</code> not found</summary>
@@ -221,14 +251,56 @@ If you’re using CodeGraphContext in your project, feel free to open a PR and a
     ``` 
     </details>
 
+2.  **Database Setup (Automatic for Unix/WSL)**
     
-    **Database Configuration:**
-    *   **Local Setup (Docker Recommended):** Helps you set up a local Neo4j instance using Docker. Requires Docker and Docker Compose to be installed.
-    *   **Local Setup (Linux Binary):** For Debian-based Linux systems (like Ubuntu), `cgc neo4j setup` can automate the installation of Neo4j. Requires `sudo` privileges.
-    *   **Hosted Setup:** Allows you to connect to an existing remote Neo4j database (e.g., Neo4j AuraDB).
+    - **FalkorDB Lite (Default):** If you're on Unix/Linux/macOS/WSL with Python 3.12+, you're done! FalkorDB Lite is already configured.
+    - **Neo4j (Optional/Windows):** To use Neo4j instead, or if you're on Windows without WSL, run: `cgc neo4j setup`
+
+---
+
+### 🛠️ For CLI Toolkit Mode
+
+**Start using immediately with CLI commands:**
+
+```bash
+# Index your current directory
+cgc index .
+
+# List all indexed repositories
+cgc list
 
-    **IDE/CLI Configuration:**
-    After setting up your database, the wizard will ask to configure your development environment. It can automatically detect and configure the following:
+# Analyze who calls a function
+cgc analyze callers my_function
+
+# Find complex code
+cgc analyze complexity --threshold 10
+
+# Find dead code
+cgc analyze dead-code
+
+# Watch for live changes (optional)
+cgc watch .
+
+# See all commands
+cgc help
+```
+
+**See the full [CLI Commands Guide](CLI_Commands.md) for all available commands and usage scenarios.**
+
+
+---
+
+### 🤖 For MCP Server Mode
+
+**Configure your AI assistant to use CodeGraphContext:**
+
+1.  **Setup:** Run the MCP setup wizard to configure your IDE/AI assistant:
+    
+    ```bash
+    cgc mcp setup
+    ```
+    
+    The wizard can automatically detect and configure:
     *   VS Code
     *   Cursor
     *   Windsurf
@@ -241,10 +313,16 @@ If you’re using CodeGraphContext in your project, feel free to open a PR and a
 
     Upon successful configuration, `cgc mcp setup` will generate and place the necessary configuration files:
     *   It creates an `mcp.json` file in your current directory for reference.
-    *   It stores your Neo4j credentials securely in `~/.codegraphcontext/.env`.
+    *   It stores your database credentials securely in `~/.codegraphcontext/.env`.
     *   It updates the settings file of your chosen IDE/CLI (e.g., `.claude.json` or VS Code's `settings.json`).
 
-3.  **Start:** `cgc mcp start`
+2.  **Start:** Launch the MCP server:
+    
+    ```bash
+    cgc mcp start
+    ```
+
+3.  **Use:** Now interact with your codebase through your AI assistant using natural language! See examples below.
 
 ## Ignoring Files (`.cgcignore`)
 
@@ -276,6 +354,7 @@ Add the following server configuration to your client's settings file (e.g., VS
     "CodeGraphContext": {
       "command": "cgc",
       "args": [
+        "mcp",
         "start"
       ],
       "env": {

{codegraphcontext-0.1.23 → codegraphcontext-0.1.27}/README.md

@@ -20,7 +20,7 @@
 
 
 
-A powerful **MCP server** and **CLI tool** that indexes local code into a graph database to provide context to AI assistants and developers. Use it as a standalone CLI for code analysis or connect it to your favorite AI IDE via MCP.
+A powerful **MCP server** and **CLI toolkit** that indexes local code into a graph database to provide context to AI assistants and developers. Use it as a standalone CLI for comprehensive code analysis or connect it to your favorite AI IDE via MCP for AI-powered code understanding.
 
 ### Indexing a codebase
 ![Indexing using an MCP client](https://github.com/Shashankss1205/CodeGraphContext/blob/main/images/Indexing.gif)
@@ -29,7 +29,7 @@ A powerful **MCP server** and **CLI tool** that indexes local code into a graph
 ![Using the MCP server](https://github.com/Shashankss1205/CodeGraphContext/blob/main/images/Usecase.gif)
 
 ## Project Details
-- **Version:** 0.1.23
+- **Version:** 0.1.27
 - **Authors:** Shashank Shekhar Singh <shashankshekharsingh1205@gmail.com>
 - **License:** MIT License (See [LICENSE](LICENSE) for details)
 - **Website:** [CodeGraphContext](http://codegraphcontext.vercel.app/)
@@ -41,11 +41,12 @@ A powerful **MCP server** and **CLI tool** that indexes local code into a graph
 
 -   **Code Indexing:** Analyzes code and builds a knowledge graph of its components.
 -   **Relationship Analysis:** Query for callers, callees, class hierarchies, call chains and more.
--   **Live Updates:** Watches local files for changes and automatically updates the graph.
+-   **Live File Watching:** Watch directories for changes and automatically update the graph in real-time (`cgc watch`).
 -   **Interactive Setup:** A user-friendly command-line wizard for easy setup.
--   **Dual Mode:** Works as a standalone **CLI tool** for developers and as an **MCP server** for AI agents.
+-   **Dual Mode:** Works as a standalone **CLI toolkit** for developers and as an **MCP server** for AI agents.
 -   **Multi-Language Support:** Full support for 11 programming languages.
--   **Flexible Database Backend:** Choose between Neo4j or FalkorDB Lite.
+-   **Flexible Database Backend:** FalkorDB Lite (default, inbuilt for Unix and through WSL for Windows) or Neo4j (all platforms via Docker/native).
+
 
 ## Supported Programming Languages
 
@@ -62,6 +63,7 @@ CodeGraphContext provides comprehensive parsing and analysis for the following l
 - **Rust** (`.rs`)
 - **Ruby** (`.rb`)
 - **PHP** (`.php`)
+- **Kotlin** (`.kt`) - Full support for classes, objects, companions, functions, and coroutines
 
 Each language parser extracts functions, classes, methods, parameters, inheritance relationships, function calls, and imports to build a comprehensive code graph.
 
@@ -69,27 +71,33 @@ Each language parser extracts functions, classes, methods, parameters, inheritan
 
 CodeGraphContext supports two graph database backends:
 
-### Neo4j (Default)
-- **Production-ready** and widely used graph database
-- Supports local instances (via Docker or native installation) and cloud hosting (Neo4j AuraDB)
-- Full Cypher query support for advanced graph analytics
-- Recommended for most use cases
-
-### FalkorDB Lite
+### FalkorDB Lite (Default for Unix/Linux/macOS)
 - **Lightweight** in-memory graph database
 - **No external dependencies** - runs entirely in-process
+- **Inbuilt and enabled by default** for Unix-based systems (Linux, macOS)
 - Available for **Python 3.12+** only
-- Perfect for quick testing and development
-- Automatically installed when using Python 3.12 or higher
+- Perfect for quick testing, development, and most use cases
+- Automatically installed and configured when using Python 3.12 or higher on Unix systems
+
 > ⚠️ **Windows Users:**  
 > FalkorDB Lite / redislite is **not supported on Windows**.  
-> You have two options:  
+> You have three options:  
 > 1. Run the project under **WSL (Windows Subsystem for Linux)**: [WSL Install](https://learn.microsoft.com/en-us/windows/wsl/install)  
-> 2. Skip FalkorDB and use **Neo4j** directly as your graph database.
+> 2. Use **Docker** to run the project in a containerized Linux environment  
+> 3. Use **Neo4j** directly as your graph database (see below)
 
+### Neo4j (Available for All Platforms)
+- **Production-ready** and widely used graph database
+- **Available on all operating systems**: Windows, Linux, macOS
+- Can be installed via:
+  - **Docker** (recommended, cross-platform)
+  - **WSL** (for Windows users)
+  - **Native installation** (dedicated command for each OS)
+- Supports local instances and cloud hosting (Neo4j AuraDB)
+- Full Cypher query support for advanced graph analytics
+- Recommended for Windows users and production deployments
 
-The `cgc neo4j setup` wizard helps you configure neo4j database backend while the falkordb database is
-supported inherently (enabled by default).
+The `cgc neo4j setup` wizard helps you configure the Neo4j database backend, while FalkorDB Lite is enabled by default on Unix systems with no configuration needed.
 
 ## Used By
 
@@ -122,9 +130,31 @@ If you’re using CodeGraphContext in your project, feel free to open a PR and a
 
 ## Getting Started
 
+### 📋 Understanding CodeGraphContext Modes
+
+CodeGraphContext operates in **two modes**, and you can use either or both:
+
+#### 🛠️ Mode 1: CLI Toolkit (Standalone)
+Use CodeGraphContext as a **powerful command-line toolkit** for code analysis:
+- Index and analyze codebases directly from your terminal
+- Query code relationships, find dead code, analyze complexity
+- Visualize code graphs and dependencies
+- Perfect for developers who want direct control via CLI commands
+
+#### 🤖 Mode 2: MCP Server (AI-Powered)
+Use CodeGraphContext as an **MCP server** for AI assistants:
+- Connect to AI IDEs (VS Code, Cursor, Windsurf, Claude, etc.)
+- Let AI agents query your codebase using natural language
+- Automatic code understanding and relationship analysis
+- Perfect for AI-assisted development workflows
+
+**You can use both modes!** Install once, then use CLI commands directly OR connect to your AI assistant.
+
+---
+
+### Installation (Both Modes)
+
 1.  **Install:** `pip install codegraphcontext`
-2.  **Setup:** `cgc mcp setup`
-    This command configures your IDE to work with CodeGraphContext. To configure a Neo4j database, use `cgc neo4j setup`.
 
     <details>
     <summary>⚙️ Troubleshooting: In case, command <code>cgc</code> not found</summary>
@@ -159,14 +189,56 @@ If you’re using CodeGraphContext in your project, feel free to open a PR and a
     ``` 
     </details>
 
+2.  **Database Setup (Automatic for Unix/WSL)**
     
-    **Database Configuration:**
-    *   **Local Setup (Docker Recommended):** Helps you set up a local Neo4j instance using Docker. Requires Docker and Docker Compose to be installed.
-    *   **Local Setup (Linux Binary):** For Debian-based Linux systems (like Ubuntu), `cgc neo4j setup` can automate the installation of Neo4j. Requires `sudo` privileges.
-    *   **Hosted Setup:** Allows you to connect to an existing remote Neo4j database (e.g., Neo4j AuraDB).
+    - **FalkorDB Lite (Default):** If you're on Unix/Linux/macOS/WSL with Python 3.12+, you're done! FalkorDB Lite is already configured.
+    - **Neo4j (Optional/Windows):** To use Neo4j instead, or if you're on Windows without WSL, run: `cgc neo4j setup`
+
+---
+
+### 🛠️ For CLI Toolkit Mode
+
+**Start using immediately with CLI commands:**
+
+```bash
+# Index your current directory
+cgc index .
+
+# List all indexed repositories
+cgc list
 
-    **IDE/CLI Configuration:**
-    After setting up your database, the wizard will ask to configure your development environment. It can automatically detect and configure the following:
+# Analyze who calls a function
+cgc analyze callers my_function
+
+# Find complex code
+cgc analyze complexity --threshold 10
+
+# Find dead code
+cgc analyze dead-code
+
+# Watch for live changes (optional)
+cgc watch .
+
+# See all commands
+cgc help
+```
+
+**See the full [CLI Commands Guide](CLI_Commands.md) for all available commands and usage scenarios.**
+
+
+---
+
+### 🤖 For MCP Server Mode
+
+**Configure your AI assistant to use CodeGraphContext:**
+
+1.  **Setup:** Run the MCP setup wizard to configure your IDE/AI assistant:
+    
+    ```bash
+    cgc mcp setup
+    ```
+    
+    The wizard can automatically detect and configure:
     *   VS Code
     *   Cursor
     *   Windsurf
@@ -179,10 +251,16 @@ If you’re using CodeGraphContext in your project, feel free to open a PR and a
 
     Upon successful configuration, `cgc mcp setup` will generate and place the necessary configuration files:
     *   It creates an `mcp.json` file in your current directory for reference.
-    *   It stores your Neo4j credentials securely in `~/.codegraphcontext/.env`.
+    *   It stores your database credentials securely in `~/.codegraphcontext/.env`.
     *   It updates the settings file of your chosen IDE/CLI (e.g., `.claude.json` or VS Code's `settings.json`).
 
-3.  **Start:** `cgc mcp start`
+2.  **Start:** Launch the MCP server:
+    
+    ```bash
+    cgc mcp start
+    ```
+
+3.  **Use:** Now interact with your codebase through your AI assistant using natural language! See examples below.
 
 ## Ignoring Files (`.cgcignore`)
 
@@ -214,6 +292,7 @@ Add the following server configuration to your client's settings file (e.g., VS
     "CodeGraphContext": {
       "command": "cgc",
       "args": [
+        "mcp",
         "start"
       ],
       "env": {

{codegraphcontext-0.1.23 → codegraphcontext-0.1.27}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codegraphcontext"
-version = "0.1.23"
+version = "0.1.27"
 description = "An MCP server that indexes local code into a graph database to provide context to AI assistants."
 authors = [{ name = "Shashank Shekhar Singh", email = "shashankshekharsingh1205@gmail.com" }]
 readme = "README.md"

{codegraphcontext-0.1.23 → codegraphcontext-0.1.27}/src/codegraphcontext/cli/cli_helpers.py

@@ -159,8 +159,11 @@ def delete_helper(repo_path: str):
     db_manager, graph_builder, _ = services
     
     try:
-        graph_builder.delete_repository_from_graph(repo_path)
-        console.print(f"[green]Successfully deleted repository: {repo_path}[/green]")
+        if graph_builder.delete_repository_from_graph(repo_path):
+            console.print(f"[green]Successfully deleted repository: {repo_path}[/green]")
+        else:
+            console.print(f"[yellow]Repository not found in graph: {repo_path}[/yellow]")
+            console.print("[dim]Tip: Use 'cgc list' to see available repositories.[/dim]")
     except Exception as e:
         console.print(f"[bold red]An error occurred:[/bold red] {e}")
     finally:
@@ -512,3 +515,94 @@ def stats_helper(path: str = None):
         console.print(f"[bold red]An error occurred:[/bold red] {e}")
     finally:
         db_manager.close_driver()
+
+
+def watch_helper(path: str):
+    """Watch a directory for changes and auto-update the graph (blocking mode)."""
+    from ..core.watcher import CodeWatcher
+    
+    services = _initialize_services()
+    if not all(services):
+        return
+
+    db_manager, graph_builder, code_finder = services
+    path_obj = Path(path).resolve()
+
+    if not path_obj.exists():
+        console.print(f"[red]Error: Path does not exist: {path_obj}[/red]")
+        db_manager.close_driver()
+        return
+    
+    if not path_obj.is_dir():
+        console.print(f"[red]Error: Path must be a directory: {path_obj}[/red]")
+        db_manager.close_driver()
+        return
+
+    console.print(f"[bold cyan]🔍 Watching {path_obj} for changes...[/bold cyan]")
+    
+    # Check if already indexed
+    indexed_repos = code_finder.list_indexed_repositories()
+    is_indexed = any(Path(repo["path"]).resolve() == path_obj for repo in indexed_repos)
+    
+    # Create watcher instance
+    job_manager = JobManager()
+    watcher = CodeWatcher(graph_builder, job_manager)
+    
+    try:
+        # Start the observer thread
+        watcher.start()
+        
+        # Add the directory to watch
+        if is_indexed:
+            console.print("[green]✓[/green] Already indexed (no initial scan needed)")
+            watcher.watch_directory(str(path_obj), perform_initial_scan=False)
+        else:
+            console.print("[yellow]⚠[/yellow]  Not indexed yet. Performing initial scan...")
+            
+            # Index the repository first (like MCP does)
+            async def do_index():
+                await graph_builder.build_graph_from_path_async(path_obj, is_dependency=False)
+            
+            asyncio.run(do_index())
+            console.print("[green]✓[/green] Initial scan complete")
+            
+            # Now start watching (without another scan)
+            watcher.watch_directory(str(path_obj), perform_initial_scan=False)
+        
+        console.print("[bold green]👀 Monitoring for file changes...[/bold green] (Press Ctrl+C to stop)")
+        console.print("[dim]💡 Tip: Open a new terminal window to continue working[/dim]\n")
+        
+        # Block here and keep the watcher running
+        import threading
+        stop_event = threading.Event()
+        
+        try:
+            stop_event.wait()  # Wait indefinitely until interrupted
+        except KeyboardInterrupt:
+            console.print("\n[yellow]🛑 Stopping watcher...[/yellow]")
+            
+    except KeyboardInterrupt:
+        console.print("\n[yellow]🛑 Stopping watcher...[/yellow]")
+    except Exception as e:
+        console.print(f"[bold red]An error occurred:[/bold red] {e}")
+    finally:
+        watcher.stop()
+        db_manager.close_driver()
+        console.print("[green]✓[/green] Watcher stopped. Graph is up to date.")
+
+
+
+def unwatch_helper(path: str):
+    """Stop watching a directory."""
+    console.print(f"[yellow]⚠️  Note: 'cgc unwatch' only works when the watcher is running via MCP server.[/yellow]")
+    console.print(f"[dim]For CLI watch mode, simply press Ctrl+C in the watch terminal.[/dim]")
+    console.print(f"\n[cyan]Path specified:[/cyan] {Path(path).resolve()}")
+
+
+def list_watching_helper():
+    """List all directories currently being watched."""
+    console.print(f"[yellow]⚠️  Note: 'cgc watching' only works when the watcher is running via MCP server.[/yellow]")
+    console.print(f"[dim]For CLI watch mode, check the terminal where you ran 'cgc watch'.[/dim]")
+    console.print(f"\n[cyan]To see watched directories in MCP mode:[/cyan]")
+    console.print(f"  1. Start the MCP server: cgc mcp start")
+    console.print(f"  2. Use the 'list_watched_paths' MCP tool from your IDE")

{codegraphcontext-0.1.23 → codegraphcontext-0.1.27}/src/codegraphcontext/cli/config_manager.py

@@ -33,6 +33,7 @@ DEFAULT_CONFIG = {
     "MAX_DEPTH": "unlimited",
     "PARALLEL_WORKERS": "4",
     "CACHE_ENABLED": "true",
+    "IGNORE_DIRS": "node_modules,venv,.venv,env,.env,dist,build,target,out,.git,.idea,.vscode,__pycache__",
 }
 
 # Configuration key descriptions
@@ -50,6 +51,7 @@ CONFIG_DESCRIPTIONS = {
     "MAX_DEPTH": "Maximum directory depth for indexing (unlimited or number)",
     "PARALLEL_WORKERS": "Number of parallel indexing workers",
     "CACHE_ENABLED": "Enable caching for faster re-indexing",
+    "IGNORE_DIRS": "Comma-separated list of directory names to ignore during indexing",
 }
 
 # Valid values for each config key

{codegraphcontext-0.1.23 → codegraphcontext-0.1.27}/src/codegraphcontext/cli/main.py

@@ -38,6 +38,9 @@ from .cli_helpers import (
     clean_helper,
     stats_helper,
     _initialize_services,
+    watch_helper,
+    unwatch_helper,
+    list_watching_helper,
 )
 
 # Set the log level for the noisy neo4j and asyncio logger to WARNING to keep the output clean.
@@ -610,6 +613,68 @@ def add_package(package_name: str = typer.Argument(..., help="Name of the packag
     _load_credentials()
     add_package_helper(package_name, language)
 
+# ============================================================================
+# WATCH COMMAND GROUP - Live File Monitoring
+# ============================================================================
+
+@app.command()
+def watch(
+    path: str = typer.Argument(".", help="Path to the directory to watch. Defaults to current directory.")
+):
+    """
+    Watch a directory for file changes and automatically update the code graph.
+    
+    This command runs in the foreground and monitors the specified directory
+    for any file changes. When changes are detected, the code graph is
+    automatically updated.
+    
+    The watcher will:
+    - Perform an initial scan if the directory is not yet indexed
+    - Monitor for file creation, modification, deletion, and moves
+    - Automatically re-index affected files and update relationships
+    
+    Press Ctrl+C to stop watching.
+    
+    Examples:
+        cgc watch .                    # Watch current directory
+        cgc watch /path/to/project     # Watch specific directory
+        cgc w .                        # Using shortcut alias
+    """
+    _load_credentials()
+    watch_helper(path)
+
+@app.command()
+def unwatch(
+    path: str = typer.Argument(..., help="Path to stop watching")
+):
+    """
+    Stop watching a directory for changes.
+    
+    Note: This command is primarily for MCP server mode.
+    For CLI watch mode, simply press Ctrl+C in the watch terminal.
+    
+    Examples:
+        cgc unwatch /path/to/project
+    """
+    _load_credentials()
+    unwatch_helper(path)
+
+@app.command()
+def watching():
+    """
+    List all directories currently being watched for changes.
+    
+    Note: This command is primarily for MCP server mode.
+    For CLI watch mode, check the terminal where you ran 'cgc watch'.
+    
+    Examples:
+        cgc watching
+    """
+    _load_credentials()
+    list_watching_helper()
+
+
+
 # ============================================================================
 # FIND COMMAND GROUP - Code Search & Discovery
 # ============================================================================
@@ -1220,6 +1285,12 @@ def visualize_abbrev(query: Optional[str] = typer.Argument(None, help="Cypher qu
     """Shortcut for 'cgc visualize'"""
     visualize(query)
 
+@app.command("w", rich_help_panel="Shortcuts")
+def watch_abbrev(path: str = typer.Argument(".", help="Path to watch")):
+    """Shortcut for 'cgc watch'"""
+    watch(path)
+
+
 # ============================================================================