threadnote 1.3.2 → 1.4.0

package/docs/agent-instructions.md

@@ -193,8 +193,8 @@ Use these only when MCP tools are not available:
 threadnote start
 threadnote recall --query "last handoff for this branch"
 threadnote recall --query "durable feature knowledge for this branch"
-threadnote read viking://agent/threadnote/memories/.abstract.md
-threadnote list viking://agent/threadnote/memories --all --recursive
+threadnote read viking://user/example/memories/.abstract.md
+threadnote list viking://user/example/memories --all --recursive
 threadnote remember --kind durable --project example --topic workflow --text "Durable engineering note..."
 threadnote remember --kind durable --project example --topic active-issue --text "Feature knowledge..."
 threadnote remember --replace viking://user/example/memories/durable/projects/example/workflow.md --text "Updated durable engineering note..."

package/docs/index.html

@@ -4,18 +4,18 @@
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
     <meta name="color-scheme" content="dark" />
-    <title>Threadnote — shared local context for development agents</title>
+    <title>Threadnote - stop re-explaining context to coding agents</title>
     <meta
       name="description"
-      content="Threadnote is a safe local workflow for using OpenViking as shared, agent-neutral context for development work — across Codex, Claude, Cursor, and Copilot."
+      content="Threadnote gives Codex, Claude, Cursor, and Copilot one shared local memory for durable decisions, current handoffs, seeded repo docs, skills, and team knowledge."
     />
 
     <link rel="icon" type="image/svg+xml" href="threadnote-logo.svg" />
 
-    <meta property="og:title" content="Threadnote — shared local context for development agents" />
+    <meta property="og:title" content="Threadnote - shared local memory for coding agents" />
     <meta
       property="og:description"
-      content="One shared memory for Codex, Claude, Cursor, and Copilot. Local-first, cross-session, cross-agent."
+      content="Stop re-explaining project context. Fresh agents recall the latest handoff, durable decisions, and team-shared knowledge."
     />
     <meta property="og:image" content="threadnote-logo.svg" />
     <meta property="og:type" content="website" />
@@ -757,7 +757,7 @@
       <a href="#hero" data-label="Intro"><span>Intro</span></a>
       <a href="#problem" data-label="Problem"><span>Problem</span></a>
       <a href="#meet" data-label="Meet threadnote"><span>Meet</span></a>
-      <a href="#vs-instructions" data-label="vs CLAUDE.md / AGENTS.md"><span>vs instructions</span></a>
+      <a href="#vs-instructions" data-label="vs Markdown"><span>vs Markdown</span></a>
       <a href="#how" data-label="How it works"><span>How</span></a>
       <a href="#safety" data-label="Safety model"><span>Safety</span></a>
       <a href="#install" data-label="Install"><span>Install</span></a>
@@ -776,14 +776,14 @@
         <div class="slide-inner">
           <img class="hero-logo" src="threadnote-logo-inverted.svg" alt="" aria-hidden="true" />
           <h1 class="hero-title-gradient">
-            Shared local context<br />for <em class="hero-accent">development agents</em>.
+            Stop re-explaining<br />context to <em class="hero-accent">coding agents</em>.
           </h1>
           <p class="lead">
-            One memory layer Codex, Claude, Cursor, and Copilot all see. Durable feature knowledge, recent handoffs, and
-            team-shared decisions — recallable from any session, on any agent, in any worktree.
+            Threadnote gives Codex, Claude, Cursor, and Copilot one shared local memory for durable decisions, current
+            handoffs, seeded repo docs, reusable skills, and team knowledge.
           </p>
           <div class="cta-row">
-            <span class="pill"><span id="version-tag">v0.6.1</span> · local-first · AGPL-3.0-or-later</span>
+            <span class="pill"><span id="version-tag">v1.3.2</span> · local-first · AGPL-3.0-or-later</span>
           </div>
         </div>
         <div class="scroll-cue">scroll ↓ &nbsp;·&nbsp; <span class="kbd">↓</span> / <span class="kbd">j</span></div>
@@ -801,6 +801,10 @@
           <ul class="flat reveal" style="margin-top: 2rem">
             <li><strong>Conversation history evaporates.</strong> Compaction summarizes; the nuance is lost.</li>
             <li><strong>Each agent has its own memory.</strong> Switching from Codex to Claude means starting over.</li>
+            <li>
+              <strong>Markdown notes are passive.</strong> The agent still has to know which note matters now, whether
+              it is stale, and where to write the next handoff.
+            </li>
             <li>
               <strong>CLAUDE.md/AGENTS.md is per-repo and static.</strong> It can't carry an in-flight feature's design
               decisions across sessions, much less across agents or repos.
@@ -839,10 +843,10 @@
             </div>
             <div class="card reveal">
               <span class="card-kicker">Cross-session</span>
