Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

Merge pull request #250 from lhzapata/fix/claude-desktop-msix-config-path

Fabio Akita12cd85cec0d0
diff --cc CHANGELOG.md
index d485707d,45aa08c2..d68bddde
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -14,24 -14,20 +14,37 @@@ and this project adheres to [Semantic V
the local SQLite index directly, so every CLI command is a thin HTTP
client of the running server; the command now requires a reachable
server and no longer works against an offline data directory.
+- Managed workstream support for Grok Build CLI: `ai-memory run grok` (alias
+ `grok-build`) creates fresh sessions with a wrapper-generated `--session-id`,
+ resumes linked sessions with `--resume`, maps wrapper `--yolo` onto Grok's
+ native `--yolo`/`--always-approve`, and delivers the bounded workstream
+ context packet through Grok's native `--rules` flag (system-prompt append,
+ acknowledged only after the child spawns). Transcript import reads
+ `$GROK_HOME/sessions/*/*/chat_history.jsonl` read-only with a
+ prefix-validated cursor and content-hash event ids so rewind-driven journal
+ rewrites cannot duplicate history; system prompts and encrypted reasoning
+ are excluded as loss annotations, as are the harness-injected `<user_info>`
+ and `<system-reminder>` blocks Grok stores inside `user` records (project
+ instructions, the skills catalogue, and connected MCP servers), which would
+ otherwise leak harness internals into the portable ledger and evict real
+ conversation from the startup packet budget. Discovery
+ matches checkouts through `summary.json`'s recorded `info.cwd` and honors
+ `GROK_HOME`. Grok stays out of the bare-mode automatic pool. Verified
+ against Grok Build CLI v0.2.111 ([#237]).
+ ### Fixed
+ - `install-mcp --client claude-desktop` now detects an MSIX-packaged
+ Claude Desktop on Windows and writes to its virtualized
+ `AppData\Local\Packages\Claude_<id>\LocalCache\Roaming\Claude\claude_desktop_config.json`
+ instead of the plain `%APPDATA%\Claude\` path. Previously this
+ silently wrote a config file the running app ignored, so the MCP
+ server never appeared after restart. The detector uses Windows'
+ resolved local and roaming app-data roots, prefers an existing config
+ when multiple package directories exist, and fails with an explicit
+ `--config-file` recovery instruction when the active package is
+ ambiguous. Unpackaged installs keep resolving to the plain path.
+ (#250)
+
## [1.18.0] - 2026-07-23
### Added