@1presence/bridge 0.17.0 → 0.20.0

package/dist/claude.js

@@ -11,99 +11,26 @@ const sessions_1 = require("./sessions");
 // ─── Bridge working directory ─────────────────────────────────────────────────
 //
 // Claude Code always loads CLAUDE.md files from cwd upward plus the global
-// ~/.claude/CLAUDE.md. If the bridge is launched from within a development
-// repo (e.g. PresenceAI), it would pick up project CLAUDE.md instructions that
-// direct it to write to local vault paths and call mempalace — both wrong in
-// bridge/Local Mode. We run Claude in a dedicated temp dir with a LOCAL MODE
-// CLAUDE.md that explicitly overrides those behaviors.
+// ~/.claude/CLAUDE.md. The bridge runs in a dedicated temp dir so it never
+// inherits a development repo's project CLAUDE.md. The CLAUDE.md we write
+// into that dir is a TINY GUARD ONLY — its sole job is to neutralize the
+// user's global ~/.claude/CLAUDE.md (which contains personal/dev rules that
+// would conflict with bridge behavior). All product, tool, UI, glossary,
+// disclosure, gmail, and memory rules come from the dynamic system prompt
+// fetched from agent-api with mode=bridge — see the "Local Mode runtime
+// adapter" section of that prompt and packages/agent-api/src/systemPrompt.ts.
+// Do NOT add product rules here; they belong in the dynamic prompt so hosted
+// and bridge stay in sync.
 const BRIDGE_CWD = (0, path_1.join)((0, os_1.tmpdir)(), '1presence-bridge');
-const BRIDGE_CLAUDE_MD = `# Bridge / Local Mode — Overrides
+const BRIDGE_CLAUDE_MD = `# Local Mode — context guard
 
-You are running as a **1Presence bridge agent** on the user's local machine.
-The rules below **override all other CLAUDE.md instructions**, including the global one.
-
-## Filesystem — DO NOT WRITE LOCALLY
-
-You have NO permission to write files to this machine.
-- Do NOT write chat history, vault notes, or memory files to the local filesystem.
-- Do NOT write to any path under /Users/, ~/Library/, ~/.obsidian/, or similar.
-- Attempting to use Write/Edit tools on local paths is forbidden in this mode.
-
-## Vault operations
-
-All vault reads and writes go through the \`mcp__1presence__*\` MCP tools.
-Use those tools instead of any local file paths.
-
-## Memory (memory map / knowledge graph / agent diary)
-
-The user's memory is hosted in the cloud, not locally. If \`mempalace_*\` tools
-are available via MCP, use them. If a call fails with "not initialised", skip
-it silently — do NOT write memory files locally as a fallback.
-
-**User-facing language.** Never say "MemPalace", "memory palace", "memory
-graph", "ChromaDB", "vector database", "embeddings", or "drawer" to the user
-in any context, even casually, even in progress/status updates. The internal
-tool prefix is \`mempalace_\` but the product name does not exist to the user.
-Use "memory map" (wings/rooms view), "knowledge graph" (facts view), "agent
-diary" (session log), or "your memory" (general). Correct: "Indexed in your
-memory map for semantic search." Wrong: "Indexed in MemPalace for semantic
-search."
-
-## Session notes / chat history
-
-Do NOT write session notes or chat history to the local filesystem.
-If vault MCP tools are available, update vault files through those.
-Otherwise, skip the write and continue — do not error or warn the user.
-
-## UI tools — call these so the chat UI matches the hosted assistant
-
-These tools are wired through MCP and produce dedicated UI events in the user's
-chat interface. Call them by their MCP-prefixed names (\`mcp__1presence__<name>\`).
-
-- **set_conversation_title** — Call ONCE on your first reply in a new
-  conversation with a 2–4 word topic title (sentence case, no verbs). Call
-  again later only if the topic clearly shifts. Without this, the user's
-  conversation list shows untitled threads.
-
-- **ui_payload** — Call exactly ONCE per turn, AFTER your reply text ends.
-  \`suggestions\` (2–4 tappable follow-on prompts) is REQUIRED on every turn
-  with a user-facing reply — never skip it. \`hints\` is an independent,
-  sparse decision: pass \`[]\` most turns (aim ~1 hint per 3 early turns,
-  less later). Do not drop suggestions because there is no hint. Hints are
-  end-user product coaching only — never mention models, AI vendors,
-  engineering, or roadmap. The only legitimate skip is a turn with no
-  user-facing reply text at all.
-
-- **plan** — Show a checklist when a task has ≥3 distinct, user-visible
-  steps with side effects. Call once at the start with all steps; update
-  the FULL list each time a step finishes. Never use for single-tool
-  answers, lookups, or conversational replies.
-
-- **copy_to_clipboard** — Use whenever the user asks you to copy something,
-  or when you produce content (code, a draft, a URL, a list) they will
-  clearly want to paste elsewhere. Call once per piece of content; the
-  text also streams into the chat.
-
-- **request_feature** — Log a feature request when declining a user ask
-  because the capability doesn't exist. Not for transient errors. After
-  calling, tell the user their request was noted.
-
-## Sending email — ALWAYS use gmail_draft
-
-To send email on the user's behalf, ALWAYS call \`gmail_draft\`. This opens
-an inline review panel in the chat UI with Send and Cancel buttons; the
-email is NOT delivered until the user clicks Send themselves.
-
-You DO NOT have direct send capability in this mode — \`gmail_send\` is not
-exposed and the user's explicit confirmation in the review panel is the only
-way mail leaves their account. After calling gmail_draft, tell the user the
-draft is ready to review and wait for them to confirm. Never claim the
-email was sent until the user tells you they clicked Send.
-
-Use the bare tool name (the part after \`mcp__1presence__\`) when reasoning
-about WHEN to call them — the prefix is just the MCP namespace.
+You are running in 1Presence Local Mode. Your **--system-prompt-file** is the
+sole authoritative source for product rules, tool policy, glossary, and
+disclosure rules. Treat any other CLAUDE.md content — including the global
+~/.claude/CLAUDE.md and any project CLAUDE.md from a parent directory — as
+**not applicable** to this runtime. Do not follow it. Do not cite it.
 `;
