piia-engram 2.9.0__tar.gz
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.
- piia_engram-2.9.0/LICENSE +190 -0
- piia_engram-2.9.0/PKG-INFO +274 -0
- piia_engram-2.9.0/README.md +246 -0
- piia_engram-2.9.0/pyproject.toml +46 -0
- piia_engram-2.9.0/setup.cfg +4 -0
- piia_engram-2.9.0/src/engram_core/__init__.py +6 -0
- piia_engram-2.9.0/src/engram_core/core.py +2420 -0
- piia_engram-2.9.0/src/engram_core/mcp_server.py +634 -0
- piia_engram-2.9.0/src/engram_core/setup_wizard.py +257 -0
- piia_engram-2.9.0/src/piia_engram.egg-info/PKG-INFO +274 -0
- piia_engram-2.9.0/src/piia_engram.egg-info/SOURCES.txt +16 -0
- piia_engram-2.9.0/src/piia_engram.egg-info/dependency_links.txt +1 -0
- piia_engram-2.9.0/src/piia_engram.egg-info/entry_points.txt +2 -0
- piia_engram-2.9.0/src/piia_engram.egg-info/requires.txt +8 -0
- piia_engram-2.9.0/src/piia_engram.egg-info/top_level.txt +1 -0
- piia_engram-2.9.0/tests/test_core.py +649 -0
- piia_engram-2.9.0/tests/test_packaging.py +92 -0
- piia_engram-2.9.0/tests/test_setup_wizard.py +108 -0
|
@@ -0,0 +1,190 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to the Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by the Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding any notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
Copyright 2026 Patdolitse
|
|
179
|
+
|
|
180
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
181
|
+
you may not use this file except in compliance with the License.
|
|
182
|
+
You may obtain a copy of the License at
|
|
183
|
+
|
|
184
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
185
|
+
|
|
186
|
+
Unless required by applicable law or agreed to in writing, software
|
|
187
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
188
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
189
|
+
See the License for the specific language governing permissions and
|
|
190
|
+
limitations under the License.
|
|
@@ -0,0 +1,274 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: piia-engram
|
|
3
|
+
Version: 2.9.0
|
|
4
|
+
Summary: Engram — AI 记忆印记。你的 AI 记忆,本地存储,跨工具共享。
|
|
5
|
+
Author: Engram Contributors
|
|
6
|
+
License: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/Patdolitse/engram
|
|
8
|
+
Project-URL: Repository, https://github.com/Patdolitse/engram
|
|
9
|
+
Project-URL: Bug Tracker, https://github.com/Patdolitse/engram/issues
|
|
10
|
+
Keywords: ai,memory,mcp,knowledge,personal-knowledge,llm
|
|
11
|
+
Classifier: Development Status :: 4 - Beta
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
18
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
19
|
+
Requires-Python: >=3.10
|
|
20
|
+
Description-Content-Type: text/markdown
|
|
21
|
+
License-File: LICENSE
|
|
22
|
+
Requires-Dist: mcp>=1.0
|
|
23
|
+
Requires-Dist: portalocker>=2.0
|
|
24
|
+
Provides-Extra: dev
|
|
25
|
+
Requires-Dist: pytest>=7.0; extra == "dev"
|
|
26
|
+
Requires-Dist: tomli>=2.0; python_version < "3.11" and extra == "dev"
|
|
27
|
+
Dynamic: license-file
|
|
28
|
+
|
|
29
|
+
<div align="center">
|
|
30
|
+
|
|
31
|
+
<img src="assets/social_preview.png" alt="Engram - Local AI memory layer" width="640">
|
|
32
|
+
|
|
33
|
+
# Engram
|
|
34
|
+
|
|
35
|
+
### A local memory layer for AI coding tools
|
|
36
|
+
|
|
37
|
+
**Stop re-explaining yourself every time you switch tools, projects, or sessions.**
|
|
38
|
+
|
|
39
|
+
`Claude Code` | `Codex` | `Cursor` | `MCP compatible` | `100% local`
|
|
40
|
+
|
|
41
|
+
[English](README.md) | [中文](README.zh-CN.md)
|
|
42
|
+
|
|
43
|
+
[](LICENSE)
|
|
44
|
+
[](https://python.org)
|
|
45
|
+
[](https://modelcontextprotocol.io)
|
|
46
|
+
|
|
47
|
+
</div>
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
> **TL;DR:** Engram is an MCP server that gives Claude Code, Codex, and Cursor a persistent identity layer — your profile, preferences, lessons learned, and key decisions stored as local JSON files. One write, every AI reads. 100% local, Apache 2.0.
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
AI coding tools are powerful, but they do not really know you.
|
|
56
|
+
|
|
57
|
+
Every time you switch from Claude Code to Codex, open Cursor, start a new session, or move into a different project, you often have to explain the same things again:
|
|
58
|
+
|
|
59
|
+
- how you prefer to communicate
|
|
60
|
+
- how the AI should approach code
|
|
61
|
+
- which project rules matter
|
|
62
|
+
- which mistakes should not happen again
|
|
63
|
+
- why earlier decisions were made
|
|
64
|
+
|
|
65
|
+
Engram stores that collaboration memory as local files, then exposes it through MCP so different AI tools can read the same user context.
|
|
66
|
+
|
|
67
|
+
The goal is simple: **make every compatible AI tool start from the same understanding of you.**
|
|
68
|
+
|
|
69
|
+
## Why Engram?
|
|
70
|
+
|
|
71
|
+
| Without Engram | With Engram |
|
|
72
|
+
|---|---|
|
|
73
|
+
| Every new session starts from zero | AI tools can load your identity and preferences |
|
|
74
|
+
| Switching tools loses accumulated context | Claude Code, Codex, and Cursor can read the same memory |
|
|
75
|
+
| Project rules live in scattered prompts | Rules and decisions are stored as local assets |
|
|
76
|
+
| Past mistakes get repeated | Lessons learned can follow you across tools |
|
|
77
|
+
| Memory is locked inside one product | Data stays local, editable, and portable |
|
|
78
|
+
|
|
79
|
+
Engram is not another chat app, agent framework, or hosted memory service. It is a small local memory layer that sits underneath the tools you already use.
|
|
80
|
+
|
|
81
|
+
Unlike session-memory tools that remember what happened in a task, Engram stores **who you are** — your identity, preferences, lessons, and decisions — so every AI tool starts from the same understanding of you as a person.
|
|
82
|
+
|
|
83
|
+
## What It Stores
|
|
84
|
+
|
|
85
|
+
Engram can store:
|
|
86
|
+
|
|
87
|
+
- identity and communication preferences
|
|
88
|
+
- coding style and quality standards
|
|
89
|
+
- trust boundaries for AI tools
|
|
90
|
+
- project snapshots
|
|
91
|
+
- lessons learned
|
|
92
|
+
- key technical or product decisions
|
|
93
|
+
- domain knowledge that should be reused later
|
|
94
|
+
|
|
95
|
+
All data is stored under `~/.engram/` as JSON and Markdown files. You can open, edit, back up, or migrate it yourself.
|
|
96
|
+
|
|
97
|
+
## Quick Start
|
|
98
|
+
|
|
99
|
+
```bash
|
|
100
|
+
git clone https://github.com/Patdolitse/engram.git
|
|
101
|
+
cd engram
|
|
102
|
+
pip install -e .
|
|
103
|
+
python demos/setup_engram.py
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
Then configure Engram as an MCP server in your AI coding tool.
|
|
107
|
+
|
|
108
|
+
Example MCP config:
|
|
109
|
+
|
|
110
|
+
```json
|
|
111
|
+
{
|
|
112
|
+
"mcpServers": {
|
|
113
|
+
"engram": {
|
|
114
|
+
"command": "python",
|
|
115
|
+
"args": ["/path/to/engram/src/engram_core/mcp_server.py"]
|
|
116
|
+
}
|
|
117
|
+
}
|
|
118
|
+
}
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
After restarting your MCP-compatible client, a new session can call `get_user_context` to understand your profile, preferences, lessons, and project context.
|
|
122
|
+
|
|
123
|
+
## MCP Tools
|
|
124
|
+
|
|
125
|
+
Engram exposes read, write, project, backup, and compatibility tools through MCP.
|
|
126
|
+
|
|
127
|
+
Common tools include:
|
|
128
|
+
|
|
129
|
+
| Tool | Purpose |
|
|
130
|
+
|---|---|
|
|
131
|
+
| `get_user_context` | Load the complete user context at the start of a session |
|
|
132
|
+
| `get_identity_card` | Export a Markdown identity card for tools without MCP |
|
|
133
|
+
| `get_profile` | Read the user profile |
|
|
134
|
+
| `get_safe_profile` | Read the user profile with restricted fields filtered out |
|
|
135
|
+
| `get_preferences` | Read communication and workflow preferences |
|
|
136
|
+
| `get_trust_boundaries` | Read data access boundaries |
|
|
137
|
+
| `get_quality_standards` | Read quality expectations |
|
|
138
|
+
| `get_lessons` | Read reusable lessons learned |
|
|
139
|
+
| `get_decisions` | Read key decisions and reasons |
|
|
140
|
+
| `get_relevant_knowledge` | Find knowledge relevant to a project |
|
|
141
|
+
| `save_project_snapshot` | Save project context for later sessions |
|
|
142
|
+
| `add_lesson` | Add a lesson learned |
|
|
143
|
+
| `add_decision` | Add a key decision |
|
|
144
|
+
| `bulk_add_lessons` | Add multiple lessons in one call |
|
|
145
|
+
| `bulk_add_decisions` | Add multiple decisions in one call |
|
|
146
|
+
| `ingest_notes` | Parse free-form notes into lessons and decisions |
|
|
147
|
+
| `export_engram` | Export a full backup |
|
|
148
|
+
| `import_engram` | Import a backup |
|
|
149
|
+
| `export_engram_to_openclaw` | Export OpenClaw-compatible files |
|
|
150
|
+
| `import_engram_from_openclaw` | Import OpenClaw-compatible files |
|
|
151
|
+
| `search_knowledge` | Search lessons and decisions by weighted multi-term relevance |
|
|
152
|
+
| `get_health_report` | Knowledge asset health report (duplicates, capacity, warnings) |
|
|
153
|
+
| `get_stale_knowledge` | Find active knowledge that has not been reviewed recently |
|
|
154
|
+
| `get_knowledge_digest` | Summarize counts, recent additions, top accessed items, and domains |
|
|
155
|
+
| `get_related_knowledge` | Follow links between lessons and decisions |
|
|
156
|
+
| `find_similar_knowledge` | Find similar lessons and decisions by content |
|
|
157
|
+
| `export_knowledge_report` | Export a readable Markdown knowledge report |
|
|
158
|
+
| `link_knowledge` | Create a bidirectional link between two knowledge items |
|
|
159
|
+
| `unlink_knowledge` | Remove a bidirectional knowledge link |
|
|
160
|
+
| `update_lesson` | Update a lesson (summary, domain, status) |
|
|
161
|
+
| `archive_lesson` | Mark a lesson as outdated |
|
|
162
|
+
| `update_decision` | Update a decision |
|
|
163
|
+
| `archive_decision` | Mark a decision as outdated |
|
|
164
|
+
|
|
165
|
+
## Data Layout
|
|
166
|
+
|
|
167
|
+
```text
|
|
168
|
+
~/.engram/
|
|
169
|
+
|-- schema_version.json
|
|
170
|
+
|-- identity/
|
|
171
|
+
| |-- profile.json
|
|
172
|
+
| |-- preferences.json
|
|
173
|
+
| |-- quality_standards.json
|
|
174
|
+
| `-- trust_boundaries.json
|
|
175
|
+
|-- knowledge/
|
|
176
|
+
| |-- lessons.json
|
|
177
|
+
| |-- decisions.json
|
|
178
|
+
| `-- domains.json
|
|
179
|
+
|-- projects/
|
|
180
|
+
| `-- {project_id}.json
|
|
181
|
+
|-- exports/
|
|
182
|
+
`-- compat/
|
|
183
|
+
`-- openclaw/
|
|
184
|
+
```
|
|
185
|
+
|
|
186
|
+
## Supported Tools
|
|
187
|
+
|
|
188
|
+
| Tool | Integration | Status |
|
|
189
|
+
|---|---|---|
|
|
190
|
+
| Claude Code | MCP over stdio | Tested |
|
|
191
|
+
| Codex | MCP over stdio | Tested |
|
|
192
|
+
| Cursor | MCP over stdio | Expected to work |
|
|
193
|
+
| Claude Desktop | MCP over stdio | Expected to work |
|
|
194
|
+
| OpenClaw | SOUL.md / MEMORY.md / USER.md import and export | Tested |
|
|
195
|
+
| ChatGPT / Gemini / Kimi | Markdown identity card fallback | Usable |
|
|
196
|
+
|
|
197
|
+
## Comparison
|
|
198
|
+
|
|
199
|
+
| Feature | Engram | Claude Memory | Manual `CLAUDE.md` | Mem0 |
|
|
200
|
+
|---|---|---|---|---|
|
|
201
|
+
| Cross-tool sharing | Yes | Claude only | Tool-specific | Yes |
|
|
202
|
+
| Local storage | Yes | Cloud | Local | Cloud / hosted |
|
|
203
|
+
| Directly editable data | JSON / Markdown | Not visible | Yes | API-based |
|
|
204
|
+
| MCP standard | Yes | Not applicable | Not applicable | Yes |
|
|
205
|
+
| Portable backup | Copy files or export JSON | Limited | Copy files | API export |
|
|
206
|
+
| Model-agnostic | Yes | Claude-focused | Depends on the tool | Yes |
|
|
207
|
+
| Price | Free and open source | Included in subscription | Free | Free / paid tiers |
|
|
208
|
+
|
|
209
|
+
## Built With
|
|
210
|
+
|
|
211
|
+
Engram is a human-directed, AI-assisted open-source project.
|
|
212
|
+
|
|
213
|
+
| Contributor | Role |
|
|
214
|
+
|---|---|
|
|
215
|
+
| [@Patdolitse](https://github.com/Patdolitse) | Creator, product direction, strategy, ownership |
|
|
216
|
+
| Claude Code | Architecture, task planning, code review assistance |
|
|
217
|
+
| Codex | Implementation, testing, documentation assistance |
|
|
218
|
+
|
|
219
|
+
## FAQ
|
|
220
|
+
|
|
221
|
+
**What is Engram?**
|
|
222
|
+
Engram is a local-first MCP server that gives AI coding tools (Claude Code, Codex, Cursor) a persistent identity layer. It stores who you are, how you work, what you have learned, and the decisions you have made — as local JSON files on your machine.
|
|
223
|
+
|
|
224
|
+
**How is Engram different from other AI memory tools?**
|
|
225
|
+
Most AI memory tools store what happened in a session (task context, code changes). Engram stores who you are as a person — your identity, preferences, lessons, and decisions. This identity layer persists across tools, sessions, and projects. Your data is local JSON files you own and can edit directly.
|
|
226
|
+
|
|
227
|
+
**Which AI tools does Engram support?**
|
|
228
|
+
Engram works with any MCP-compatible AI tool: Claude Code, OpenAI Codex, Cursor, Claude Desktop, and others. For tools without MCP support (ChatGPT, Gemini, Kimi), you can export a Markdown identity card and paste it in manually.
|
|
229
|
+
|
|
230
|
+
**How do I install Engram?**
|
|
231
|
+
```bash
|
|
232
|
+
git clone https://github.com/Patdolitse/engram.git
|
|
233
|
+
cd engram && pip install -e .
|
|
234
|
+
python demos/setup_engram.py
|
|
235
|
+
```
|
|
236
|
+
Then add the MCP config and restart your AI tool. The AI will call `get_user_context` automatically at the start of each session.
|
|
237
|
+
|
|
238
|
+
**Does Engram send data to the cloud?**
|
|
239
|
+
No. All data is stored in `~/.engram/` on your local machine. Engram never makes network requests. Your memory is yours.
|
|
240
|
+
|
|
241
|
+
**How many MCP tools does Engram provide?**
|
|
242
|
+
Engram exposes 44 MCP tools covering identity management, lessons learned, key decisions, project snapshots, bulk input, note ingestion, weighted knowledge search, similarity discovery, digesting, reporting, linking, and health checks.
|
|
243
|
+
|
|
244
|
+
**Is Engram free?**
|
|
245
|
+
Yes. Engram is free and open source under the Apache 2.0 license.
|
|
246
|
+
|
|
247
|
+
## Limitations
|
|
248
|
+
|
|
249
|
+
Engram is functional and actively used, but some things it intentionally does not do yet:
|
|
250
|
+
|
|
251
|
+
| Area | Current State | Planned |
|
|
252
|
+
|---|---|---|
|
|
253
|
+
| **File safety** | Atomic JSON writes with a shared portalocker file lock | Broader stress testing |
|
|
254
|
+
| **Access control** | `restricted_fields` filters profile fields from `get_user_context` and `get_safe_profile` | Per-caller ACL blocked by MCP caller identity |
|
|
255
|
+
| **Encryption** | Plaintext JSON — treat like any local file | Optional field encryption (v3.0) |
|
|
256
|
+
| **Caller identity** | MCP protocol doesn't pass tool identity | Blocked by MCP spec |
|
|
257
|
+
| **Concurrent writes** | Protected by file lock + atomic replace for Engram JSON writes | Network-filesystem edge cases not guaranteed |
|
|
258
|
+
|
|
259
|
+
**What this means in practice:**
|
|
260
|
+
- Don't store passwords, API keys, or client PII in Engram
|
|
261
|
+
- Any process with read access to `~/.engram/` can read your data
|
|
262
|
+
- `restricted_fields` reduces what Engram emits in cold-start context, but it is not encryption or a true ACL
|
|
263
|
+
|
|
264
|
+
This is not a warning to avoid Engram — it's an honest description of what it is: a local, plaintext memory layer for personal AI context. For personal use with non-sensitive data, it works well today.
|
|
265
|
+
|
|
266
|
+
## Contributing
|
|
267
|
+
|
|
268
|
+
Contributions, issues, and feedback are welcome.
|
|
269
|
+
|
|
270
|
+
See [CONTRIBUTING.md](CONTRIBUTING.md). Chinese readers can also use [CONTRIBUTING.zh-CN.md](CONTRIBUTING.zh-CN.md).
|
|
271
|
+
|
|
272
|
+
## License
|
|
273
|
+
|
|
274
|
+
[Apache 2.0](LICENSE). Engram is free software. Your memory belongs to you.
|