Graph memory says connected, but doesn't seem to be working?

[nullbio]

Checklist

• I searched existing issues and this hasn't been reported

Area

Fullstack

Operating System

Windows

Version

2.7.2-beta.12

What happened?

Under "Context -> Memories", Graph Memory Status says "Connected", but there are no memories.

Steps to reproduce

Under "Context -> Memories", Graph Memory Status says "Connected", but there are no memories.

If I go to "Agent Terminals", and open Claude in terminal, /mcp does not show any MCPs. Is this expected?

If I go to Insights, and ask if Graphiti is working properly, Claude claims:

• The Graphiti MCP server isn't running
• The tools aren't properly registered with this Claude instance

The log files don't show anything related to Graphiti. Memorys never seem to fill.

I configured it in Project Settings to use Agent Memory Access, Voyage API, and gave it a model name of "voyage-3-large".

Expected behavior

Logged memories.

Logs / Screenshots

=== Auto Claude Debug Report ===
Generated: 2026-01-01T04:23:05.338Z

--- System Information ---
appVersion: 2.7.2-beta.12
electronVersion: 39.2.7
nodeVersion: 22.21.1
chromeVersion: 142.0.7444.235
platform: win32
arch: x64
osVersion: 10.0.22631
osType: Windows_NT
totalMemory: 128GB
freeMemory: 61GB
cpuCores: 24
locale: en-GB
isPackaged: true
userData: C:\Users\na\AppData\Roaming\auto-claude-ui

--- Recent Errors ---
No recent errors

=== End Debug Report ===

[github-actions]

👋 Thanks for opening your first issue!

A maintainer will triage this soon. In the meantime:

• Make sure you've provided all the requested info
• Join our Discord for faster help

[joelfuller2016]

@openhands-agent Please fix this Graphiti memory integration bug.

Issue Summary: Graph Memory shows "Connected" but has no memories, Graphiti MCP server not running, tools not registered with Claude instance.

Platform: Windows (Auto Claude v2.7.2-beta.12)

User Configuration:

• Agent Memory Access enabled
• Voyage API configured with model "voyage-3-large"

Investigation Areas:

1. apps/backend/integrations/graphiti/ - Check Graphiti initialization
2. apps/backend/graphiti_config.py - Validate configuration loading
3. apps/backend/graphiti_providers.py - Verify Voyage AI provider setup
4. MCP registration in apps/backend/core/client.py

Potential Causes:

• Graphiti service not starting on Windows
• Voyage AI provider not properly initialized
• MCP tools not being registered with Claude sessions
• Missing error logging for silent failures

Required Fixes:

1. Add detailed logging for Graphiti initialization steps
2. Verify Windows-compatible startup sequence
3. Ensure MCP tools register properly in terminal sessions
4. Add connection validation beyond just "Connected" status

Target Branch: develop