-
Notifications
You must be signed in to change notification settings - Fork 38
Expand file tree
/
Copy pathllms.txt
More file actions
75 lines (56 loc) · 2.66 KB
/
llms.txt
File metadata and controls
75 lines (56 loc) · 2.66 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
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
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
# Memorix
> Open-source cross-agent memory layer for coding agents via MCP.
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:
- **Git Memory** for engineering truth from commits
- **Reasoning Memory** for why decisions were made
- **Cross-Agent Recall** so multiple IDEs and agents can share the same local memory base
## What Memorix Is Best At
- Turning `git commit` history into searchable memory with commit provenance and noise filtering
- Preserving architecture decisions, bug fixes, gotchas, and reasoning across sessions
- Sharing memory across Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, and Gemini CLI
- Running a local memory control plane with search, detail, timeline, dashboard, retention, and team workflows
## Quick Start
```bash
npm install -g memorix
memorix init
memorix serve
```
Memorix uses:
- `memorix.yml` for behavior and project settings
- `.env` for secrets such as API keys
For the normal HTTP MCP + dashboard experience:
```bash
memorix background start
```
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.
Generic stdio MCP config:
```json
{
"mcpServers": {
"memorix": {
"command": "memorix",
"args": ["serve"]
}
}
}
```
Generic HTTP MCP config:
```json
{
"mcpServers": {
"memorix": {
"transport": "http",
"url": "http://localhost:3211/mcp"
}
}
}
```
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.
## Core Links
- Primary AI operator guide: [docs/AGENT_OPERATOR_PLAYBOOK.md](https://github.com/AVIDS2/memorix/blob/main/docs/AGENT_OPERATOR_PLAYBOOK.md)
- GitHub: [AVIDS2/memorix](https://github.com/AVIDS2/memorix)
- npm: [memorix](https://www.npmjs.com/package/memorix)
- Full AI-facing docs: [llms-full.txt](https://github.com/AVIDS2/memorix/blob/main/llms-full.txt)
- Setup: [docs/SETUP.md](https://github.com/AVIDS2/memorix/blob/main/docs/SETUP.md)
- Configuration: [docs/CONFIGURATION.md](https://github.com/AVIDS2/memorix/blob/main/docs/CONFIGURATION.md)
- Git Memory: [docs/GIT_MEMORY.md](https://github.com/AVIDS2/memorix/blob/main/docs/GIT_MEMORY.md)