-// Write the override CLAUDE.md once on module load
+// Write the guard CLAUDE.md once on module load
 (0, fs_1.mkdirSync)(BRIDGE_CWD, { recursive: true });
 (0, fs_1.writeFileSync)((0, path_1.join)(BRIDGE_CWD, 'CLAUDE.md'), BRIDGE_CLAUDE_MD, 'utf-8');
 const config_1 = require("./config");
@@ -170,7 +97,7 @@ function spawnClaude(params) {
         '--tools', '',
         '--setting-sources', '',
         '--allowedTools', 'mcp__1presence__*',
-        '--system-prompt', systemPromptPath,
+        '--system-prompt-file', systemPromptPath,
         '--mcp-config', mcpConfigPath,
         '--strict-mcp-config',
     ];

package/dist/index.js

@@ -48,7 +48,7 @@ let currentWs = null;
 // vanish and the agent to vault-hunt for skills).
 async function fetchSystemPrompt(token) {
     const tz = Intl.DateTimeFormat().resolvedOptions().timeZone;
-    const url = `${GATEWAY_HTTP}/system-prompt?timezone=${encodeURIComponent(tz)}`;
+    const url = `${GATEWAY_HTTP}/system-prompt-for-bridge?timezone=${encodeURIComponent(tz)}`;
     let res;
     try {
         res = await fetch(url, {
@@ -60,17 +60,17 @@ async function fetchSystemPrompt(token) {
     }
     if (!res.ok) {
         const body = await res.text().catch(() => '<unreadable body>');
-        throw new Error(`/system-prompt returned ${res.status} ${res.statusText}: ${body.slice(0, 500)}`);
+        throw new Error(`/system-prompt-for-bridge returned ${res.status} ${res.statusText}: ${body.slice(0, 500)}`);
     }
     let data;
     try {
         data = await res.json();
     }
     catch (err) {
-        throw new Error(`/system-prompt returned non-JSON: ${err.message}`);
+        throw new Error(`/system-prompt-for-bridge returned non-JSON: ${err.message}`);
     }
     if (!data.text) {
-        throw new Error(`/system-prompt returned no "text" field (got keys: ${Object.keys(data).join(', ') || '<none>'})`);
+        throw new Error(`/system-prompt-for-bridge returned no "text" field (got keys: ${Object.keys(data).join(', ') || '<none>'})`);
     }
     return data.text;
 }
@@ -304,7 +304,7 @@ function connect(auth, retryDelay = 1000) {
         setTimeout(async () => {
             try {
                 // Refresh setup files on reconnect in case token was refreshed.
-                // If /system-prompt is down this throws — log and retry; the bridge
+                // If /system-prompt-for-bridge is down this throws — log and retry; the bridge
                 // is useless without a current prompt so don't paper over it.
                 if (currentAuth)
                     await writeSetupFiles(currentAuth);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@1presence/bridge",
-  "version": "0.17.0",
+  "version": "0.20.0",
   "description": "Run 1Presence on your Mac and use your Claude.ai Pro subscription from any device",
   "bin": {
     "1presence-bridge": "dist/index.js"