You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ This project follows [Conventional Commits](https://www.conventionalcommits.org/
9
9
Full release notes with changelogs per version live on the **[GitHub Releases page](https://github.com/Gentleman-Programming/engram/releases)**.
10
10
11
11
GoReleaser generates them automatically from commits, filtering by type:
12
+
12
13
-`feat:` / `fix:` / `refactor:` / `chore:` commits appear in the release notes
13
14
-`docs:` / `test:` / `ci:` commits are excluded from the generated changelog
14
15
@@ -22,6 +23,8 @@ Breaking changes are always marked with a `type:breaking-change` label and docum
22
23
23
24
### Pi package (`pi-engram`)
24
25
26
+
-**fix(plugin):** allow `mem_session_summary` to accept an explicit `project` fallback when automatic project detection is unavailable.
27
+
-**fix(plugin):** fall back to local `.engram/config.json` and surface a clearer version-mismatch diagnostic when the running Engram server lacks `/project/current`.
25
28
-**feat(plugin):** add `gentle-engram` package for Pi marketplace installs, with HTTP event capture, Memory Protocol prompt injection, safe `engram mcp` launcher config, and `pi-engram init` setup helper.
@@ -63,6 +66,7 @@ The `project` argument has been removed from the JSON schemas of 7 MCP write too
63
66
**After:** the project is auto-detected from the server's working directory (cwd). Any `project` argument sent by the LLM is silently discarded.
64
67
65
68
**Migration:**
69
+
66
70
- Remove `project` from write tool calls in your agent's memory protocol.
67
71
- Use `mem_current_project` (new tool) to inspect which project Engram will use before writing.
68
72
- If the cwd is ambiguous (multiple git repos), Engram returns a structured error with `available_projects`. Navigate to one of the repos before writing.
Copy file name to clipboardExpand all lines: docs/AGENT-SETUP.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,12 +35,12 @@ Install Engram's Pi package, the MCP adapter, and Pi MCP config:
35
35
engram setup pi
36
36
```
37
37
38
-
`engram setup pi` runs `pi install npm:gentle-engram@0.1.5` and `pi install npm:pi-mcp-adapter`, then ensures Pi settings contain both packages and writes `mcpServers.engram` in the Pi agent MCP config when no Engram server is already configured. Existing `mcpServers.engram` entries are preserved.
38
+
`engram setup pi` runs `pi install npm:gentle-engram@0.1.7` and `pi install npm:pi-mcp-adapter`, then ensures Pi settings contain both packages and writes `mcpServers.engram` in the Pi agent MCP config when no Engram server is already configured. Existing `mcpServers.engram` entries are preserved.
Copy file name to clipboardExpand all lines: plugin/pi/README.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ Engram includes a terminal UI for browsing sessions, observations, prompts, proj
78
78
## Quick start
79
79
80
80
```bash
81
-
pi install npm:gentle-engram@0.1.5
81
+
pi install npm:gentle-engram@0.1.7
82
82
pi install npm:pi-mcp-adapter
83
83
pi-engram init
84
84
```
@@ -189,7 +189,7 @@ If the binary is missing, Pi keeps running and memory degrades instead of crashi
189
189
190
190
`pi-engram init` writes Pi-owned config in the Pi agent directory:
191
191
192
-
-`settings.json`: ensures `npm:pi-mcp-adapter` and `npm:gentle-engram@0.1.5` are declared.
192
+
-`settings.json`: ensures `npm:pi-mcp-adapter` and `npm:gentle-engram@0.1.7` are declared.
193
193
-`mcp.json`: adds an `engram` MCP server that launches `engram mcp --tools=agent` through a safe Node wrapper with `directTools: false`, so MCP remains available through the gateway without duplicating Pi-native `mem_*` tools.
194
194
195
195
Existing `mcpServers.engram` entries are preserved unless you pass `--force`:
@@ -210,7 +210,7 @@ The HTTP event-capture path mirrors Engram's normal project detection order as c
210
210
4. single child git repo name
211
211
5. current directory basename
212
212
213
-
MCP tool calls still use Engram core's canonical project resolver at call time. For critical repos or monorepos, prefer an explicit `.engram/config.json`:
213
+
MCP tool calls still use Engram core's canonical project resolver at call time. Pi-native tool calls ask the Engram HTTP server for `/project/current`; if that route is missing on an older running server, the adapter falls back to the nearest local `.engram/config.json` and returns a version-mismatch warning. For critical repos or monorepos, prefer an explicit `.engram/config.json`:
214
214
215
215
```json
216
216
{
@@ -220,12 +220,14 @@ MCP tool calls still use Engram core's canonical project resolver at call time.
|`mem_*` tools are missing | Install `pi-mcp-adapter`, run `pi-engram init`, then restart Pi. |
226
+
| Pi cannot find `engram`| Set `ENGRAM_BIN=/absolute/path/to/engram`. |
227
+
| Session capture should use another server | Set `ENGRAM_URL=http://host:7437`. |
228
+
| Existing MCP config was not replaced | Run `pi-engram init --force`. |
229
+
|`mem_current_project` reports `/project/current` unsupported | Restart or upgrade the running `engram serve`; check `ENGRAM_URL`/`ENGRAM_BIN`. If `.engram/config.json` exists, Pi uses it as a temporary fallback. |
230
+
|`mem_session_summary` cannot detect a project | Ask the user which project should receive the summary, then retry `mem_session_summary` with `project: "name"`. |
warning: `Engram server at ${ENGRAM_URL} does not support /project/current; using ${configPath}. Upgrade or restart Engram for canonical project detection.`,
209
+
};
210
+
}
211
+
return{
212
+
cwd,
213
+
error_hint: `${configPath} exists but project_name is missing or empty. Fix the config or pass project explicitly.`,
error_hint: `Engram server at ${ENGRAM_URL} does not support /project/current. Upgrade or restart the running Engram server, verify ENGRAM_URL/ENGRAM_BIN, or pass project explicitly to project-capable memory tools.`,
0 commit comments