From 16b64cedef33ba53fd2358a07ba35ddb97cff174 Mon Sep 17 00:00:00 2001 From: Sean Robbins Date: Sun, 9 Aug 2026 14:42:22 -0400 Subject: [PATCH 1/6] docs(site): marketing copy pass and accurate release publish recipe Rewrite landing copy for checkpoints, packets, model-down recovery, and durable inbox without AI filler. Fix npm publish token expansion in the release runbook. Clarify Wrangler as the site deploy path. --- docs/guides/release.md | 19 +++-- site/README.md | 6 +- site/public/index.html | 179 +++++++++++++++++++++++------------------ 3 files changed, 119 insertions(+), 85 deletions(-) diff --git a/docs/guides/release.md b/docs/guides/release.md index 7f91201..ac4d3d3 100644 --- a/docs/guides/release.md +++ b/docs/guides/release.md @@ -114,6 +114,10 @@ Optional second token name for CI later: `3notch-cli-publish-gha` (no IP lock; s From the project root, with `package.json` already at the release version: ```bash +# Publish from the tree you intend to ship (usually up-to-date main) +git checkout main && git pull +node -p "require('./package.json').version" # confirm expected version + npm run build npm run release:check @@ -121,26 +125,27 @@ npm run release:check read -rs "NPM_TOKEN?Paste npm token from 1Password: " echo export NPM_TOKEN +test -n "$NPM_TOKEN" || { echo "empty token"; exit 1; } npm_cfg="$(mktemp)" chmod 600 "$npm_cfg" -printf '%s\n' '//registry.npmjs.org/:_authToken=${NPM_TOKEN}' > "$npm_cfg" +# Double quotes required so ${NPM_TOKEN} expands (single quotes write the literal text) +printf '%s\n' "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > "$npm_cfg" export NPM_CONFIG_USERCONFIG="$npm_cfg" -trap 'rm -f -- "$npm_cfg"' EXIT +trap 'rm -f -- "$npm_cfg"; unset NPM_TOKEN' EXIT npm whoami npm publish --access public - -unset NPM_TOKEN +npm view @3notch/cli version npm run release:status -- --require-published ``` What this does: -- Keeps the token out of the project tree and out of your permanent user `.npmrc` if you prefer +- Publishes the current checkout (not whatever happens to be on GitHub unless you pulled) +- Keeps the token out of the project tree and out of a permanent project `.npmrc` - Uses a mode-`600` temp npm userconfig and deletes it on shell exit -- Confirms identity before publish -- Fails the status check until registry `latest` equals `package.json` +- Confirms identity before publish; fails status check until registry `latest` equals `package.json` Dry-run (no registry write): diff --git a/site/README.md b/site/README.md index 5d788a1..9fda906 100644 --- a/site/README.md +++ b/site/README.md @@ -45,6 +45,9 @@ This uses `npx serve` (no install needed). Open the URL, edit `public/index.html ## Deploy to Cloudflare Pages +**Canonical path:** Wrangler → Cloudflare Pages project `3notch`. +There is no GitHub Pages workflow for this site in-repo. If you ever saw a GitHub deploy, it was one-off or external—not the maintained path. + ### One-time setup 1. **Create a Cloudflare account** at https://dash.cloudflare.com (free). @@ -60,9 +63,10 @@ This uses `npx serve` (no install needed). Open the URL, edit `public/index.html ### Ship it -From `site/`: +From `site/` (after copy/version changes are on the branch you want live): ```bash +cd site npm run deploy ``` diff --git a/site/public/index.html b/site/public/index.html index fa0a57a..3738741 100644 --- a/site/public/index.html +++ b/site/public/index.html @@ -4,12 +4,12 @@ 3Notch — Mark your trail. - + - + @@ -17,7 +17,7 @@ - + @@ -27,7 +27,7 @@ "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "3Notch", - "description": "3Notch is an open-source CLI tool that saves AI working state as local, portable checkpoints and packets. When a session hits a rate limit, the model goes down, the context window compacts, or you switch tools, 3Notch preserves the current objective, completed work, decisions, blockers, and next steps so the next session can resume without starting over.", + "description": "3Notch is an open-source CLI and MCP server for local AI working-state checkpoints and portable handoff packets. Use it when a session dies, a model fails, you switch tools, or you need async delivery between agents and repos—without a cloud account or hosted relay.", "applicationCategory": "DeveloperApplication", "operatingSystem": "macOS, Windows, Linux", "url": "https://3notch.dev/", @@ -58,7 +58,7 @@ "name": "How do I save context when switching AI models?", "acceptedAnswer": { "@type": "Answer", - "text": "3Notch creates portable checkpoints that capture your current objective, completed work, decisions, blockers, and next steps. When you switch from one AI tool to another (e.g., Claude to Codex), the outgoing agent writes a checkpoint and the incoming agent reads it to resume with full context. Install with: npm install -g @3notch/cli" + "text": "Write a packet (or continuation checkpoint) with the objective, what finished, what is blocked, and what is next. Import or resume it in the other tool. Install: npm install -g @3notch/cli" } }, { @@ -66,7 +66,7 @@ "name": "How do I recover context after an AI rate limit or session crash?", "acceptedAnswer": { "@type": "Answer", - "text": "With continuation checkpoints enabled, 3Notch saves working state when a session hits a rate limit, the model goes down (overloaded, server error, and related failures), or the context window compacts. When you start a new session, 3Notch offers the latest checkpoint for review and loads it after you approve." + "text": "Enable continuation checkpoints for Claude Code. 3Notch writes a fallback when the session hits a rate limit, model-down failure, or compaction, then offers that checkpoint at the next session start for your approval." } }, { @@ -74,7 +74,7 @@ "name": "What is 3Notch?", "acceptedAnswer": { "@type": "Answer", - "text": "3Notch is a free, open-source CLI tool and MCP server that saves AI coding session context as portable, local Markdown files. It works with Claude Code, Codex, Cursor, ChatGPT, and any MCP-compatible AI tool. Checkpoints are plain Markdown with structured frontmatter — no database, no cloud service, no account required. Everything stays on your machine." + "text": "A local CLI and MCP server for AI working-state checkpoints and portable handoff packets. Markdown on disk, no hosted service, no account. Works with Claude Code, Codex, Cursor, and other tools." } }, { @@ -82,7 +82,7 @@ "name": "Does 3Notch work with Claude Code, Codex, and Cursor?", "acceptedAnswer": { "@type": "Answer", - "text": "Yes. 3Notch is vendor-neutral and works with any AI coding tool. It includes a built-in MCP server for tools that support Model Context Protocol (Claude Code, Claude Desktop, Cursor), and portable .notchpkt archives that can be imported into any tool. Checkpoints are plain Markdown files readable by any agent." + "text": "Yes. Use the MCP server where the client supports it, or pack and import .notchpkt archives. Packets are plain Markdown plus optional artifacts—any agent can read them." } }, { @@ -90,7 +90,7 @@ "name": "Is 3Notch free?", "acceptedAnswer": { "@type": "Answer", - "text": "Yes. 3Notch is completely free, open-source software released under the MIT license. There is no cloud service, no account, no telemetry, and no paid tier. Install it with: npm install -g @3notch/cli" + "text": "Yes. MIT license. No cloud product, no account, no telemetry. npm install -g @3notch/cli" } } ] @@ -451,17 +451,19 @@ /* ── WORKFLOW CARDS ── */ .workflow-grid { - display: grid; grid-template-columns: repeat(3, 1fr); + display: grid; grid-template-columns: repeat(2, 1fr); border: 1px solid var(--line); margin-bottom: 1.25rem; } .workflow-card { padding: 2rem 1.75rem 2rem; background: var(--ink-soft); border-right: 1px solid var(--line); + border-bottom: 1px solid var(--line); display: flex; flex-direction: column; min-height: 280px; } -.workflow-card:last-child { border-right: none; } +.workflow-card:nth-child(2n) { border-right: none; } +.workflow-card:nth-child(n+3) { border-bottom: none; } .workflow-num { font-family: var(--f-mono); font-size: 0.7rem; letter-spacing: 0.18em; color: var(--mark); @@ -485,7 +487,13 @@ .workflow-code .m { color: var(--paper-mute); } @media (max-width: 900px) { .workflow-grid { grid-template-columns: 1fr; } - .workflow-card { border-right: none; border-bottom: 1px solid var(--line); min-height: 0; } + .workflow-card, + .workflow-card:nth-child(2n), + .workflow-card:nth-child(n+3) { + border-right: none; + border-bottom: 1px solid var(--line); + min-height: 0; + } .workflow-card:last-child { border-bottom: none; } } @@ -808,9 +816,9 @@ open source · - works with every AI tool + vendor-neutral · - nothing leaves your machine + stays on your machine
@@ -818,10 +826,10 @@

Mark your
trail.

- Your AI session died. Six hours of decisions, constraints, and working state—gone. The next agent starts from scratch because nothing portable survived the switch. + Rate limited. Model died. Context compacted. You switched tools. The code is still in git—the working state is not. The next session re-learns the objective, the constraints, and what you already tried.

- 3Notch saves the working state your AI tools won't. Local checkpoints that survive rate limits, context compaction, and model switches. Portable packets when context needs to move across tools, repos, or machines. + 3Notch is a local CLI and MCP server for checkpoints and handoff packets. Save selected state, resume after a crash, and move context across tools, repos, or agents—without a cloud account.

@@ -838,13 +846,13 @@

Mark your
trail.

Paste this into your agent -
- Run npm install -g @3notch/cli, then notch --help. Read the installed package README for client configuration before making changes. + Install @3notch/cli, run notch onboard here, enable continuation checkpoints for Claude Code if needed. Use packets for cross-tool or cross-repo handoffs. Read the package README before changing MCP config.
@@ -904,36 +912,36 @@

Mark your
trail.

THE PROBLEM

The code survives. The working state doesn't.

-

Rate limited at 2 AM. Context window compacted mid-refactor. Switched models because the cap hit at the worst moment. Every time, you rebuild from zero—re-explaining the goal, the constraints, what you already tried.

+

Git has the files. It does not have the objective you were mid-way through, the decisions you already made, or the landmines you already stepped on.

-

Your commits, docs, and wiki hold durable knowledge. But the objective you were chasing, the decisions you'd made, the blockers you'd identified, what you'd already verified—that state dies with the session. No AI vendor will fix this. Anthropic won't ship "easily move your context to Codex." OpenAI won't ship "easily move to Claude."

-

A neutral, locally-owned format is the only place this problem gets solved.

+

Vendors optimize for their own product. Claude will not make it easy to hand a live session to Codex. Codex will not make it easy to hand one to Cursor. That is not a bug in any one tool—it is the market structure.

+

3Notch is a neutral, local format for the state that falls between commits: what you were doing, what finished, what is blocked, and what is next. You decide what gets written. Nothing scrapes your chats in the background.

-
Session crashed?
+
Session died
- Pick up where you left off - 3Notch already saved your working state. The next session offers to resume. + Resume from a checkpoint + With Claude Code hooks enabled, 3Notch can write a fallback before the trail goes cold.
-
Switching models?
+
Switching tools
- Take your context with you - The outgoing agent writes what's done, what's blocked, what's next. The incoming agent reads it. + Write a packet, import it + Outgoing agent records the handoff. Incoming agent reads it after you approve.
-
Different tool?
+
Async agents / repos
- Package the handoff - Bundle the relevant files, decisions, and next steps into a portable packet. + Durable inbox + Pack, send to a shared mailbox, forward a text notice, pull and ack on the other side.
@@ -949,15 +957,15 @@

The code survives. The working state do
HOW IT WORKS

Session dies. Context survives.

-

When a session hits a rate limit, the model goes down, or context compacts, 3Notch can save the working state. When you start a new session, it offers to pick up where you left off.

+

Turn on continuation checkpoints for Claude Code. When the session fails for reasons that are not your fault, 3Notch can leave a checkpoint the next session can offer you.

Without 3Notch -

Start over. Every time.

-

Your session crashes at 2 AM. You open a new one, re-explain the project, re-describe what you were building, re-list what's done and what isn't. Forty minutes later you're back where you were—if you remembered everything.

+

Start over from memory.

+

New session. Blank agent. You reconstruct the plan from commits, chat scraps, and whatever you still remember. That reconstruction is slow and incomplete—and you pay for it every time the model flakes.

@@ -982,8 +990,8 @@

Start over. Every time.

With 3Notch -

Resume in seconds.

-

3Notch saved a checkpoint when the last session ended. The new session finds it, shows you what it contains, and picks up with full context after you approve.

+

Offer a checkpoint. You approve.

+

A fallback packet is already on disk: objective, tasks, git state. The next session can surface it once. Nothing loads into the agent until you say yes.

@@ -1014,44 +1022,52 @@

Resume in seconds.

USE CASES
-

Three ways your context breaks. One tool to fix all of them.

+

Four common breaks. Same local format for all of them.

-
Session crashed
-

Rate limited. Compacted. Model went down.

-

Doesn't matter why—with checkpoints enabled, 3Notch already saved where you were. Your next session offers to pick up exactly where this one stopped.

+
Session failed
+

Rate limit, overload, compaction.

+

Claude Code hooks can write a continuation checkpoint from task state and git—including model-down failures, not only rate limits. Next session can offer it once.

$ notch packet list
   auth-refactor  checkpoint
   next: Redis session adapter
-  ✓ ready to resume
+ ✓ ready to review
-
Switching models
-

Moving from Claude to Codex because the cap hit?

-

The outgoing agent writes a checkpoint: what's done, what's blocked, what's next. The incoming agent reads it and confirms before continuing.

- 
$ notch packet show latest
+      
Switching tools

+      
Claude today. Codex tomorrow.

+      
Outgoing agent writes a handoff packet. Incoming agent imports it. No vendor bridge required—Markdown and optional artifacts on disk.

+      
$ notch packet show <id>
   completed: 4 of 6 tasks
   blocked: API schema change
-  next: update client types
-  ✓ portable across tools

+  next: update client types
-
Different tool, different repo
-

Built in Claude Code, need to continue in Cursor?

-

Package the relevant files, decisions, and next steps into a portable packet. The receiving tool picks it up with full context.

- 
$ notch packet pack latest
+      
Files need to travel

+      
Pack a .notchpkt archive.

+      
Hash-verified artifacts for the other machine or repo. Move the archive with scp, git, AirDrop, or whatever you already trust.

+      
$ notch packet pack <id>
   auth-refactor.notchpkt
   3 files · sha256 verified
-  ✓ move it however you want

+  ✓ your transport
+
+
+
Async agents
+

Durable inbox between stores.

+

Two repos share a mailbox root. Send a packed project packet, forward the text delivery notice (chat, Slack, Claude messaging), then pull, import, and ack.

+ 
$ notch send pkt.notchpkt --to local:review
+  notice: pull delivery_…
+$ notch inbox pull … --import
+$ notch inbox ack …
-

You stay in control. A new session offers the checkpoint once and loads it only after you approve. Nothing commits, pushes, or travels automatically.

+

You stay in control. Checkpoints are offered, not force-loaded. Packets do not auto-commit or leave the machine unless you move them. Local addresses are routing labels, not authenticated identity.

@@ -1063,21 +1079,21 @@

Built in Claude Code, need to continue in Cursor?

UNDER THE HOOD
-

Plain Markdown. No database. Completely local.

-

A 3Notch checkpoint is a Markdown file you can read, edit, and version like any other file in your repo. Selected files travel alongside it, hash-verified. Everything stays on your machine unless you move it yourself.

+

Plain Markdown. No database. Local by default.

+

Packets are files under .notch/. You can open them, diff them, and keep them out of git when they should stay private.

- What you'd expect from a CLI tool -

Readable by you. Useful to the next agent.

+ Under the hood +

Readable by you. Usable by the next agent.

    -
  • You control what's saved — only context you or your agent explicitly supply. Nothing runs in the background.
    • -
  • Secret scanning built in — every write is scanned for credentials. Packets land clean or not at all.
    • -
  • Works with any AI tool — Claude Code, Codex, Cursor, ChatGPT, or whatever ships next. MCP server included.
    • -
  • Your transport, your call — move packets via Git, email, AirDrop, Tailscale, or anything else you trust.
    • -
  • Zero dependencies — no SQLite, no native compilation. Pure TypeScript, runs everywhere Node does.
    • +
  • Explicit writes only — you or the agent choose what to save. No chat scraping, no background daemon.
    • +
  • Secret scanning on write — credential-like content is blocked before it lands in a packet.
    • +
  • MCP where it helps — Claude Code, Desktop, Cursor, and other stdio clients; pack/import when MCP is not available.
    • +
  • Your transport — scp, git, AirDrop, Tailscale, a shared mailbox root. 3Notch does not host a relay.
    • +
  • No SQLite, no native addons — TypeScript on Node 20+.
@@ -1118,47 +1134,56 @@

Common questions.

+
+

Create a packet with the objective, completed work, blockers, and next steps—plus files if the other side needs them. Import it in the other tool, or pack a .notchpkt and move it yourself. npm install -g @3notch/cli

+
+
+
+
-

3Notch creates portable checkpoints that capture your current objective, completed work, decisions, blockers, and next steps. When you switch from one AI tool to another—say Claude to Codex—the outgoing agent writes a checkpoint and the incoming agent reads it to resume with full context. One install command: npm install -g @3notch/cli

+

With Claude Code continuation checkpoints enabled, 3Notch can write a fallback on rate limits, model-down failures (overload, server error, and related cases), and compaction. The next session may offer that checkpoint once; you approve before anything is loaded.

-

With continuation checkpoints enabled, 3Notch saves working state on rate limits, model-down failures, and context compaction. When you start a new session, it offers the latest checkpoint for review and loads it after you approve—seconds instead of re-explaining the project.

+

Use the durable inbox: both stores register the same mailbox root, you send a packed project packet, forward the plain-text delivery notice through any channel you already use, then pull/import/ack on the receiver. Local addresses are labels, not auth.

-

Yes. 3Notch is vendor-neutral and works with any AI coding tool. It includes a built-in MCP server for tools that support Model Context Protocol (Claude Code, Claude Desktop, Cursor), and portable .notchpkt archives that can be imported into any tool. Checkpoints are plain Markdown files readable by any agent.

+

Yes. MCP for clients that support it; pack/import for everything else. Packets are Markdown on disk, not a proprietary memory store.

-

Neither. Memory tools help a single AI tool remember more. 3Notch makes working context move between tools. Checkpoints are plain Markdown files with structured frontmatter—no database, no embeddings, no cloud service. You can read, edit, and version them like any other file in your repo.

+

No. Memory tools grow one vendor's context window. 3Notch moves selected working state across sessions and tools as files. No embeddings, no hosted index.

-

Completely free, open-source software under the MIT license. No cloud service, no account, no telemetry, no paid tier. Everything runs locally on your machine.

+

MIT. No SaaS tier, no account, no telemetry. Install from npm and run locally.

@@ -1172,9 +1197,9 @@

Common questions.

- open source · MIT · works everywhere + open source · MIT · local by default

Stop rebuilding
context.

-

One command to install. Works with Claude, Codex, Cursor, and whatever you switch to next.

+

Install once. Use checkpoints when a session dies. Use packets when work has to move.

@@ -1190,12 +1215,12 @@

Stop rebuilding
context.

Paste this into your agent -
-
Run npm install -g @3notch/cli, then notch --help. Read the installed package README for client configuration before making changes.
+
Install @3notch/cli, run notch onboard here, enable continuation checkpoints for Claude Code if needed. Use packets for cross-tool or cross-repo handoffs. Read the package README before changing MCP config.
@@ -1220,8 +1245,8 @@

Stop rebuilding
context.

3Notch
-

Save the working state your AI tools won't.

-
Local. Portable. Open source.
+

Checkpoints and packets for AI working state.

+
Local files. No account. MIT.
From 73e3251989fd03ec7a73b8a7b7291db9a8b86726 Mon Sep 17 00:00:00 2001 From: Sean Robbins Date: Sun, 9 Aug 2026 14:50:42 -0400 Subject: [PATCH 2/6] fix(site): reorganize hero and fix social-proof contrast Put install first in the hero CTA column, tighten left-column hierarchy, and make market-signal attribution readable on dark background. --- site/public/index.html | 169 ++++++++++++++++++++++++++--------------- 1 file changed, 107 insertions(+), 62 deletions(-) diff --git a/site/public/index.html b/site/public/index.html index 3738741..855c351 100644 --- a/site/public/index.html +++ b/site/public/index.html @@ -220,17 +220,25 @@ } .hero-inner { position: relative; } .hero-split { - display: grid; grid-template-columns: 1.15fr 1fr; - gap: 3rem; align-items: center; + display: grid; grid-template-columns: minmax(0, 1.05fr) minmax(18rem, 0.95fr); + gap: 2.75rem 3.25rem; align-items: start; } @media (max-width: 900px) { - .hero-split { grid-template-columns: 1fr; gap: 2rem; } + .hero-split { grid-template-columns: 1fr; gap: 1.75rem; } +} +.hero-copy { max-width: 38rem; } +.hero-cta-col { + display: flex; flex-direction: column; gap: 0.85rem; + position: sticky; top: 5.5rem; +} +@media (max-width: 900px) { + .hero-cta-col { position: static; } } .hero-eyebrow { display: inline-flex; align-items: center; gap: 9px; font-family: var(--f-mono); font-size: 0.66rem; letter-spacing: 0.18em; text-transform: uppercase; - color: var(--paper-dim); margin-bottom: 2rem; + color: var(--paper-dim); margin-bottom: 1.35rem; } .hero-eyebrow .dot { width: 6px; height: 6px; border-radius: 50%; background: var(--mark); @@ -245,18 +253,24 @@ .hero-h1 { font-family: var(--f); font-weight: 600; - font-size: clamp(3.5rem, 9vw, 7rem); + font-size: clamp(3.25rem, 8.5vw, 6.25rem); letter-spacing: -0.045em; line-height: 0.95; - color: var(--paper); margin-bottom: 1.5rem; + color: var(--paper); margin-bottom: 1.25rem; } .hero-h1 .accent { color: var(--mark); } .hero-sub { - font-size: clamp(1.05rem, 1.8vw, 1.35rem); - color: var(--paper-dim); line-height: 1.5; - margin-bottom: 1.25rem; font-weight: 400; + font-size: clamp(1.02rem, 1.55vw, 1.2rem); + color: var(--paper-dim); line-height: 1.55; + margin-bottom: 0.9rem; font-weight: 400; letter-spacing: -0.01em; + max-width: 34rem; } .hero-sub strong { color: var(--paper); font-weight: 500; } +.hero-sub.hero-sub-product { + color: var(--paper-mute); + font-size: clamp(0.95rem, 1.35vw, 1.08rem); + margin-bottom: 1.35rem; +} .install-block { display: flex; flex-direction: column; gap: 0.6rem; @@ -291,7 +305,7 @@ .install-cmd-copy svg { width: 12px; height: 12px; } .agent-prompt { - max-width: 46rem; margin-bottom: 1.5rem; + max-width: none; margin: 0; border: 1px solid var(--line-mid); background: var(--ink-soft); } .agent-prompt-head { @@ -316,9 +330,13 @@ color: var(--paper-mute); line-height: 1.55; } .direct-install { - max-width: 46rem; margin: -0.35rem 0 1.5rem; + max-width: none; margin: 0; display: grid; grid-template-columns: auto 1fr auto; - align-items: center; border: 1px solid var(--line); background: var(--ink); + align-items: center; border: 1px solid var(--line-mid); background: var(--ink-soft); +} +.hero-cta-note { + font-family: var(--f-mono); font-size: 0.62rem; + letter-spacing: 0.08em; color: var(--paper-mute); line-height: 1.5; } .direct-install-label { align-self: stretch; display: flex; align-items: center; @@ -339,7 +357,10 @@ .direct-install-label { grid-column: 1 / -1; min-height: 34px; border-right: none; border-bottom: 1px solid var(--line); } } -.hero-actions { display: flex; align-items: center; gap: 2rem; flex-wrap: wrap; } +.hero-actions { + display: flex; align-items: center; gap: 1.5rem 1.75rem; flex-wrap: wrap; + margin-top: 0.25rem; +} .hero-link { display: inline-flex; align-items: center; gap: 8px; font-family: var(--f-mono); font-size: 0.72rem; @@ -355,9 +376,9 @@ .hero-tags { display: flex; flex-wrap: wrap; gap: 0; - margin-top: 3rem; + margin-top: 2.25rem; border-top: 1px solid var(--line); - padding-top: 1.5rem; + padding-top: 1.25rem; } .hero-tag { font-family: var(--f-mono); font-size: 0.6rem; @@ -370,35 +391,57 @@ .hero-tag svg { width: 16px; height: 16px; color: var(--mark); flex-shrink: 0; } /* ── MARKET SIGNAL ── */ -.market-signal { padding: 2.25rem 0; } +.market-signal { padding: 2.5rem 0; } .market-signal-inner { - display: grid; grid-template-columns: 140px minmax(0, 1fr) 220px; - gap: 2.5rem; align-items: center; + display: grid; grid-template-columns: 140px minmax(0, 1fr) minmax(12rem, 16rem); + gap: 2rem 2.5rem; align-items: start; + padding: 1.75rem 1.75rem 1.75rem 0; + border: 1px solid var(--line); + background: var(--ink-soft); } .market-signal-label { font-family: var(--f-mono); font-size: 0.62rem; color: var(--mark); letter-spacing: 0.18em; text-transform: uppercase; font-weight: 500; + padding-left: 1.5rem; padding-top: 0.2rem; } .market-signal-quote { - margin: 0; font-size: clamp(1.15rem, 2vw, 1.55rem); - line-height: 1.4; letter-spacing: -0.018em; color: var(--paper); - font-weight: 500; + margin: 0; font-size: clamp(1.1rem, 1.9vw, 1.4rem); + line-height: 1.45; letter-spacing: -0.018em; color: var(--paper); + font-weight: 500; padding-right: 0.5rem; } .market-signal-quote::before { content: "\201C"; color: var(--mark); } .market-signal-quote::after { content: "\201D"; color: var(--mark); } .market-signal-source { - font-family: var(--f-mono); font-size: 0.68rem; - line-height: 1.6; color: var(--paper-mute); + font-family: var(--f-mono); font-size: 0.78rem; + line-height: 1.55; color: var(--paper-dim); + padding-right: 1.25rem; border-left: 1px solid var(--line); + padding-left: 1.25rem; } -.market-signal-source a { - color: var(--paper-dim); border-bottom: 1px solid var(--line-mid); - transition: color 0.15s, border-color 0.15s; +.market-signal-name { + display: block; color: var(--paper); font-weight: 500; + font-size: 0.88rem; letter-spacing: -0.01em; margin-bottom: 0.2rem; +} +.market-signal-handle { + display: inline-block; color: var(--paper); + border-bottom: 1px solid var(--line-mid); + margin-bottom: 0.55rem; transition: color 0.15s, border-color 0.15s; +} +.market-signal-handle:hover { color: var(--mark); border-color: var(--mark); } +.market-signal-context { + display: block; color: var(--paper-dim); + font-size: 0.72rem; line-height: 1.5; } -.market-signal-source a:hover { color: var(--mark); border-color: var(--mark); } -.market-signal-source strong { display: block; color: var(--paper); font-weight: 500; } @media (max-width: 800px) { - .market-signal-inner { grid-template-columns: 1fr; gap: 0.8rem; } - .market-signal-source { max-width: 28rem; } + .market-signal-inner { + grid-template-columns: 1fr; gap: 1rem; + padding: 1.25rem 1.25rem 1.4rem; + } + .market-signal-label { padding-left: 0; } + .market-signal-source { + border-left: none; border-top: 1px solid var(--line); + padding: 1rem 0 0; max-width: none; + } + .market-signal-quote { padding-right: 0; } } /* ── SECTION HEADS ── */ @@ -812,58 +855,59 @@
-
- - open source - · - vendor-neutral - · - stays on your machine -
-
-
+
+
+ + open source + · + vendor-neutral + · + local files +
+

Mark your
trail.

- Rate limited. Model died. Context compacted. You switched tools. The code is still in git—the working state is not. The next session re-learns the objective, the constraints, and what you already tried. + Rate limited. Model died. Context compacted. You switched tools. The code is still in git—the working state is not.

-

- 3Notch is a local CLI and MCP server for checkpoints and handoff packets. Save selected state, resume after a crash, and move context across tools, repos, or agents—without a cloud account. +

+ Local CLI and MCP server for checkpoints and handoff packets. Resume after a crash. Move context across tools, repos, or agents—no cloud account.

-
+
How it works - Read the docs + Docs GitHub
-
-
+
+
+ Install + npm install -g @3notch/cli + +
+ +
- Paste this into your agent + Or paste into your agent
- Install @3notch/cli, run notch onboard here, enable continuation checkpoints for Claude Code if needed. Use packets for cross-tool or cross-repo handoffs. Read the package README before changing MCP config. + Install @3notch/cli, run notch onboard in this repo, enable continuation checkpoints for Claude Code if needed. Use packets for cross-tool or cross-repo handoffs.
- -
- Or run - npm install -g @3notch/cli - -
+

No account. Runs on your machine.

@@ -894,11 +938,12 @@

Mark your
trail.

From 4aff08e135613c1439d7ed4ce08c1d21e62a1618 Mon Sep 17 00:00:00 2001 From: Sean Robbins Date: Sun, 9 Aug 2026 14:51:28 -0400 Subject: [PATCH 3/6] fix(site): use relative docs links on the landing page Absolute /docs/ breaks when index.html is opened as a file URL. Point landing Docs CTAs at docs/ and document npm run dev for local preview. --- site/README.md | 2 ++ site/public/index.html | 8 ++++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/site/README.md b/site/README.md index 9fda906..25fbdc0 100644 --- a/site/README.md +++ b/site/README.md @@ -41,6 +41,8 @@ npm run dev This uses `npx serve` (no install needed). Open the URL, edit `public/index.html`, refresh. +**Do not open `public/index.html` via `file://`.** Root-absolute paths on docs pages (`/docs/...`, `/docs/docs.css`) only work when the site is served from a host root (`localhost:4321` or `3notch.dev`). Landing “Docs” links use relative `docs/` so a file open is less broken, but the docs tree still needs a real server. + --- ## Deploy to Cloudflare Pages diff --git a/site/public/index.html b/site/public/index.html index 855c351..b032a5c 100644 --- a/site/public/index.html +++ b/site/public/index.html @@ -838,7 +838,7 @@
How it works Use cases - Docs + Docs GitHub @@ -880,7 +880,7 @@

Mark your
trail.

How it works - Docs + Docs GitHub
@@ -1273,7 +1273,7 @@

Stop rebuilding
context.

View on GitHub - Read the docs + Read the docs
@@ -1308,7 +1308,7 @@

Stop rebuilding
context.

Source
From 6b7687511b02af0d72799ec58405450aba35ff19 Mon Sep 17 00:00:00 2001 From: Sean Robbins Date: Sun, 9 Aug 2026 14:52:53 -0400 Subject: [PATCH 4/6] docs: polish public README and restore production docs URLs Rewrite the GitHub README for a clean public product surface (accurate flows, less hype). Restore absolute /docs/ links for 3notch.dev, and ignore local site/test playground artifacts. --- .gitignore | 8 ++ README.md | 268 ++++++++++++++++------------------------- docs/README.md | 2 +- site/README.md | 2 +- site/public/index.html | 8 +- 5 files changed, 119 insertions(+), 169 deletions(-) diff --git a/.gitignore b/.gitignore index a5eb364..06d281a 100644 --- a/.gitignore +++ b/.gitignore @@ -44,3 +44,11 @@ Desktop.ini .notch/index/ .notch/logs/ .notch/private/ + +# Local playground stores (do not commit personal .notch roots) +# Keep fixtures/ and intentional demo stores tracked separately. + +# Site local artifacts +site/public/test-results/ +site/node_modules/ +site/.wrangler/ diff --git a/README.md b/README.md index a3ebef5..74d7775 100644 --- a/README.md +++ b/README.md @@ -2,263 +2,205 @@ **Save the working state your AI tools won't.** -[**Website →**](https://3notch.dev) · [**Docs →**](https://3notch.dev/docs/) · [**Quickstart →**](https://3notch.dev/docs/quickstart/) · [**npm →**](https://www.npmjs.com/package/@3notch/cli) +[Website](https://3notch.dev) · [Docs](https://3notch.dev/docs/) · [Quickstart](https://3notch.dev/docs/quickstart/) · [npm](https://www.npmjs.com/package/@3notch/cli) [![CI](https://img.shields.io/github/actions/workflow/status/coldlogicAI/3notch/ci.yml?branch=main&style=flat-square)](https://github.com/coldlogicAI/3notch/actions/workflows/ci.yml) [![npm](https://img.shields.io/npm/v/@3notch/cli?style=flat-square)](https://www.npmjs.com/package/@3notch/cli) [![Node](https://img.shields.io/node/v/@3notch/cli?style=flat-square)](https://nodejs.org) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](LICENSE) -Your AI session died — rate limited, context compacted, model went down. Six hours of decisions, constraints, and working state gone. The next agent starts from scratch because nothing portable survived the switch. +Rate limits, model failures, context compaction, tool switches — the code is still in git. The objective, decisions, and next steps often are not. The next session rebuilds that state from scratch. -3Notch is a local CLI and MCP server that saves your working state as portable checkpoints. When a session crashes, the next one picks up where you left off. When you switch tools — Claude to Codex, Cursor to ChatGPT — your context travels with you. When work moves to another repo or machine, you package the handoff. +3Notch is a **local CLI and MCP server** for: -No cloud service. No account. No telemetry. No lock-in. Everything stays on your machine. +- **Continuation checkpoints** — when Claude Code is configured, recover after rate limits, model-down failures, and compaction +- **Portable packets** — hand off selected work across tools, repos, and machines +- **Durable inbox** — async delivery between stores that share a mailbox root ---- - -## Get Started - -Give this to your agent: +No cloud service. No account. No telemetry. Records stay on disk as Markdown (and optional artifacts) under `.notch/`. -> Install @3notch/cli and set up context checkpoints for this repo. When a session crashes or I hit a rate limit, save where I was so the next session can pick up. When I switch tools, package the handoff. +--- -Or install directly: +## Install ```bash npm install -g @3notch/cli notch onboard ``` -Then pick the flow that matches your situation. +Agent prompt (optional): + +> Install @3notch/cli, run `notch onboard` in this repo, and set up continuation checkpoints if I use Claude Code. Use packets for handoffs across tools or repos. Read the package README before changing MCP config. + +--- + +## Common flows -### Session crashed — pick up where you left off +### Resume after a failed session -When a session hits a rate limit or compacts, 3Notch saves your working state automatically. The next session offers to resume: +With [continuation checkpoints](docs/guides/continuation-checkpoints.md) enabled for Claude Code, 3Notch can write a fallback from task state and git when the session hits a rate limit, model-down failure, or compaction. The next session may offer that checkpoint once; you approve before it is loaded. ```bash notch packet list -# Shows your latest checkpoint with objective, completed work, blockers, and next action +notch packet preview ``` -### Switching tools — take your context with you - -Moving from Claude Code to Codex? The outgoing agent writes a checkpoint. The incoming agent reads it: +### Hand off between tools ```bash notch packet create \ --title "Auth refactor checkpoint" \ - --summary "Token validation done, session store migration blocked." \ + --summary "Token validation done; session store migration blocked." \ --next-steps "Implement Redis session adapter" -``` -### Different repo or machine — package the handoff +notch packet preview +# other tool / session imports and continues +``` -Bundle selected files, decisions, and next steps into a portable packet: +### Ship files to another repo or machine ```bash notch packet create \ --title "Brand handoff" \ - --summary "Brand handoff for the launch page." \ - --to-agent codex \ - --to-repo ../brand-site \ + --summary "Assets and layout for the launch page." \ --file mascot.jpg:asset \ --file showcase.html:source \ - --next-steps "Build the launch page using showcase.html as the layout and mascot.jpg in the hero." -``` + --next-steps "Build the launch page from showcase.html and mascot.jpg." -The packet lands as a folder in `.notch/outbox/` with `packet.md`, `manifest.json`, and copied bytes under `artifacts/`. The destination imports it: - -```bash -notch packet import ../source/.notch/outbox//packet.md -notch packet preview +notch packet pack +# move .notchpkt however you prefer, then: +notch packet unpack .notchpkt ``` -### Cross-machine +### Async agents — durable inbox -Pack the folder into a `.notchpkt` archive, move it however you want (scp, iCloud, Tailscale, email, git), unpack on the other side: +Both sides register the same mailbox root, then pack/send and pull/ack: ```bash -notch packet pack -# move .notchpkt to the destination machine -notch packet unpack .notchpkt -``` - -### Async agents or repos — use durable inbox - -When two agents cannot rely on one live chat or shared store, point both at one explicit local mailbox root: - -```bash -# Run once in each store with a unique name and the same root notch inbox init --name review-agent --root /shared/3notch-mailbox +notch packet pack +notch send .notchpkt --to local:review-agent +# forward the printed delivery notice via chat, Slack, etc. -# Pack and send from the source -notch packet pack -notch send .notchpkt --to local:review-agent -notch inbox status --at local:review-agent - -# Verify and import at the receiver notch inbox list notch inbox pull --import notch inbox ack ``` -`notch send` prints an agent-readable delivery notice that can move through Claude cross-session messaging, Slack, email, or any other text channel. The local address is a routing label, not authenticated identity. Deliveries are hashed, validated, scanned, retained after ack, and traced locally. See [Durable inbox](docs/guides/durable-inbox.md). - -### Browser-only chats (fallback) +`local:` addresses are routing labels, not authenticated identity. See [Durable inbox](docs/guides/durable-inbox.md). -Web chats that can't reach local MCP use a clipboard bridge: +### Web chat without MCP ```bash notch prompt --client claude-chat -# paste the prompt into the chat, ask for a packet, copy the result +# paste into the chat, copy the packet back pbpaste | notch packet import - ``` ### Personal capture -When you just want to remember something for yourself: - ```bash -notch mark --summary "Decided to keep browser auth cookie-based" --tags auth +notch mark --summary "Keep browser auth cookie-based" --tags auth ``` --- -## How It Works +## How it works -Checkpoints and packets are plain Markdown files with structured frontmatter. You can read, edit, and version them like anything else in your repo. +1. You or an agent write selected context through the CLI or MCP tools. +2. 3Notch validates, secret-scans, and stores records under `.notch/`. +3. Preview before another agent relies on the content. +4. The next session, tool, or store imports or resumes from that record. -1. You or your agent ask 3Notch to save the current working state. -2. 3Notch validates the record, scans it for secrets, and writes it under `.notch/`. -3. You preview the checkpoint before another tool relies on it. -4. The next session, tool, or repo reads and resumes from it. +Targeting fields (`--to-agent`, `--to-repo`) are intent metadata. Bytes move via your transport (scp, git, AirDrop, Tailscale) or the durable inbox mailbox — not a 3Notch-hosted relay. -Targeting fields (`--to-agent`, `--to-repo`) remain intent metadata. Manual transports move archives directly; durable inbox uses a separate registered `local:` address as its delivery control. +--- ## Commands ```text -notch onboard initialize .notch/ and MCP setup -notch packet create create a checkpoint or packet (--file, --ref, --next-steps) -notch packet import import a packet into .notch/inbox/ -notch packet preview show what an agent will read -notch packet pack produce a .notchpkt archive -notch packet unpack import a .notchpkt archive -notch inbox init/list/status/pull/ack configure and process durable deliveries -notch send --to
send a packed project handoff -notch packet list / show list / inspect packets -notch reply typed reply to a packet -notch mark self-addressed private capture -notch brief / brief create / list / show scoped task briefs -notch seed from private context seeding -notch prompt --client optional copy-paste agent instruction pack -notch scan standalone secret scanner -notch check deterministic corpus integrity checks -notch doctor store diagnostics -notch status store summary -notch mcp serve local stdio MCP server +notch onboard initialize .notch/ and MCP setup +notch packet create create a packet (--file, --ref, --next-steps) +notch packet import import into .notch/inbox/ +notch packet preview show what an agent will read +notch packet pack / unpack .notchpkt archive round-trip +notch packet list / show list / inspect packets +notch inbox init/list/status/pull/ack durable delivery lifecycle +notch send --to
send a packed project handoff +notch reply typed reply to a packet +notch mark self-addressed private capture +notch brief / brief create|list|show scoped task briefs +notch seed from private context seeding +notch prompt --client agent / web-chat instruction packs +notch scan secret scanner +notch check structural corpus checks +notch doctor store diagnostics +notch status store summary +notch mcp serve local stdio MCP server ``` -## MCP - -`notch mcp serve` exposes these tools over local stdio: - -- Read-only: `get_brief`, `list_briefs`, `get_targeted_brief`, `get_packet`, `list_packets`, `list_inbox`, `get_inbox_delivery`, `get_status`, `check_store`, `run_doctor` -- Write: `create_brief`, `create_packet`, `create_mark`, `create_reply`, `create_seed_packet`, `import_packet`, `import_seed_packet`, `inbox_init`, `send_packet`, `pull_inbox_packet`, `ack_inbox_delivery` - -Private records under `.notch/private/` are hidden unless the server starts with `--include-private`. See [docs/guides/mcp-setup.md](docs/guides/mcp-setup.md) for client-specific setup. +--- -## Docs +## MCP -Full index: [docs/README.md](docs/README.md). +`notch mcp serve` over local stdio: -| Goal | Doc | +| | Tools | | --- | --- | -| Move context between repos | [docs/guides/cross-repo-packets.md](docs/guides/cross-repo-packets.md) | -| Move context between tools | [docs/guides/cross-tool-handoff.md](docs/guides/cross-tool-handoff.md) | -| Deliver packets asynchronously | [docs/guides/durable-inbox.md](docs/guides/durable-inbox.md) | -| Carry preferences into a new repo | [docs/guides/private-context-seeding.md](docs/guides/private-context-seeding.md) | -| Brief an agent on scoped work | [docs/guides/targeted-brief-workflow.md](docs/guides/targeted-brief-workflow.md) | -| Set up continuation checkpoints | [docs/guides/continuation-checkpoints.md](docs/guides/continuation-checkpoints.md) | -| Set up MCP clients | [docs/guides/mcp-setup.md](docs/guides/mcp-setup.md) | -| Understand privacy posture | [docs/reference/privacy.md](docs/reference/privacy.md) | -| Understand the security model | [docs/reference/security-story.md](docs/reference/security-story.md) | -| Use the web-chat bridge | [docs/prompts/web-chat-to-project.md](docs/prompts/web-chat-to-project.md) | - -## Boundaries - -3Notch is deliberately narrow. - -- Local files by default. No cloud dependency, no hosted relay, no account system. -- No telemetry. -- No vector database or native database dependency. -- No arbitrary shell execution through MCP. -- Manual transports or the explicit local durable inbox move bytes; 3Notch validates, scans, hashes, and stores them. - -A regression-guard test (`tests/unit/no-deferred-commands.test.ts`) prevents accidental scope creep. - -## Where We Want Help +| **Read** | `get_brief`, `list_briefs`, `get_targeted_brief`, `get_packet`, `list_packets`, `list_inbox`, `get_inbox_delivery`, `get_status`, `check_store`, `run_doctor` | +| **Write** | `create_brief`, `create_packet`, `create_mark`, `create_reply`, `create_seed_packet`, `import_packet`, `import_seed_packet`, `inbox_init`, `send_packet`, `pull_inbox_packet`, `ack_inbox_delivery` | -3Notch is open source because the cross-vendor context problem can only be solved neutrally. These are known gaps where contributor input is welcome: +Private records under `.notch/private/` stay hidden unless the server starts with `--include-private`. Client setup: [docs/guides/mcp-setup.md](docs/guides/mcp-setup.md). -**Reaching more surfaces** -- **Web-chat ingest via custom connectors / remote MCP.** An optional HTTP/SSE MCP mode a user wires to Claude.ai via Anthropic's custom-connector flow plus a user-controlled tunnel (Tailscale, Cloudflare). No hosted relay. -- **Onboarding for additional clients** — Gemini CLI, future MCP-capable agents. -- **Mobile / voice intake.** -- **Claude Code → web-chat sharing** (reverse of the current bridge). - -**Moving packets between machines and people** -- **Hosted authenticated transport** that preserves the durable-inbox CLI/MCP contract without putting accounts or network listeners in the local core. -- **Cross-machine transport recipes** for Tailscale, iCloud, Syncthing, git, scp/rsync — opinionated adapter docs and honest sync guarantees. -- **Cross-user / teammate workflows** — conventions for handing packets through whatever channel a team already uses. +--- -**Distribution polish** -- **DXT packaging** for one-click Claude Desktop install. -- **Notarized / signed installers.** +## Documentation -**Capture ergonomics** -- **Agent prompt packs / skills** that wrap "save artifact to disk, then `create_packet`" for specific clients. -- **Per-language / per-framework brief templates.** +| Topic | Guide | +| --- | --- | +| Index | [docs/README.md](docs/README.md) | +| Cross-repo packets | [docs/guides/cross-repo-packets.md](docs/guides/cross-repo-packets.md) | +| Cross-tool handoff | [docs/guides/cross-tool-handoff.md](docs/guides/cross-tool-handoff.md) | +| Durable inbox | [docs/guides/durable-inbox.md](docs/guides/durable-inbox.md) | +| Continuation checkpoints | [docs/guides/continuation-checkpoints.md](docs/guides/continuation-checkpoints.md) | +| MCP setup | [docs/guides/mcp-setup.md](docs/guides/mcp-setup.md) | +| Privacy | [docs/reference/privacy.md](docs/reference/privacy.md) | +| Security | [docs/reference/security-story.md](docs/reference/security-story.md) | +| Releases (maintainers) | [docs/guides/release.md](docs/guides/release.md) | + +Website docs mirror: [https://3notch.dev/docs/](https://3notch.dev/docs/). -**Surfaces on top of the stable substrate** -- **Reply-surfacing UX patterns.** The schema (`replyTo`, `replyType`, `status`) is shipped; the surfacing layer is deferred so contributors can experiment. -- **Wiki / browse / graph views** over `relationships.json`. Out of core by design; contributor surfaces welcome. -- **Additional `notch check` rules** — contribute once you've hit the pain. +--- -**Hardening** -- **Encryption at rest** for `.notch/private/`. -- **Scanner rule contributions** — org-specific, industry-specific, or platform-specific patterns. +## Boundaries -If you're considering a contribution, open an issue first so we can align on scope. +- Local files by default — no hosted relay, account system, or telemetry +- No vector DB / native DB dependency +- No arbitrary shell execution through MCP +- You move bytes; 3Notch validates, scans, hashes, and stores them -## Repo Structure +Regression guard: `tests/unit/no-deferred-commands.test.ts`. -``` -src/ CLI, core services, MCP server, schemas, types -tests/ unit, CLI, MCP, schema, e2e tests + fixtures -fixtures/ demo .notch/ stores used by docs and e2e tests -docs/ guides, reference, agent prompts, archived plans -.github/ CI workflow, issue templates, PR template -``` +--- -For internal architecture (record types, store layout, services), see [docs/archived-plans/v1/3notch-v1-technical-spec.md](docs/archived-plans/v1/3notch-v1-technical-spec.md). +## Contributing -## Development +Prefer opening an issue before large features. See open issues and [CONTRIBUTING.md](CONTRIBUTING.md). ```bash -git clone +git clone https://github.com/coldlogicAI/3notch.git cd 3notch npm install -npm run lint -npm run type-check -npm run build -npm test -npm run test:e2e -node dist/cli/index.js --help +npm run lint && npm run type-check && npm run build +npm test && npm run test:e2e +npm run release:check ``` -See [CONTRIBUTING.md](CONTRIBUTING.md) for the full contributor loop, including a working cross-repo demo you can run from a fresh clone. +See [CONTRIBUTING.md](CONTRIBUTING.md). + +Architecture reference (historical but still useful): [docs/archived-plans/v1/3notch-v1-technical-spec.md](docs/archived-plans/v1/3notch-v1-technical-spec.md). + +--- ## License diff --git a/docs/README.md b/docs/README.md index 9d6187b..72688a3 100644 --- a/docs/README.md +++ b/docs/README.md @@ -13,7 +13,7 @@ Task-shaped how-tos for the main flows. - [Targeted brief workflow](guides/targeted-brief-workflow.md) — scoped task briefs vs cross-boundary packets. - [MCP setup](guides/mcp-setup.md) — server flags, available tools, agent instruction packs. - [Continuation checkpoints](guides/continuation-checkpoints.md) — opt-in Claude task aggregation, compaction fallback, model-down StopFailure recovery, and resume confirmation. -- [Release](guides/release.md) — version surfaces, manual npm publish (token + temp config), and release-check automation. +- [Release](guides/release.md) — maintainer version surfaces, publish recipe, and release-check. ## Reference diff --git a/site/README.md b/site/README.md index 25fbdc0..0ac0b04 100644 --- a/site/README.md +++ b/site/README.md @@ -41,7 +41,7 @@ npm run dev This uses `npx serve` (no install needed). Open the URL, edit `public/index.html`, refresh. -**Do not open `public/index.html` via `file://`.** Root-absolute paths on docs pages (`/docs/...`, `/docs/docs.css`) only work when the site is served from a host root (`localhost:4321` or `3notch.dev`). Landing “Docs” links use relative `docs/` so a file open is less broken, but the docs tree still needs a real server. +**Preview with `npm run dev`, not by opening HTML as a file.** The site uses root-absolute paths (`/docs/`, `/docs/docs.css`) so production and `serve` behave the same. `file://` will break those links. --- diff --git a/site/public/index.html b/site/public/index.html index b032a5c..855c351 100644 --- a/site/public/index.html +++ b/site/public/index.html @@ -838,7 +838,7 @@
How it works Use cases - Docs + Docs GitHub @@ -880,7 +880,7 @@

Mark your
trail.

How it works - Docs + Docs GitHub
@@ -1273,7 +1273,7 @@

Stop rebuilding
context.

View on GitHub - Read the docs + Read the docs
@@ -1308,7 +1308,7 @@

Stop rebuilding
context.

Source
From 3707872289744aa9cb7c368df67bf146ea289b9b Mon Sep 17 00:00:00 2001 From: Sean Robbins Date: Sun, 9 Aug 2026 14:58:43 -0400 Subject: [PATCH 5/6] docs(site): SEO/GEO pass and honest resume demo Expand meta, WebSite/SoftwareApplication/FAQ JSON-LD, and sitemap lastmod for search and answer engines. Soften the checkpoint demo to chat confirmation (not a fake y/n UI) and use a 20-minute recovery claim. --- site/public/index.html | 103 +++++++++++++++++++++++++++++++--------- site/public/robots.txt | 3 ++ site/public/sitemap.xml | 22 ++++----- 3 files changed, 94 insertions(+), 34 deletions(-) diff --git a/site/public/index.html b/site/public/index.html index 855c351..15bddc6 100644 --- a/site/public/index.html +++ b/site/public/index.html @@ -3,36 +3,64 @@ -3Notch — Mark your trail. - +3Notch — Local AI checkpoints and portable handoff packets + + + + - - + + + + + - - + + + - + +