@imunitic/synapse 0.0.1-test.0 → 0.0.1-test.1

package/bin/synapse-setup.cjs

@@ -356,7 +356,13 @@ function configureOpencode() {
   const pluginDestDir = path.join(os.homedir(), ".config", "opencode", "plugin");
   const pluginDest = path.join(pluginDestDir, "synapse.js");
   fs.mkdirSync(pluginDestDir, { recursive: true });
-  fs.copyFileSync(pluginSrc, pluginDest);
+  // synapse.js as shipped is a template -- it has no way to compute its own
+  // binary's install path at import time (no CLAUDE_PLUGIN_ROOT-equivalent
+  // for OpenCode plugins), so this bakes the real resolved path in as a
+  // literal, the same absolute path resolveHookBin() already gave the
+  // Claude/Codex hooks.json rendering above.
+  const pluginSource = fs.readFileSync(pluginSrc, "utf8").replace('"__SYNAPSE_HOOK_BIN__"', JSON.stringify(hookBin));
+  fs.writeFileSync(pluginDest, pluginSource);
   console.log(`installed ${pluginDest}`);
 
   const skillCount = copySkills(path.join(os.homedir(), ".config", "opencode", "skill"), opencodeToolNameTransform);

package/harness/opencode/plugin/synapse.js

@@ -36,23 +36,18 @@
 //
 // `synapse-hook`'s own binary path isn't resolved here the usual way --
 // OpenCode plugins get no `${CLAUDE_PLUGIN_ROOT}`-equivalent "where am I
-// installed" value, unlike Claude Code/Codex. Resolves via `SYNAPSE_HOOK_BIN`
-// if set (an override, not a requirement), else the fixed shared install
-// location every harness's setup fetches into (`~/.cache/synapse/bin/
-// synapse-hook`, `XDG_CACHE_HOME`-aware) -- a real, predictable path now that
-// the binary is shared and unsuffixed across harnesses, not a bare name that
-// needed PATH resolution.
+// installed" value, unlike Claude Code/Codex, and an npm install's binary
+// lives inside a per-platform optionalDependency package
+// (node_modules/@imunitic/synapse-{platform}-{arch}/bin/), a path with no
+// fixed location this file could hardcode or compute at import time.
+// `synapse-setup configure opencode` resolves it once, at configure time,
+// and rewrites the literal string below to the real absolute path -- this
+// file as shipped in the npm package is a template, not the copy that
+// actually runs. `SYNAPSE_HOOK_BIN` overrides it if ever needed.
 
 import { spawnSync } from "child_process"
-import { homedir } from "os"
-import { join } from "path"
 
-function defaultHookBin() {
-  const cacheHome = process.env.XDG_CACHE_HOME || join(homedir(), ".cache")
-  return join(cacheHome, "synapse", "bin", "synapse-hook")
-}
-
-const HOOK_BIN = process.env.SYNAPSE_HOOK_BIN || defaultHookBin()
+const HOOK_BIN = process.env.SYNAPSE_HOOK_BIN || "__SYNAPSE_HOOK_BIN__"
 const SESSION_START_MARKER = "[SYNAPSE-SESSION-START]"
 
 function runHook(subcommand, payload) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imunitic/synapse",
-  "version": "0.0.1-test.0",
+  "version": "0.0.1-test.1",
   "description": "Memory for Claude Code, Codex CLI, and OpenCode: a durable Obsidian vault plus a per-repo code graph.",
   "bin": {
     "synapse-setup": "bin/synapse-setup.cjs",