Feature Request: Desktop app as remote client (connect to remote instance for graph visualization)

[yang-he]

Problem

I run Nowledge Mem on a Mac mini (always-on server) where all my memories are stored. My daily work machine is a MacBook Pro.

Currently, I can access my memory from the MacBook Pro via:

• ✅ nmem CLI (remote API)
• ✅ Chrome browser extension (Exchange)
• ✅ MCP connections (Cursor, Claude Code, etc.)

However, I cannot use the desktop app's graph visualization on my MacBook Pro to explore memories stored on the Mac mini. The desktop app always starts its own local engine and local database — there is no way to point it at a remote Nowledge Mem instance.

Proposed Solution

Add a "Remote Mode" or "Client Mode" to the desktop app, where:

1. Instead of starting a local engine, the app connects to a remote Nowledge Mem instance via API URL + API Key (same credentials used by nmem CLI and browser extension)
2. All features work as normal — especially the interactive knowledge graph visualization, timeline, and visual exploration
3. The app acts as a pure UI client; all data stays on the remote server

Use Case

This is a natural extension of the existing "Access Mem Anywhere" architecture. The CLI, browser extension, and MCP clients already support remote connections. The desktop app is the only client that doesn't.

Many users likely have a similar setup: a central always-on machine (Mac mini, home server, Linux VPS) running Nowledge Mem, with laptops and other devices connecting remotely. The graph visualization is one of Nowledge Mem's most compelling features — it would be great to access it from any machine.

Environment

• Server: Mac mini (Apple Silicon, macOS 15+)
• Client: MacBook Pro (Apple Silicon, macOS 15+)
• Connection: Cloudflare Zero Trust Tunnel (stable URL)
• Nowledge Mem version: v0.6