@1presence/bridge 0.3.0 → 0.4.0

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.
Files changed (2) hide show
  1. package/dist/claude.js +14 -5
  2. package/package.json +1 -1
package/dist/claude.js CHANGED
@@ -12,7 +12,7 @@ const sessions_1 = require("./sessions");
12
12
  // Claude Code always loads CLAUDE.md files from cwd upward plus the global
13
13
  // ~/.claude/CLAUDE.md. If the bridge is launched from within a development
14
14
  // repo (e.g. PresenceAI), it would pick up project CLAUDE.md instructions that
15
- // direct it to write to local vault paths and call MemPalace — both wrong in
15
+ // direct it to write to local vault paths and call mempalace — both wrong in
16
16
  // bridge/Local Mode. We run Claude in a dedicated temp dir with a LOCAL MODE
17
17
  // CLAUDE.md that explicitly overrides those behaviors.
18
18
  const BRIDGE_CWD = (0, path_1.join)((0, os_1.tmpdir)(), '1presence-bridge');
@@ -33,11 +33,20 @@ You have NO permission to write files to this machine.
33
33
  All vault reads and writes go through the \`mcp__1presence__*\` MCP tools.
34
34
  Use those tools instead of any local file paths.
35
35
 
36
- ## MemPalace / memory
36
+ ## Memory (memory map / knowledge graph / agent diary)
37
37
 
38
- MemPalace is hosted in the cloud, not locally. If mempalace tools are available
39
- via MCP, use them. If a mempalace call fails with "not initialised", skip it
40
- silently — do NOT attempt to write memory files locally as a fallback.
38
+ The user's memory is hosted in the cloud, not locally. If \`mempalace_*\` tools
39
+ are available via MCP, use them. If a call fails with "not initialised", skip
40
+ it silently — do NOT write memory files locally as a fallback.
41
+
42
+ **User-facing language.** Never say "MemPalace", "memory palace", "memory
43
+ graph", "ChromaDB", "vector database", "embeddings", or "drawer" to the user
44
+ in any context, even casually, even in progress/status updates. The internal
45
+ tool prefix is \`mempalace_\` but the product name does not exist to the user.
46
+ Use "memory map" (wings/rooms view), "knowledge graph" (facts view), "agent
47
+ diary" (session log), or "your memory" (general). Correct: "Indexed in your
48
+ memory map for semantic search." Wrong: "Indexed in MemPalace for semantic
49
+ search."
41
50
 
42
51
  ## Session notes / chat history
43
52
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@1presence/bridge",
3
- "version": "0.3.0",
3
+ "version": "0.4.0",
4
4
  "description": "Run 1Presence on your Mac and use your Claude.ai Pro subscription from any device",
5
5
  "bin": {
6
6
  "1presence-bridge": "dist/index.js"