Nexusyn Engine
Long-Term, Time-Aware Memory Engine for AI Agents
Stop building agents that forget. Give your LLMs persistent, grounded memory across sessions.
接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
Most AI agent frameworks implement memory by taking the last conversation turn, calculating an embedding, and storing it in a vector database.
When the agent queries this "memory", it runs a simple nearest-neighbor search. This breaks down in production:
Nexusyn is a dedicated data plane engine designed specifically for agentic long-term memory:
valid_from / valid_to). New statements supersede older ones automatically without deleting history.pgvector HNSW) + BM25 full-text search + entity graph expansion + recency & date-anchor boosts using Reciprocal Rank Fusion./v1/mcp) running over streamable HTTP. Connects directly to Claude Code, Cursor, Windsurf, or custom agent frameworks with zero glue code.Nexusyn is evaluated against standard public benchmarks for agent long-term memory under reproducible conditions:
┌─────────────────────────┐
│ AI Agent / IDE │
│ (Claude Code, Cursor, …)│
└────────────┬────────────┘
HTTP │ MCP (/v1/mcp)
▼
┌────────────────────────────────────────────────────────────────────────┐
│ NEXUSYN ENGINE │
│ │
│ POST /v1/ingest POST /v1/query │
│ │ │ │
│ ▼ ▼ │
│ [ Deduplication ] [ Sub-query Gen ] │
│ │ │ │
│ [ Chunker ] [ Hybrid Retrieval ] │
│ │ ├── Vector (HNSW) │
│ ▼ ├── BM25 Full-Text │
│ [ River Queue (Async) ] ├── Entity Graph │
│ ├── Batch Embeddings └── Date Anchor Boost │
│ ├── Entity & Relation Extraction │ │
│ └── Wiki / Profile Compilation ▼ │
│ │ [ RRF Fusion ] │
│ ▼ │ │
│ [ PostgreSQL 18 (pgvector) ] [ Cross-Encoder Rerank]│
│ Row-Level Security (Multi-Tenant) │ │
│ ▼ │
│ [ Grounded Answer ] │
│ (Synthesized + Sources)│
└────────────────────────────────────────────────────────────────────────┘
Get the complete stack running locally (PostgreSQL 17+ with pgvector, the Nexusyn HTTP/MCP API on :8044, and the River background worker) in under 60 seconds:
# 1. Clone the repository
git clone https://github.com/nexusyn/engine.git
cd engine
# 2. Configure environment
cp .env.example .env
# Edit .env with your preferred model provider API keys
# (OpenAI, Anthropic, Gemini, Ollama, Jina, etc.)
# 3. Spin up the containers
docker compose up -d
# 4. Verify health
curl http://localhost:8044/health
# {"status":"ok","time":"..."}
Nexusyn runs an HTTP Model Context Protocol (MCP) server at /v1/mcp. Any MCP-compliant client gets persistent long-term memory tools out of the box.
Connect Nexusyn to Claude Code with a single CLI command:
claude mcp add nexusyn --transport http \
"http://localhost:8044/v1/mcp" \
--header "Authorization: Bearer <YOUR_API_TOKEN>"
~/.cursor/mcp.json)Add Nexusyn to your Cursor global or project configuration:
{
"mcpServers": {
"nexusyn": {
"url": "http://localhost:8044/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}
~/.codeium/windsurf/mcp_config.json){
"mcpServers": {
"nexusyn": {
"serverUrl": "http://localhost:8044/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}
add_memory — Record a decision, convention, lesson, or fact tagged by project and agent.search_memory — Query memories using hybrid search, returning grounded answers with sources.get_guideline — Retrieve organization/project-wide mandatory standards.update_memory / delete_memory — In-place curation and correction of existing records.Two endpoints cover 90% of all integration needs:
POST /v1/ingest)curl -X POST http://localhost:8044/v1/ingest \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"title": "Auth Architecture",
"content": "We migrated from session cookies to stateless JWT with Ed25519 token signing on 2026-08-15.",
"agent": "cursor",
"project": "mobile-app"
}'
Response:
{
"job_id": 482,
"status": "queued"
}
POST /v1/query)curl -X POST http://localhost:8044/v1/query \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"question": "What token signing algorithm do we use for authentication?",
"project": "mobile-app"
}'
Response:
{
"question": "What token signing algorithm do we use for authentication?",
"answer": "The authentication system uses stateless JWTs signed with the Ed25519 algorithm, migrated on August 15, 2026.",
"sources": [
{
"id": "chk_9a8b7c",
"title": "Auth Architecture",
"content": "We migrated from session cookies to stateless JWT with Ed25519 token signing on 2026-08-15.",
"score": 0.942
}
],
"usage": {
"model": "gpt-4o-mini",
"prompt_tokens": 312,
"completion_tokens": 38
}
}
Streaming: Real-time token streaming with Server-Sent Events (SSE) is available at
POST /v1/query/stream.
Nexusyn uses an adapter architecture. Bring your own models for generation, embeddings, and reranking:
# Build binary
go build -v ./...
# Run unit tests
go test -v ./internal/core/... ./internal/auth/... ./internal/dateutil/...
# Run security checks
gitleaks detect --source . --no-git
govulncheck ./...
Open-source long-term, time-aware memory engine for AI agents (MCP + hybrid search + bi-temporal recall)
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Engine 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 Open-source long-term, time-aware memory engine for AI agents (MCP + hybrid search + bi-temporal recall)