-              <h3>Survives compaction</h3>
+              <h3>More than compaction</h3>
               <p>
-                After the context window fills up, the next turn recalls durable feature memories and the latest handoff
-                instead of relying on the compressed summary alone.
+                Compaction summarizes a conversation. Threadnote stores explicit handoffs and durable memories the next
+                session can recall, inspect, update, archive, or share.
               </p>
             </div>
             <div class="card reveal">
@@ -863,30 +867,64 @@
               </p>
             </div>
           </div>
+
+          <div class="compare reveal" style="margin-top: 2rem">
+            <div class="compare-col">
+              <h3 class="warm">Before Threadnote</h3>
+              <ul class="flat">
+                <li>
+                  <strong>Codex:</strong> asks what changed, rediscovers the test command, and trusts a compacted chat
+                  summary to keep the important caveat.
+                </li>
+                <li>
+                  <strong>Claude Code:</strong> resumes a long debugging thread with the story arc, but not the exact
+                  blocker, command output, or decision that matters.
+                </li>
+              </ul>
+            </div>
+
+            <div class="compare-col">
+              <h3>With Threadnote</h3>
+              <ul class="flat">
+                <li>
+                  <strong>Codex:</strong> recalls the branch handoff and durable feature memory before editing: files
+                  touched, last failing check, design reason, next step.
+                </li>
+                <li>
+                  <strong>Claude Code:</strong> snapshots concrete state before compaction and reads the same memory in
+                  the next session instead of asking the user to reconstruct it.
+                </li>
+              </ul>
+            </div>
+          </div>
         </div>
       </section>
 
       <!-- 4. vs CLAUDE.md / AGENTS.md -->
       <section id="vs-instructions" class="slide">
         <div class="slide-inner">
-          <span class="slide-eyebrow">03 · Why not just CLAUDE.md or AGENTS.md?</span>
-          <h2>Use them. Threadnote is not a replacement.</h2>
+          <span class="slide-eyebrow">03 · Why not just Markdown files?</span>
+          <h2>Use Markdown. Threadnote makes it operational.</h2>
           <p class="lead">
-            They are perfect for stable, canonical, version-controlled rules. They are wrong for living context — what
-            happened in the last session, which branch is mid-refactor, which on-call workaround actually shipped.
+            The source of truth is still plain files on disk. The difference is that agents can recall the right
+            pointer, tell durable knowledge from current handoff state, replace stale notes, and share only what you
+            explicitly publish.
           </p>
 
           <div class="compare">
             <div class="compare-col reveal">
-              <h3 class="warm">CLAUDE.md · AGENTS.md · Cursor rules</h3>
+              <h3 class="warm">Raw .md files</h3>
               <ul class="flat">
-                <li><strong>Where it lives:</strong> in the repo, versioned, shared via PR.</li>
+                <li><strong>Where it lives:</strong> repo docs, personal notes, chat snippets, ad hoc handoffs.</li>
                 <li>
-                  <strong>Best for:</strong> coding standards, test commands, review rules, architecture invariants.
+                  <strong>Best for:</strong> stable repo policy, reviewed architecture docs, human-written references.
                 </li>
-                <li><strong>Read pattern:</strong> loaded into every agent context window in this repo.</li>
-                <li><strong>Edit cost:</strong> human writes; PR review; high friction (which is the point).</li>
-                <li><strong>Lifecycle:</strong> long-lived. Stale entries hurt every session.</li>
+                <li><strong>Read pattern:</strong> humans decide what to paste or agents grep broad folders.</li>
+                <li>
+                  <strong>Edit cost:</strong> no lifecycle; easy to make another note instead of updating the current
+                  one.
+                </li>
+                <li><strong>Failure mode:</strong> stale context quietly looks as authoritative as current context.</li>
               </ul>
             </div>
 
@@ -898,21 +936,25 @@
                   to a team git repo.
                 </li>
                 <li>
-                  <strong>Best for:</strong> feature knowledge, handoffs, branch state, prod-on-call findings, personal
-                  workflow facts.
+                  <strong>Best for:</strong> feature knowledge, handoffs, branch state, prod-on-call findings, skills,
+                  and personal workflow facts.
+                </li>
+                <li>
+                  <strong>Read pattern:</strong> semantic recall returns scoped <code>viking://</code> URIs; only
+                  relevant content enters the context window.
                 </li>
                 <li>
-                  <strong>Read pattern:</strong> recalled on demand; only the relevant URIs enter the context window.
+                  <strong>Edit cost:</strong> agents write and replace one stable <code>project/topic</code>; humans
+                  guide.
                 </li>
