memorix 1.0.4 → 1.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +564 -489
- package/CLAUDE.md +106 -56
- package/README.md +193 -24
- package/README.zh-CN.md +222 -53
- package/dist/cli/index.js +41006 -35768
- package/dist/cli/index.js.map +1 -1
- package/dist/dashboard/static/app.js +769 -677
- package/dist/dashboard/static/index.html +4 -0
- package/dist/dashboard/static/style.css +492 -20
- package/dist/index.js +2979 -870
- package/dist/index.js.map +1 -1
- package/llms-full.txt +365 -0
- package/llms.txt +75 -0
- package/package.json +110 -101
package/llms-full.txt
ADDED
|
@@ -0,0 +1,365 @@
|
|
|
1
|
+
# Memorix - Full Documentation for AI Systems
|
|
2
|
+
|
|
3
|
+
> Open-source cross-agent memory layer for coding agents via MCP
|
|
4
|
+
|
|
5
|
+
## Overview
|
|
6
|
+
|
|
7
|
+
Memorix is an open-source MCP server written in TypeScript that provides persistent, project-aware memory for coding agents. It is designed for coding workflows, not generic chat memory, and works across Cursor, Claude Code, Codex, Windsurf, Gemini CLI, GitHub Copilot, Kiro, OpenCode, Antigravity, and Trae through MCP.
|
|
8
|
+
|
|
9
|
+
If you are an AI coding agent helping a user install or operate Memorix, read [docs/AGENT_OPERATOR_PLAYBOOK.md](https://github.com/AVIDS2/memorix/blob/main/docs/AGENT_OPERATOR_PLAYBOOK.md) before taking action. It is the canonical operator guide for runtime mode selection, Git/project binding, integrations, hooks, and troubleshooting.
|
|
10
|
+
|
|
11
|
+
Memorix solves four recurring problems in AI-assisted development:
|
|
12
|
+
|
|
13
|
+
1. **Session amnesia** - the next chat forgets what the previous one learned
|
|
14
|
+
2. **IDE isolation** - memory created in one coding IDE is invisible to another
|
|
15
|
+
3. **Engineering truth loss** - commits record what changed, but not in a form agents can easily recall
|
|
16
|
+
4. **Config and workflow fragmentation** - MCP config, agent rules, and IDE integrations drift apart over time
|
|
17
|
+
|
|
18
|
+
## Product Model
|
|
19
|
+
|
|
20
|
+
Memorix is best understood as four layers:
|
|
21
|
+
|
|
22
|
+
1. **Runtime layer**
|
|
23
|
+
- MCP server over stdio or HTTP
|
|
24
|
+
- Project detection
|
|
25
|
+
- Config loading and project switching
|
|
26
|
+
|
|
27
|
+
2. **Memory core**
|
|
28
|
+
- Observations
|
|
29
|
+
- Sessions
|
|
30
|
+
- Search index
|
|
31
|
+
- Retention
|
|
32
|
+
- Export/import
|
|
33
|
+
- Knowledge graph relations
|
|
34
|
+
|
|
35
|
+
3. **Quality layer**
|
|
36
|
+
- Formation pipeline
|
|
37
|
+
- Source-aware retrieval
|
|
38
|
+
- Compaction
|
|
39
|
+
- Optional LLM quality improvements
|
|
40
|
+
- Optional local vector search
|
|
41
|
+
|
|
42
|
+
4. **Platform layer**
|
|
43
|
+
- Git Memory
|
|
44
|
+
- Hooks and auto-capture
|
|
45
|
+
- Rules sync
|
|
46
|
+
- Workspace sync
|
|
47
|
+
- Team collaboration
|
|
48
|
+
- Dashboard
|
|
49
|
+
|
|
50
|
+
## Memory Layers
|
|
51
|
+
|
|
52
|
+
### 1. Observation Memory
|
|
53
|
+
|
|
54
|
+
Observation memory stores reusable project knowledge such as:
|
|
55
|
+
|
|
56
|
+
- architecture decisions
|
|
57
|
+
- gotchas
|
|
58
|
+
- bug fixes
|
|
59
|
+
- implementation notes
|
|
60
|
+
- discoveries
|
|
61
|
+
- trade-offs
|
|
62
|
+
- what changed
|
|
63
|
+
|
|
64
|
+
Examples:
|
|
65
|
+
|
|
66
|
+
- `decision` - chose queue-based ingestion over direct writes
|
|
67
|
+
- `problem-solution` - fixed dashboard width jump by stabilizing scrollbar gutter
|
|
68
|
+
- `gotcha` - npm publish fails from Windows device-style cwd paths
|
|
69
|
+
- `what-changed` - reworked project detection to use git identity consistently
|
|
70
|
+
|
|
71
|
+
### 2. Reasoning Memory
|
|
72
|
+
|
|
73
|
+
Reasoning memory stores the **why** behind decisions:
|
|
74
|
+
|
|
75
|
+
- alternatives considered
|
|
76
|
+
- rationale
|
|
77
|
+
- constraints
|
|
78
|
+
- expected outcomes
|
|
79
|
+
- risks
|
|
80
|
+
|
|
81
|
+
This is the layer that helps future agents understand why a system was designed a certain way instead of only seeing the final code change.
|
|
82
|
+
|
|
83
|
+
### 3. Git Memory
|
|
84
|
+
|
|
85
|
+
Git Memory turns commits into structured memory with provenance:
|
|
86
|
+
|
|
87
|
+
- `source='git'`
|
|
88
|
+
- commit hash
|
|
89
|
+
- files changed
|
|
90
|
+
- inferred type
|
|
91
|
+
- entity extraction
|
|
92
|
+
- noise filtering
|
|
93
|
+
|
|
94
|
+
Memorix can:
|
|
95
|
+
|
|
96
|
+
- install a `post-commit` hook
|
|
97
|
+
- ingest a single commit
|
|
98
|
+
- ingest a commit range or recent history
|
|
99
|
+
- skip low-value commit noise
|
|
100
|
+
- preserve release and milestone commits
|
|
101
|
+
|
|
102
|
+
This is one of Memorix's main differentiators for coding agents.
|
|
103
|
+
|
|
104
|
+
## Retrieval Model
|
|
105
|
+
|
|
106
|
+
Memorix retrieval is intentionally layered:
|
|
107
|
+
|
|
108
|
+
- **Search** - compact project-scoped or global retrieval
|
|
109
|
+
- **Timeline** - chronological context around an event
|
|
110
|
+
- **Detail** - full observation detail
|
|
111
|
+
- **Dashboard** - visual and operational view
|
|
112
|
+
|
|
113
|
+
Important retrieval behavior:
|
|
114
|
+
|
|
115
|
+
- default search is **current-project scoped**
|
|
116
|
+
- `scope="global"` searches across projects
|
|
117
|
+
- global results can be opened explicitly with project-aware refs
|
|
118
|
+
- source-aware retrieval boosts:
|
|
119
|
+
- Git memory for "what changed" style queries
|
|
120
|
+
- reasoning/decision memory for "why" style queries
|
|
121
|
+
- both for debugging/problem-solving style queries
|
|
122
|
+
|
|
123
|
+
## Configuration Model
|
|
124
|
+
|
|
125
|
+
Memorix now uses a simple outward-facing model:
|
|
126
|
+
|
|
127
|
+
- `memorix.yml` for behavior and project settings
|
|
128
|
+
- `.env` for secrets
|
|
129
|
+
|
|
130
|
+
Internally it still supports layered config and compatibility fallbacks, but the intended user-facing mental model is:
|
|
131
|
+
|
|
132
|
+
- **behavior in YAML**
|
|
133
|
+
- **secrets in `.env`**
|
|
134
|
+
|
|
135
|
+
This is more structured than flat env-only config and is intended to keep the system explainable.
|
|
136
|
+
|
|
137
|
+
## Runtime Modes
|
|
138
|
+
|
|
139
|
+
### Stdio MCP
|
|
140
|
+
|
|
141
|
+
```bash
|
|
142
|
+
memorix serve
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
Use this for normal MCP clients that expect stdio transport.
|
|
146
|
+
|
|
147
|
+
This is the best fit for quick, single-project usage where the client already launches Memorix from the correct workspace root.
|
|
148
|
+
|
|
149
|
+
Generic stdio MCP config:
|
|
150
|
+
|
|
151
|
+
```json
|
|
152
|
+
{
|
|
153
|
+
"mcpServers": {
|
|
154
|
+
"memorix": {
|
|
155
|
+
"command": "memorix",
|
|
156
|
+
"args": ["serve"]
|
|
157
|
+
}
|
|
158
|
+
}
|
|
159
|
+
}
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
### HTTP MCP + Dashboard
|
|
163
|
+
|
|
164
|
+
```bash
|
|
165
|
+
memorix background start
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
Use this when you want:
|
|
169
|
+
|
|
170
|
+
- HTTP MCP transport
|
|
171
|
+
- collaboration tools
|
|
172
|
+
- the dashboard on the same port
|
|
173
|
+
- a long-lived control plane that keeps running in the background
|
|
174
|
+
|
|
175
|
+
Use `memorix serve-http --port 3211` when you want the same HTTP control plane in the foreground for debugging, manual supervision, or a custom port.
|
|
176
|
+
|
|
177
|
+
Important:
|
|
178
|
+
|
|
179
|
+
- In HTTP control-plane mode, agents should call `memorix_session_start` with `projectRoot` set to the **absolute path of the current workspace or repo root** when that path is available.
|
|
180
|
+
- `projectRoot` is a detection anchor only; Git remains the source of truth for the final project identity.
|
|
181
|
+
- If the client cannot supply a reliable workspace path, HTTP mode should fail closed instead of silently inventing an `untracked/*` project.
|
|
182
|
+
|
|
183
|
+
Typical endpoints:
|
|
184
|
+
|
|
185
|
+
- MCP endpoint: `http://localhost:3211/mcp`
|
|
186
|
+
- Dashboard: `http://localhost:3211`
|
|
187
|
+
|
|
188
|
+
Generic HTTP MCP config:
|
|
189
|
+
|
|
190
|
+
```json
|
|
191
|
+
{
|
|
192
|
+
"mcpServers": {
|
|
193
|
+
"memorix": {
|
|
194
|
+
"transport": "http",
|
|
195
|
+
"url": "http://localhost:3211/mcp"
|
|
196
|
+
}
|
|
197
|
+
}
|
|
198
|
+
}
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
## Supported Environments
|
|
202
|
+
|
|
203
|
+
Memorix is designed for multi-agent and multi-IDE coding workflows. It supports integrations and workflows around:
|
|
204
|
+
|
|
205
|
+
- Cursor
|
|
206
|
+
- Windsurf
|
|
207
|
+
- Claude Code
|
|
208
|
+
- Codex
|
|
209
|
+
- Copilot / VS Code MCP setups
|
|
210
|
+
- Kiro
|
|
211
|
+
- Antigravity
|
|
212
|
+
- OpenCode
|
|
213
|
+
- Trae
|
|
214
|
+
- Gemini CLI
|
|
215
|
+
|
|
216
|
+
The exact integration surface differs by IDE, but the shared memory model remains the same.
|
|
217
|
+
|
|
218
|
+
## Key Capabilities
|
|
219
|
+
|
|
220
|
+
### Persistent Cross-Session Memory
|
|
221
|
+
|
|
222
|
+
Agents can search prior work at session start and continue from real project context instead of asking the user to re-explain.
|
|
223
|
+
|
|
224
|
+
### Cross-Agent Recall
|
|
225
|
+
|
|
226
|
+
Different coding agents can read from the same local memory base, making handoff and tool switching much smoother.
|
|
227
|
+
|
|
228
|
+
### Git-Memory Pipeline
|
|
229
|
+
|
|
230
|
+
Memorix can capture engineering truth from Git and make it searchable as memory instead of raw commit text.
|
|
231
|
+
|
|
232
|
+
### Reasoning Preservation
|
|
233
|
+
|
|
234
|
+
Memorix can store design rationale and trade-offs directly, which is critical for avoiding contradictory future suggestions.
|
|
235
|
+
|
|
236
|
+
### Dashboard / Control Plane
|
|
237
|
+
|
|
238
|
+
The dashboard exposes:
|
|
239
|
+
|
|
240
|
+
- memory source distribution
|
|
241
|
+
- Git Memory views
|
|
242
|
+
- config provenance
|
|
243
|
+
- project identity health
|
|
244
|
+
- retention and session summaries
|
|
245
|
+
- graph visualization
|
|
246
|
+
|
|
247
|
+
### Team Collaboration
|
|
248
|
+
|
|
249
|
+
When running with HTTP transport, Memorix also supports:
|
|
250
|
+
|
|
251
|
+
- agent registry
|
|
252
|
+
- advisory file locks
|
|
253
|
+
- task board
|
|
254
|
+
- agent-to-agent messages
|
|
255
|
+
|
|
256
|
+
## Tool Surface
|
|
257
|
+
|
|
258
|
+
Memorix exposes MCP tools across several groups:
|
|
259
|
+
|
|
260
|
+
### Core Memory
|
|
261
|
+
|
|
262
|
+
- `memorix_store`
|
|
263
|
+
- `memorix_search`
|
|
264
|
+
- `memorix_detail`
|
|
265
|
+
- `memorix_timeline`
|
|
266
|
+
- `memorix_resolve`
|
|
267
|
+
- `memorix_retention`
|
|
268
|
+
- `memorix_transfer`
|
|
269
|
+
|
|
270
|
+
### Session and Reasoning
|
|
271
|
+
|
|
272
|
+
- `memorix_session_start`
|
|
273
|
+
- `memorix_session_end`
|
|
274
|
+
- `memorix_session_context`
|
|
275
|
+
- `memorix_store_reasoning`
|
|
276
|
+
- `memorix_search_reasoning`
|
|
277
|
+
|
|
278
|
+
### Quality and Maintenance
|
|
279
|
+
|
|
280
|
+
- `memorix_consolidate`
|
|
281
|
+
- `memorix_deduplicate`
|
|
282
|
+
- `memorix_formation_metrics`
|
|
283
|
+
- `memorix_promote`
|
|
284
|
+
- `memorix_skills`
|
|
285
|
+
|
|
286
|
+
### Platform and Integrations
|
|
287
|
+
|
|
288
|
+
- `memorix_rules_sync`
|
|
289
|
+
- `memorix_workspace_sync`
|
|
290
|
+
- `memorix_dashboard`
|
|
291
|
+
|
|
292
|
+
### Team Tools
|
|
293
|
+
|
|
294
|
+
- `team_manage`
|
|
295
|
+
- `team_file_lock`
|
|
296
|
+
- `team_task`
|
|
297
|
+
- `team_message`
|
|
298
|
+
|
|
299
|
+
The exact set may evolve, so AI systems should not hard-code stale tool counts.
|
|
300
|
+
|
|
301
|
+
## Optional Enhancements
|
|
302
|
+
|
|
303
|
+
### LLM Quality Mode
|
|
304
|
+
|
|
305
|
+
If configured with an API key, Memorix can use LLMs for:
|
|
306
|
+
|
|
307
|
+
- narrative compression
|
|
308
|
+
- semantic deduplication
|
|
309
|
+
- higher-quality ranking and enrichment
|
|
310
|
+
|
|
311
|
+
### Local Vector Search
|
|
312
|
+
|
|
313
|
+
Memorix works out of the box with BM25/full-text search. It can also use optional local vector providers for better semantic retrieval without requiring cloud embeddings.
|
|
314
|
+
|
|
315
|
+
## Recommended AI Usage Pattern
|
|
316
|
+
|
|
317
|
+
At session start:
|
|
318
|
+
|
|
319
|
+
1. load session context with `memorix_session_start`
|
|
320
|
+
2. in HTTP control-plane mode, pass `projectRoot` = the absolute current workspace or repo-root path when available
|
|
321
|
+
3. if session start cannot resolve the project, retry with the correct path before using project-scoped tools
|
|
322
|
+
4. search relevant recent memory
|
|
323
|
+
5. fetch detail only when needed
|
|
324
|
+
|
|
325
|
+
During work:
|
|
326
|
+
|
|
327
|
+
1. store meaningful decisions, fixes, gotchas, and milestones
|
|
328
|
+
2. resolve memories when tasks are completed
|
|
329
|
+
3. prefer reasoning-rich summaries over raw logs
|
|
330
|
+
|
|
331
|
+
At session end:
|
|
332
|
+
|
|
333
|
+
1. store a concise session summary
|
|
334
|
+
2. include what changed, why, current state, and next steps
|
|
335
|
+
|
|
336
|
+
## When Memorix Is Strongest
|
|
337
|
+
|
|
338
|
+
Memorix is strongest when the task is:
|
|
339
|
+
|
|
340
|
+
- codebase-specific
|
|
341
|
+
- project-memory heavy
|
|
342
|
+
- multi-session
|
|
343
|
+
- multi-agent
|
|
344
|
+
- Git-aware
|
|
345
|
+
- explanation-sensitive
|
|
346
|
+
|
|
347
|
+
It is especially strong for:
|
|
348
|
+
|
|
349
|
+
- "what changed recently?"
|
|
350
|
+
- "why did we choose this?"
|
|
351
|
+
- "what broke here before?"
|
|
352
|
+
- "which commit relates to this behavior?"
|
|
353
|
+
- "what should the next agent know before continuing?"
|
|
354
|
+
|
|
355
|
+
## Core Links
|
|
356
|
+
|
|
357
|
+
- GitHub: https://github.com/AVIDS2/memorix
|
|
358
|
+
- npm: https://www.npmjs.com/package/memorix
|
|
359
|
+
- README: https://github.com/AVIDS2/memorix/blob/main/README.md
|
|
360
|
+
- Setup Guide: https://github.com/AVIDS2/memorix/blob/main/docs/SETUP.md
|
|
361
|
+
- Configuration Guide: https://github.com/AVIDS2/memorix/blob/main/docs/CONFIGURATION.md
|
|
362
|
+
- Git Memory Guide: https://github.com/AVIDS2/memorix/blob/main/docs/GIT_MEMORY.md
|
|
363
|
+
- Architecture: https://github.com/AVIDS2/memorix/blob/main/docs/ARCHITECTURE.md
|
|
364
|
+
- API Reference: https://github.com/AVIDS2/memorix/blob/main/docs/API_REFERENCE.md
|
|
365
|
+
- Changelog: https://github.com/AVIDS2/memorix/blob/main/CHANGELOG.md
|
package/llms.txt
ADDED
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
# Memorix
|
|
2
|
+
|
|
3
|
+
> Open-source cross-agent memory layer for coding agents via MCP.
|
|
4
|
+
|
|
5
|
+
Memorix is an open-source MCP server that gives coding agents persistent, project-aware memory across IDEs and sessions. It is compatible with Cursor, Claude Code, Codex, Windsurf, Gemini CLI, GitHub Copilot, Kiro, OpenCode, Antigravity, and Trae through MCP. It combines three layers in one system:
|
|
6
|
+
|
|
7
|
+
- **Git Memory** for engineering truth from commits
|
|
8
|
+
- **Reasoning Memory** for why decisions were made
|
|
9
|
+
- **Cross-Agent Recall** so multiple IDEs and agents can share the same local memory base
|
|
10
|
+
|
|
11
|
+
## What Memorix Is Best At
|
|
12
|
+
|
|
13
|
+
- Turning `git commit` history into searchable memory with commit provenance and noise filtering
|
|
14
|
+
- Preserving architecture decisions, bug fixes, gotchas, and reasoning across sessions
|
|
15
|
+
- Sharing memory across Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, and Gemini CLI
|
|
16
|
+
- Running a local memory control plane with search, detail, timeline, dashboard, retention, and team workflows
|
|
17
|
+
|
|
18
|
+
## Quick Start
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
npm install -g memorix
|
|
22
|
+
memorix init
|
|
23
|
+
memorix serve
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Memorix uses:
|
|
27
|
+
|
|
28
|
+
- `memorix.yml` for behavior and project settings
|
|
29
|
+
- `.env` for secrets such as API keys
|
|
30
|
+
|
|
31
|
+
For the normal HTTP MCP + dashboard experience:
|
|
32
|
+
|
|
33
|
+
```bash
|
|
34
|
+
memorix background start
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
Use `memorix serve-http --port 3211` only when you want the same HTTP control plane in the foreground for debugging, manual supervision, or a custom port.
|
|
38
|
+
|
|
39
|
+
Generic stdio MCP config:
|
|
40
|
+
|
|
41
|
+
```json
|
|
42
|
+
{
|
|
43
|
+
"mcpServers": {
|
|
44
|
+
"memorix": {
|
|
45
|
+
"command": "memorix",
|
|
46
|
+
"args": ["serve"]
|
|
47
|
+
}
|
|
48
|
+
}
|
|
49
|
+
}
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Generic HTTP MCP config:
|
|
53
|
+
|
|
54
|
+
```json
|
|
55
|
+
{
|
|
56
|
+
"mcpServers": {
|
|
57
|
+
"memorix": {
|
|
58
|
+
"transport": "http",
|
|
59
|
+
"url": "http://localhost:3211/mcp"
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
}
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
In HTTP control-plane mode, agents should call `memorix_session_start` with `projectRoot` set to the **absolute path of the current workspace or repo root** when that path is available. Git remains the source of truth for the final project identity; `projectRoot` is the detection anchor that prevents cross-project drift.
|
|
66
|
+
|
|
67
|
+
## Core Links
|
|
68
|
+
|
|
69
|
+
- Primary AI operator guide: [docs/AGENT_OPERATOR_PLAYBOOK.md](https://github.com/AVIDS2/memorix/blob/main/docs/AGENT_OPERATOR_PLAYBOOK.md)
|
|
70
|
+
- GitHub: [AVIDS2/memorix](https://github.com/AVIDS2/memorix)
|
|
71
|
+
- npm: [memorix](https://www.npmjs.com/package/memorix)
|
|
72
|
+
- Full AI-facing docs: [llms-full.txt](https://github.com/AVIDS2/memorix/blob/main/llms-full.txt)
|
|
73
|
+
- Setup: [docs/SETUP.md](https://github.com/AVIDS2/memorix/blob/main/docs/SETUP.md)
|
|
74
|
+
- Configuration: [docs/CONFIGURATION.md](https://github.com/AVIDS2/memorix/blob/main/docs/CONFIGURATION.md)
|
|
75
|
+
- Git Memory: [docs/GIT_MEMORY.md](https://github.com/AVIDS2/memorix/blob/main/docs/GIT_MEMORY.md)
|
package/package.json
CHANGED
|
@@ -1,101 +1,110 @@
|
|
|
1
|
-
{
|
|
2
|
-
"name": "memorix",
|
|
3
|
-
"version": "1.0.
|
|
4
|
-
"description": "
|
|
5
|
-
"type": "module",
|
|
6
|
-
"sideEffects": false,
|
|
7
|
-
"bin": {
|
|
8
|
-
"memorix": "./dist/cli/index.js"
|
|
9
|
-
},
|
|
10
|
-
"main": "./dist/index.js",
|
|
11
|
-
"types": "./dist/index.d.ts",
|
|
12
|
-
"exports": {
|
|
13
|
-
".": {
|
|
14
|
-
"import": "./dist/index.js",
|
|
15
|
-
"types": "./dist/index.d.ts"
|
|
16
|
-
}
|
|
17
|
-
},
|
|
18
|
-
"files": [
|
|
19
|
-
"dist",
|
|
20
|
-
"README.md",
|
|
21
|
-
"LICENSE",
|
|
22
|
-
"CHANGELOG.md",
|
|
23
|
-
"CLAUDE.md"
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
"
|
|
29
|
-
"
|
|
30
|
-
"
|
|
31
|
-
"
|
|
32
|
-
"
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
"
|
|
38
|
-
"
|
|
39
|
-
"
|
|
40
|
-
"
|
|
41
|
-
"
|
|
42
|
-
"
|
|
43
|
-
"
|
|
44
|
-
"
|
|
45
|
-
"
|
|
46
|
-
"
|
|
47
|
-
"
|
|
48
|
-
"
|
|
49
|
-
"agent-memory",
|
|
50
|
-
"
|
|
51
|
-
"
|
|
52
|
-
"
|
|
53
|
-
"
|
|
54
|
-
"
|
|
55
|
-
"
|
|
56
|
-
"
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
"
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
"@
|
|
79
|
-
"@
|
|
80
|
-
"
|
|
81
|
-
"
|
|
82
|
-
"
|
|
83
|
-
"
|
|
84
|
-
"
|
|
85
|
-
"
|
|
86
|
-
"
|
|
87
|
-
"
|
|
88
|
-
"
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
"
|
|
92
|
-
"
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
"
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
"
|
|
99
|
-
"
|
|
100
|
-
}
|
|
101
|
-
|
|
1
|
+
{
|
|
2
|
+
"name": "memorix",
|
|
3
|
+
"version": "1.0.6",
|
|
4
|
+
"description": "Open-source cross-agent memory layer for coding agents across Cursor, Claude Code, Codex, Windsurf, Gemini CLI, Copilot, Kiro, OpenCode, Antigravity, and Trae via MCP.",
|
|
5
|
+
"type": "module",
|
|
6
|
+
"sideEffects": false,
|
|
7
|
+
"bin": {
|
|
8
|
+
"memorix": "./dist/cli/index.js"
|
|
9
|
+
},
|
|
10
|
+
"main": "./dist/index.js",
|
|
11
|
+
"types": "./dist/index.d.ts",
|
|
12
|
+
"exports": {
|
|
13
|
+
".": {
|
|
14
|
+
"import": "./dist/index.js",
|
|
15
|
+
"types": "./dist/index.d.ts"
|
|
16
|
+
}
|
|
17
|
+
},
|
|
18
|
+
"files": [
|
|
19
|
+
"dist",
|
|
20
|
+
"README.md",
|
|
21
|
+
"LICENSE",
|
|
22
|
+
"CHANGELOG.md",
|
|
23
|
+
"CLAUDE.md",
|
|
24
|
+
"llms.txt",
|
|
25
|
+
"llms-full.txt"
|
|
26
|
+
],
|
|
27
|
+
"scripts": {
|
|
28
|
+
"build": "tsup",
|
|
29
|
+
"dev": "tsup --watch",
|
|
30
|
+
"start": "node dist/index.js",
|
|
31
|
+
"test": "vitest run",
|
|
32
|
+
"test:watch": "vitest",
|
|
33
|
+
"lint": "tsc --noEmit",
|
|
34
|
+
"prepublishOnly": "npm run build && npm test"
|
|
35
|
+
},
|
|
36
|
+
"keywords": [
|
|
37
|
+
"mcp",
|
|
38
|
+
"mcp-server",
|
|
39
|
+
"model-context-protocol",
|
|
40
|
+
"cursor-mcp",
|
|
41
|
+
"windsurf-mcp",
|
|
42
|
+
"claude-code-memory",
|
|
43
|
+
"codex-mcp",
|
|
44
|
+
"copilot-mcp",
|
|
45
|
+
"kiro-mcp",
|
|
46
|
+
"antigravity-mcp",
|
|
47
|
+
"ai-coding-memory",
|
|
48
|
+
"cross-ide-sync",
|
|
49
|
+
"cross-agent-memory",
|
|
50
|
+
"context-persistence",
|
|
51
|
+
"agent-memory",
|
|
52
|
+
"knowledge-graph",
|
|
53
|
+
"workspace-sync",
|
|
54
|
+
"progressive-disclosure",
|
|
55
|
+
"session-memory",
|
|
56
|
+
"vector-search",
|
|
57
|
+
"rules-sync",
|
|
58
|
+
"project-skills"
|
|
59
|
+
],
|
|
60
|
+
"author": "AVIDS2",
|
|
61
|
+
"license": "Apache-2.0",
|
|
62
|
+
"repository": {
|
|
63
|
+
"type": "git",
|
|
64
|
+
"url": "git+https://github.com/AVIDS2/memorix.git"
|
|
65
|
+
},
|
|
66
|
+
"homepage": "https://github.com/AVIDS2/memorix#readme",
|
|
67
|
+
"bugs": {
|
|
68
|
+
"url": "https://github.com/AVIDS2/memorix/issues"
|
|
69
|
+
},
|
|
70
|
+
"funding": {
|
|
71
|
+
"type": "github",
|
|
72
|
+
"url": "https://github.com/sponsors/AVIDS2"
|
|
73
|
+
},
|
|
74
|
+
"engines": {
|
|
75
|
+
"node": ">=20.0.0"
|
|
76
|
+
},
|
|
77
|
+
"dependencies": {
|
|
78
|
+
"@clack/prompts": "^0.9.1",
|
|
79
|
+
"@modelcontextprotocol/sdk": "^1.26.0",
|
|
80
|
+
"@orama/orama": "^3.1.0",
|
|
81
|
+
"@orama/plugin-data-persistence": "^3.1.0",
|
|
82
|
+
"citty": "^0.1.6",
|
|
83
|
+
"cytoscape": "^3.33.1",
|
|
84
|
+
"cytoscape-dagre": "^2.5.0",
|
|
85
|
+
"dagre": "^0.8.5",
|
|
86
|
+
"diff": "^7.0.0",
|
|
87
|
+
"dotenv": "^17.3.1",
|
|
88
|
+
"gpt-tokenizer": "^2.8.0",
|
|
89
|
+
"gray-matter": "^4.0.3",
|
|
90
|
+
"ink": "^6.8.0",
|
|
91
|
+
"js-yaml": "^3.13.1",
|
|
92
|
+
"react": "^19.2.4",
|
|
93
|
+
"remark": "^15.0.1",
|
|
94
|
+
"remark-stringify": "^11.0.0",
|
|
95
|
+
"zod": "^3.24.0"
|
|
96
|
+
},
|
|
97
|
+
"optionalDependencies": {
|
|
98
|
+
"@huggingface/transformers": "^3.0.0",
|
|
99
|
+
"fastembed": "^1.14.4"
|
|
100
|
+
},
|
|
101
|
+
"devDependencies": {
|
|
102
|
+
"@types/diff": "^7.0.0",
|
|
103
|
+
"@types/node": "^22.0.0",
|
|
104
|
+
"@types/react": "^19.2.14",
|
|
105
|
+
"ink-testing-library": "^4.0.0",
|
|
106
|
+
"tsup": "^8.4.0",
|
|
107
|
+
"typescript": "^5.7.0",
|
|
108
|
+
"vitest": "^3.0.0"
|
|
109
|
+
}
|
|
110
|
+
}
|