memgineering 0.13.0 → 0.13.1
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 +16 -0
- package/README.md +85 -38
- package/assets/MEMGINEERING.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,22 @@ language the reader wants. The bilingual rule the monorepo applies to
|
|
|
11
11
|
|
|
12
12
|
## [Unreleased]
|
|
13
13
|
|
|
14
|
+
## [0.13.1] — 2026-08-28
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
|
|
18
|
+
- **The README matches the CLI it ships with.** It had drifted in the ways
|
|
19
|
+
that mislead: "Nothing is uploaded" predated hosted brains (now: nothing is
|
|
20
|
+
uploaded until you `push` or connect one); the brain-resolution order
|
|
21
|
+
omitted the signed-in machine pointer, which outranks every folder rule;
|
|
22
|
+
the command table was missing thirteen verbs, including the entire account
|
|
23
|
+
group; and storage boundaries — the control "Your notes stay yours" is
|
|
24
|
+
about — were absent entirely. Also fixed: the environment table now lists
|
|
25
|
+
`MEMGINEERING_API_URL` and `MEMGINEERING_AGENT_HOME`, the tool list names
|
|
26
|
+
what `setup` actually installs into (Claude Code, Codex, Grok, Gemini CLI),
|
|
27
|
+
and `resurface`'s folder-local ranking signal is described as existing only
|
|
28
|
+
for a brain on this machine. No behaviour changed.
|
|
29
|
+
|
|
14
30
|
## [0.13.0] — 2026-08-28
|
|
15
31
|
|
|
16
32
|
### Added
|
package/README.md
CHANGED
|
@@ -3,9 +3,9 @@
|
|
|
3
3
|
One memory for the AI you connect.
|
|
4
4
|
|
|
5
5
|
Your notes stay in a folder you own. Every agent you use — Claude Code, Codex,
|
|
6
|
-
|
|
7
|
-
of them is there for the next one,
|
|
8
|
-
after that.
|
|
6
|
+
Grok, Gemini CLI, anything that can run a command — reads and writes the same
|
|
7
|
+
brain through one CLI, so what you told one of them is there for the next one,
|
|
8
|
+
tomorrow, and in whatever tool you move to after that.
|
|
9
9
|
|
|
10
10
|
**You do not have to run any of this yourself.** Ask whichever agent you are
|
|
11
11
|
already talking to — "install memgineering and set it up" — and it does the
|
|
@@ -75,14 +75,23 @@ away.
|
|
|
75
75
|
|
|
76
76
|
## Your notes stay yours
|
|
77
77
|
|
|
78
|
-
- **Nothing is uploaded.**
|
|
79
|
-
|
|
78
|
+
- **Nothing is uploaded until you say so.** A brain is a folder on this disk;
|
|
79
|
+
only `push`, or connecting a hosted brain, carries notes to your account. The
|
|
80
|
+
index is derived and lives outside your notes folder; deleting it costs a
|
|
81
|
+
rebuild and nothing else.
|
|
80
82
|
- **Prose is never rewritten.** `revise` only touches the memory block in a
|
|
81
83
|
note's frontmatter. Your paragraphs are yours.
|
|
82
84
|
- **You decide what is read.** `link` shows the actual lines that would be
|
|
83
85
|
stored — not a description of them — before anything is indexed. Notes whose
|
|
84
86
|
content looks like a credential are refused automatically; anything else you
|
|
85
87
|
want left alone goes in `.memgdeny`.
|
|
88
|
+
- **You decide what is never written.** Say "nothing about my health goes in
|
|
89
|
+
here" and the declaration is enforced, not advised:
|
|
90
|
+
`remember "…" --never-store "health, hospital"` records the boundary in your
|
|
91
|
+
own words, and any later write carrying one of them is refused with the word
|
|
92
|
+
and your declaration quoted back — whether or not the agent read anything
|
|
93
|
+
first. Widen it one word at a time with `revise --never-store-add`; retire
|
|
94
|
+
the declaration to lift it.
|
|
86
95
|
- **`memgineering unlink --purge`** removes every trace this tool kept locally.
|
|
87
96
|
|
|
88
97
|
## Progressive reading
|
|
@@ -102,19 +111,23 @@ and read it" in a single call.
|
|
|
102
111
|
|
|
103
112
|
## Several brains
|
|
104
113
|
|
|
105
|
-
A personal one, a team folder that syncs, one per repository
|
|
106
|
-
is decided
|
|
114
|
+
A personal one, a team folder that syncs, one per repository, one in your
|
|
115
|
+
account. Which one answers is decided in this order:
|
|
107
116
|
|
|
108
|
-
1. `--vault <path>`
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
117
|
+
1. an explicit flag — `--vault <path>`, `--brain <name>` (a hosted brain, without
|
|
118
|
+
moving the machine's pointer), or `--local`
|
|
119
|
+
2. the hosted brain this machine is pointed at, when you are signed in
|
|
120
|
+
3. a `.memgineering` pointer, found by walking up from the current directory
|
|
121
|
+
4. the brain the current directory is inside
|
|
122
|
+
5. the only one linked
|
|
112
123
|
|
|
113
124
|
If nothing settles it, memgineering refuses and lists the candidates rather
|
|
114
|
-
than guessing. To bind a directory once — a repository root, say
|
|
125
|
+
than guessing. To bind a directory once — a repository root, say — or to point
|
|
126
|
+
the whole machine at a hosted brain:
|
|
115
127
|
|
|
116
128
|
```bash
|
|
117
129
|
memgineering use ~/brains/work # writes a relative path when it can, so it commits
|
|
130
|
+
memgineering use --brain "work" # this machine now reads that hosted brain
|
|
118
131
|
```
|
|
119
132
|
|
|
120
133
|
## Starting a session
|
|
@@ -123,40 +136,74 @@ memgineering use ~/brains/work # writes a relative path when it can, so it co
|
|
|
123
136
|
memgineering resurface
|
|
124
137
|
```
|
|
125
138
|
|
|
126
|
-
No query. It ranks by what has been recalled
|
|
127
|
-
|
|
128
|
-
|
|
139
|
+
No query. It ranks by what has been recalled before, how recently, and which of
|
|
140
|
+
your base notes have gone unread — a folder-local signal joins in when the
|
|
141
|
+
brain lives on this machine. `memgineering setup` can register it to run
|
|
142
|
+
automatically when a Claude Code session starts.
|
|
129
143
|
|
|
130
144
|
## Commands
|
|
131
145
|
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
|
135
|
-
|
|
|
136
|
-
| `
|
|
137
|
-
| `
|
|
138
|
-
| `
|
|
139
|
-
| `
|
|
140
|
-
| `
|
|
141
|
-
| `
|
|
142
|
-
| `
|
|
143
|
-
| `
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
|
148
|
-
|
|
|
149
|
-
| `
|
|
146
|
+
**Memory — day to day**
|
|
147
|
+
|
|
148
|
+
| | |
|
|
149
|
+
| ----------------- | ----------------------------------------------------- |
|
|
150
|
+
| `recall <query>` | recall memory cards for a question |
|
|
151
|
+
| `open <ref>` | open one memory — by handle, id, path, or exact title |
|
|
152
|
+
| `evidence <ref>` | how much a memory has been used, and why it changed |
|
|
153
|
+
| `remember <text>` | write something down now |
|
|
154
|
+
| `revise <ref>` | change a memory's conclusion |
|
|
155
|
+
| `undo [op]` | take back the last change, or a named one |
|
|
156
|
+
| `resurface` | what is worth having in view, unasked |
|
|
157
|
+
| `rules` | the standing decisions that bind here |
|
|
158
|
+
|
|
159
|
+
**Brain — set up and point**
|
|
160
|
+
|
|
161
|
+
| | |
|
|
162
|
+
| ----------------------------------- | ------------------------------------------------------------------------ |
|
|
163
|
+
| `init <path>` | create a brain, laid out and ready |
|
|
164
|
+
| `onboard` | what to ask so it knows who it belongs to |
|
|
165
|
+
| `link <path>` | read notes you already keep |
|
|
166
|
+
| `use [brain]` | bind this folder — or, with `--brain`, point the machine at a hosted one |
|
|
167
|
+
| `unlink` · `reindex` · `sync-rules` | brain housekeeping |
|
|
168
|
+
| `log` | what changed, and what can still be undone |
|
|
169
|
+
|
|
170
|
+
**Curation — occasional**
|
|
171
|
+
|
|
172
|
+
| | |
|
|
173
|
+
| ----------------------- | --------------------------------------------------- |
|
|
174
|
+
| `retire` · `unretire` | mark a memory no longer current, or current again |
|
|
175
|
+
| `exclude` · `unexclude` | stop reading a note entirely, or resume |
|
|
176
|
+
| `consolidate` | find memories worth merging — reads, writes nothing |
|
|
177
|
+
| `propose <action>` | draft a change for approval — writes no note |
|
|
178
|
+
| `proposals` | review what is waiting — approve, reject, rebase |
|
|
179
|
+
|
|
180
|
+
**Account — optional; everything above works without it**
|
|
181
|
+
|
|
182
|
+
| | |
|
|
183
|
+
| ------------------------------------ | --------------------------------------------------- |
|
|
184
|
+
| `login` · `logout` · `whoami` | the account session on this machine |
|
|
185
|
+
| `brains` | list your hosted brains, and which one answers here |
|
|
186
|
+
| `create` · `rename` · `delete-brain` | make, rename, or delete a hosted brain |
|
|
187
|
+
| `push` · `pull` | carry a brain to your account, and back down again |
|
|
188
|
+
|
|
189
|
+
**System**
|
|
190
|
+
|
|
191
|
+
| | |
|
|
192
|
+
| -------- | -------------------------- |
|
|
193
|
+
| `setup` | install into your agents |
|
|
194
|
+
| `update` | update memgineering itself |
|
|
150
195
|
|
|
151
196
|
Every command takes `--json`.
|
|
152
197
|
|
|
153
198
|
## Environment
|
|
154
199
|
|
|
155
|
-
| |
|
|
156
|
-
| -------------------------- |
|
|
157
|
-
| `MEMGINEERING_HOME` | state and derived index (default `~/.memgineering`)
|
|
158
|
-
| `MEMGINEERING_JSON=1` | force JSON output without the flag
|
|
159
|
-
| `MEMGINEERING_NO_UPDATE=1` | skip the version check for one run
|
|
200
|
+
| | |
|
|
201
|
+
| -------------------------- | ------------------------------------------------------------ |
|
|
202
|
+
| `MEMGINEERING_HOME` | state and derived index (default `~/.memgineering`) |
|
|
203
|
+
| `MEMGINEERING_JSON=1` | force JSON output without the flag |
|
|
204
|
+
| `MEMGINEERING_NO_UPDATE=1` | skip the version check for one run |
|
|
205
|
+
| `MEMGINEERING_API_URL` | hosted brain server (default `https://api.memgineering.com`) |
|
|
206
|
+
| `MEMGINEERING_AGENT_HOME` | where `setup` installs agent files (default: your home) |
|
|
160
207
|
|
|
161
208
|
## A brain that is not on this machine
|
|
162
209
|
|
package/assets/MEMGINEERING.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: memgineering
|
|
3
3
|
description: Use whenever the user refers to something they told you before, asks what was decided, tells you something worth keeping, or settles something that should hold next time. The memory lives in their own folder and outlives this session; check it before answering from guesswork, and write to it when you learn something durable.
|
|
4
4
|
type: skill
|
|
5
|
-
version: 0.13.
|
|
5
|
+
version: 0.13.1
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# memgineering
|
package/package.json
CHANGED