-                <li><strong>Edit cost:</strong> agents write; humans guide; low friction by design.</li>
                 <li><strong>Lifecycle:</strong> durable / handoff / archived. Compact in place, never accrete.</li>
               </ul>
             </div>
           </div>
 
           <p class="muted" style="margin-top: 1.5rem">
-            <strong style="color: var(--text)">The split:</strong> put repo policy in the .md files. Put feature
-            history, in-flight task state, handoffs, and personal workflow facts in threadnote.
+            <strong style="color: var(--text)">The split:</strong> put canonical repo policy in checked-in docs. Put
+            living context, in-flight task state, handoffs, and personal workflow facts in Threadnote.
           </p>
         </div>
       </section>
@@ -1098,14 +1140,14 @@
                 <div class="terminal-bar"><span></span><span></span><span></span></div>
                 <pre><span class="cmd">$ curl -fsSL https://raw.githubusercontent.com/Kashkovsky/threadnote/main/scripts/install.sh | sh</span>
 
-<span class="out">Installed threadnote@1.0.0</span>
+<span class="out">Installed threadnote@1.3.2</span>
 <span class="out">Already exists: ~/.local/bin/threadnote</span>
 <span class="out">OpenViking installs into Python; neither uv nor pipx is</span>
 <span class="out">on PATH so threadnote would fall back to `pip install</span>
 <span class="out">--user`, which fails on PEP 668 setups.</span>
 <span class="out">Install uv now? [Y/n] </span><span class="out-strong">Y</span>
 <span class="out">Installing uv via Homebrew…</span>
-<span class="out-strong">OK   openviking 0.3.24 ready · server healthy</span></pre>
+<span class="out-strong">OK   openviking 0.4.4 ready · server healthy</span></pre>
               </div>
               <p class="muted" style="margin-top: 0.75rem; font-size: 0.9rem">
                 Or manually: <code>npm install -g threadnote && threadnote install</code>. On a fresh macOS / modern
@@ -1485,6 +1527,19 @@ threadnote remember \
               </div>
             </div>
 
+            <div class="vignette reveal">
+              <div class="v-say">Isn't this just auto-compaction plus Markdown files?</div>
+              <pre class="v-call">recall_context({query: "&lt;repo&gt; current handoff durable feature memory"})</pre>
+              <pre class="v-response">
+→ active handoff: status · tests · blockers · next step
+→ durable memory: design decisions · API contracts · gotchas</pre
+              >
+              <div class="v-answer">
+                Compaction compresses a conversation. Threadnote stores explicit records with lifecycle, stable URIs,
+                scoped recall, replacement, archiving, and optional team publishing.
+              </div>
+            </div>
+
             <div class="vignette reveal">
               <div class="v-say">Continue where we left off on this branch.</div>
               <pre class="v-call">recall_context({query: "&lt;branch&gt; latest handoff durable feature memory"})</pre>
@@ -1596,7 +1651,7 @@ threadnote doctor --dry-run</code></pre>
           </div>
 
           <p class="colophon">
-            threadnote · AGPL-3.0-or-later · built on OpenViking 0.3.24 · use <span class="kbd">↑</span>
+            threadnote · AGPL-3.0-or-later · built on OpenViking 0.4.4 · use <span class="kbd">↑</span>
             <span class="kbd">↓</span> / <span class="kbd">j</span> <span class="kbd">k</span> to navigate
           </p>
         </div>

package/docs/migration.md

@@ -108,6 +108,12 @@ paths.
    threadnote seed
    ```
 
+   Seeded docs refresh on the next `threadnote seed`/`repair`, which re-runs the
+   secret scan. To let OpenViking auto-refresh them between runs, opt in with
+   `THREADNOTE_SEED_WATCH_INTERVAL=<minutes> threadnote seed`. Watches attach
+   only to original, non-redaction-prone files, since an OpenViking-managed
+   refresh re-ingests the file without Threadnote's per-import secret scan.
+
 7. Inspect and seed shared skills:
 
    ```bash

package/manager/app.js

@@ -7,7 +7,11 @@
   var __getProtoOf = Object.getPrototypeOf;
   var __hasOwnProp = Object.prototype.hasOwnProperty;
   var __commonJS = (cb, mod) => function __require() {
-    return mod || (0, cb[__getOwnPropNames(cb)[0]])((mod = { exports: {} }).exports, mod), mod.exports;
+    try {
+      return mod || (0, cb[__getOwnPropNames(cb)[0]])((mod = { exports: {} }).exports, mod), mod.exports;
+    } catch (e) {
+      throw mod = 0, e;
+    }
   };
   var __export = (target, all2) => {
     for (var name2 in all2)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "threadnote",
-  "version": "1.3.2",
+  "version": "1.4.0",
   "type": "commonjs",
   "main": "dist/threadnote.cjs",
   "description": "Shared local context and handoffs for development agents",