Reported issues for OMEGA Memory

Pod holds 13 of 13 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to OMEGA Memory.

Most discussed

docs: add Cursor MCP configuration example

Summary

The README shows how to configure OMEGA for Claude Code but doesn't include a configuration example for Cursor, which is one of the most popular AI-powered editors.

What to do

Add a section to the README (in the Setup / Configuration area, after the existing Claude Code example) showing how to configure OMEGA in Cursor's MCP settings.

File to edit: README.md

Cursor MCP config location: .cursor/mcp.json (in your project root)

**Example configu

Read the thread · 2026-03-14 · closed · 4 comments

Pro license activates but Pro MCP tools never load — omega_memory_pro wheel missing omega.plugins entry point

Summary

A valid, active Pro license does not unlock Pro MCP tools. Root cause is a packaging bug in the omega_memory_pro wheel: it ships the omega_platform code but registers no omega.plugins entry point, so the capability gate in mcp_server.py stays closed and all ~93 Pro tools are silently skipped at MCP startup.

Environment

• omega (core) 1.5.4, omega_memory_pro 1.5.4
• Installed via uv into a dedicated venv (Python 3.14)
• macOS; license active (omega license

Read the thread · 2026-06-22 · closed · external user · 3 comments

Windows: MCP server crashes on startup — ModuleNotFoundError: resource (mcp_server._get_current_rss_bytes)

Environment

• OS: Windows 10/11 (win32)
• Python: 3.13
• Package: omega-memory 1.4.9 (pip install omega-memory[server])
• Client: Cursor MCP (python -m omega.server.mcp_server, OMEGA_CLIENT=cursor)

Problem

The MCP server exits immediately on Windows. Cursor shows omega-memory in error state.

Traceback

ModuleNotFoundError: No module named 'resource' File ".../omega/server/mcp_server.py", line 1084, in asyncio.run(main()) File ".../omega/server/mcp_server.py

Read the thread · 2026-05-04 · closed · external user · 2 comments

handlers.py _get_store() imports non-existent omega.store module

Bug

omega/server/handlers.py:49-52 imports from omega.store, which doesn't exist in the package:

def _get_store():
    """Get the memory store instance."""
    from omega.store import MemoryStore
    return MemoryStore()

The actual module is omega.sqlite_store and the class is SQLiteStore. This appears to be a leftover from a rename during development.

Impact

Any MCP tool that calls _get_store() crashes with ModuleNotFoundError: No module named 'omega.store'.

Read the thread · 2026-03-17 · closed · external user · 2 comments

Add Windows/WSL installation guide

OMEGA works on Windows through WSL, but there are no docs covering the setup.

What's needed:

• Step-by-step WSL installation instructions
• Any WSL-specific gotchas (file paths, keyring behavior, etc.)
• Add a Windows/WSL section to the README or a separate doc

Good first issue because it's documentation-only, no code changes required. Just needs someone with a Windows machine to test and document the experience.

Read the thread · 2026-02-15 · closed · 2 comments

docs: add Zed editor MCP configuration example

Summary

Zed now supports MCP servers natively. The README should include a configuration example so Zed users can set up OMEGA quickly.

What to do

Add a section to the README (in the Setup / Configuration area, after the existing Claude Code example) showing how to configure OMEGA in Zed's settings.

File to edit: README.md

Zed config location: Zed settings (Zed > Settings > Open Settings or ~/.config/zed/settings.json)

**Example configuration to add:

Read the thread · 2026-03-14 · closed · 1 comment

docs: add directory listing badges to README

Summary

OMEGA is listed on several well-known MCP and tool directories. Adding a "Listed On" or "Featured In" section to the README would boost credibility and help new visitors understand the project's traction.

What to do

Add a "Listed On" or "Featured In" section near the top of the README (after the existing badges, before the main description) with links/badges to these directories:

1. Official MCP Registry — https://github.com/modelcontextprotocol/servers
2. **punkpeye/awesom

Read the thread · 2026-03-14 · closed · 1 comment

docs: add Windsurf MCP configuration example

Summary

The README shows how to configure OMEGA for Claude Code but doesn't include a configuration example for Windsurf, another popular AI-powered editor that supports MCP.

What to do

Add a section to the README (in the Setup / Configuration area, after the existing Claude Code example) showing how to configure OMEGA in Windsurf's MCP settings.

File to edit: README.md

Windsurf MCP config location: ~/.codeium/windsurf/mcp_config.json

**Exa

Read the thread · 2026-03-14 · closed · 1 comment

Most recent

Support additional MCP clients in omega setup

Summary

omega setup currently supports Claude Code, Cursor, Windsurf, and Zed. There are more MCP-compatible editors and tools emerging. Adding support for additional clients would expand OMEGA's reach.

Candidates

• Continue (VS Code / JetBrains extension) — ~/.continue/config.json
• Cline (VS Code extension) — ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Any new MCP client — contributions welcome as th

Read the thread · 2026-02-14 · closed · 1 comment

Add CONTRIBUTING guide with development setup instructions

Problem

The CONTRIBUTING.md exists but may need more detail on:

• How to set up a development environment from scratch
• How to run the test suite
• Code style guidelines (ruff config)
• How the MCP server can be tested locally without Claude Code
• PR expectations and review process

What to do

Expand CONTRIBUTING.md to include:

1. Dev setup — clone, create venv, pip install -e ".[dev]", verify with omega doctor
2. Running tests — pytest tests/ with any flags or env vars

Read the thread · 2026-02-14 · closed · 0 comments

Add omega export/import commands for memory portability

Problem

Users may want to:

• Back up their memories to a portable format
• Move memories between machines
• Share anonymized memory templates

The MCP server has omega_backup (export/import to file), but there's no CLI equivalent.

What to do

Add omega export and omega import CLI commands:

# Export all memories to a JSON file
omega export memories.json

# Import memories from a JSON file
omega import memories.json

Implementation hints

• The backup logic already ex

Read the thread · 2026-02-14 · closed · 0 comments

Improve error message when ONNX model is not downloaded

Problem

If a user runs omega query or uses the MCP server before running omega setup, the ONNX embedding model won't be present at ~/.cache/omega/models/bge-small-en-v1.5-onnx/. The current error can be cryptic (file not found or ONNX runtime error).

What to do

Add a clear, actionable error message when the embedding model directory is missing:

Error: ONNX embedding model not found at ~/.cache/omega/models/bge-small-en-v1.5-onnx/

Run 'omega setup' to download the model (~90 

[Read the thread](https://github.com/omega-memory/omega-memory/issues/3) · 2026-02-14 · closed · 0 comments

### Add Cursor and Windsurf setup guides

## Problem

The README's compatibility table says Cursor and Windsurf have "Full" support with "Manual MCP config in settings", but doesn't explain how to actually configure them.

New users on Cursor or Windsurf have no clear path to getting OMEGA working.

## What to do

Add a `docs/setup-cursor.md` and `docs/setup-windsurf.md` (or a single `docs/editor-setup.md`) that explains:

1. Where to find the MCP settings in each editor
2. The exact JSON config to add
3. How to verify OMEGA is connecte

[Read the thread](https://github.com/omega-memory/omega-memory/issues/1) · 2026-02-14 · closed · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/omega-memory/omega-memory/issues).