Very slow indexing and MCP hangs on Windows when project is on a remote macOS SMB shared drive

[cutey-none]

Title

Very slow indexing and MCP hangs on Windows when project is on a remote macOS SMB shared drive

Description

Hi, thanks for building CodeGraph.

I am using CodeGraph on a Windows machine. My project is physically stored on a remote macOS machine, and Windows accesses it through an SMB shared folder mapped as a drive.

I noticed a very large performance difference between indexing the same project from a local Windows path and indexing it from the remote macOS SMB shared path.

Environment

• CodeGraph version: 0.9.9
• OS running CodeGraph: Windows 11 Pro 24H2, build 26100.6584
• Remote machine OS: macOS 26.5.1
• Share type: SMB
• Windows mapped drive example: Z:\...
• Project language: Swift / Objective-C mixed project
• .codegraph location: inside the shared project directory
• AI tool: Claude Code
• Claude Code is launched on Windows
• Project size: about 8,500+ valid indexed files

What I observed

For the same project:

Case 1: Project on local Windows disk

When the project is stored on a local Windows disk, running CodeGraph commands such as:

codegraph init
codegraph sync
codegraph status

takes about 5 minutes to index around 8,500+ valid files.

Case 2: Project on remote macOS SMB shared directory

When the same project is stored on a remote macOS machine and accessed from Windows through an SMB mapped drive, the same CodeGraph operations become extremely slow.

The same indexing process takes around 4–5 hours.

The commands that are noticeably slow include:

codegraph init
codegraph sync
codegraph status

Later, I also noticed that when using CodeGraph MCP inside Claude Code on Windows against this SMB-mounted project, CodeGraph sometimes appears to hang or block for a long time.

Expected behavior

I understand that indexing over an SMB/network-mounted directory can be slower than indexing a local directory.

However, the difference seems very large:

• Local Windows project: around 5 minutes
• Remote macOS SMB shared project: around 4–5 hours

I would expect the SMB case to be slower, but not by such a large margin.

Actual behavior

When the project is accessed from Windows through the SMB mapped drive:

1. codegraph init takes several hours.
2. codegraph sync and codegraph status can also become very slow.
3. CodeGraph MCP usage inside Claude Code sometimes hangs or blocks for a long time.
4. Since .codegraph is also located inside the shared project directory, I am wondering whether SQLite/database access or repeated file reads over SMB may be contributing to the slowdown.

Steps to reproduce

1. On Windows, clone or place a project with around 8,500+ valid source files on a local disk.
2. Run:

codegraph init
codegraph status

3. Record the indexing time.
4. On macOS, clone or place the same project.
5. Share the project directory through SMB.
6. On Windows, map the SMB shared directory as a drive, for example Z:\....
7. Run the same commands from Windows:

codegraph init
codegraph status

8. Compare the indexing time and MCP responsiveness in Claude Code.

Questions

I would like to ask:

1. Is indexing a project through a Windows SMB mapped drive officially supported or recommended?
2. Is this level of slowdown expected when CodeGraph runs on Windows but the project files are on a remote macOS SMB share?
3. Is there any recommended workflow for this setup?
4. Would it be better to run CodeGraph directly on the macOS machine where the project files physically exist?
5. Should .codegraph avoid being stored on the SMB shared directory?
6. Is there any way to configure CodeGraph so that the index/database is stored locally on Windows while the source files remain on the SMB share?
7. Are there any settings to reduce repeated file reads or improve performance for network-mounted projects?
8. For MCP usage in Claude Code, are there any timeout, daemon, cache, or file-watching behaviors I should check when CodeGraph appears to hang?
9. I am currently using CodeGraph 0.9.9. If this has already been improved in a newer version, please let me know and I can retest with the latest version.

Workarounds I am considering

A few possible workarounds I am considering:

• Run CodeGraph on the macOS machine instead of running it on Windows against the SMB share.
• Keep a local clone of the project on Windows for CodeGraph indexing.
• Use a sync-based workflow instead of directly indexing the SMB-mounted project.
• Avoid storing .codegraph on the SMB share if CodeGraph supports a local index/database location.

I am not sure what the recommended approach is, so any guidance would be appreciated.

Thanks!