From 477bb807fc80d263f13be80ce4aa630607e24d13 Mon Sep 17 00:00:00 2001 From: Paperclip Agent Date: Thu, 29 Oct 2026 06:03:09 +0000 Subject: [PATCH] faq: tighten three claims in the objections draft E1 self-contained (no /agents completeness promise), E4 drops the held remote-pane sentence, E8 names crash reporting. Page patch regenerated; still not applied. Source issue: FRE-326. Co-Authored-By: Paperclip --- marketing/drafts/faq-from-objections.md | 37 ++++++++++++------------- marketing/drafts/faq-page.patch | 8 +++--- 2 files changed, 22 insertions(+), 23 deletions(-) diff --git a/marketing/drafts/faq-from-objections.md b/marketing/drafts/faq-from-objections.md index f5e4a7d..96d9c3d 100644 --- a/marketing/drafts/faq-from-objections.md +++ b/marketing/drafts/faq-from-objections.md @@ -81,22 +81,21 @@ check. > sessions, finished turns and errors appear in the island, but when Cursor asks for permission the > prompt stays in Cursor. That is deliberate — Cursor blocks the action when a permission hook runs > and prints nothing, so gating it would override Cursor's own prompts. Other agents do hand the -> decision to The Nook, so a tool call waits and you tap Allow or Deny from the card. `/agents` lists -> which is which for every agent. One limit: `cursor-agent -p` one-shot runs send no turn end, so -> they appear but do not get a completion card. +> decision to The Nook, so a tool call waits and you tap Allow or Deny from the card. One limit: +> `cursor-agent -p` one-shot runs send no turn end, so they appear but do not get a completion card. - **Question source:** FRE-326, 2026-10-29 (*"does it work with Cursor?"*); NOOK-643, 2026-10-20 (*"No permission hook is installed, deliberately: Cursor blocks the action when a permission hook prints nothing…"*). -- **Claim:** agent gating is per-agent; Cursor is watch-only; `/agents` carries the matrix. +- **Claim:** agent gating is per-agent; Cursor is watch-only. - **Audience:** the buyer whose agent is not Claude Code. - **Channel:** `/faq`, plus the same answer in any FAQ structured data. - **Owner:** CMO writes; CTO confirms. - **Date:** CTO confirmation 2026-11-03; publish 2026-11-06. - **Must be true:** at the shipped commit, Cursor still reads `.missing(.approvals)` with the same reason, and `.available(.sessions)`, `.available(.completion)` and `.available(.errors)` as stated - (`AgentRegistry.swift:524-552`); `/agents` adds Cursor (and Kimi) in the same edit so the two pages - cannot disagree. If either changes, the answer changes with it. + (`AgentRegistry.swift:524-552`). The separate `/agents` page is incomplete for Cursor and the other + newer rows; that is a page correction, not a gate for this self-contained answer. ### E2 · "What happens when my agent is idle?" @@ -152,23 +151,22 @@ check. > **Yes — Terminal.app, iTerm2, Warp, Ghostty, kitty, WezTerm and tmux.** A session is tied to the > terminal that started it, so Jump lands in the right window and, in tmux, the right pane. Replies -> type back into that same pane. A remote agent's pane is resolved by walking the process tree, -> including panes on a private tmux server. +> type back into that same pane. - **Question source:** no captured ask. Underlying reports: NOOK-302, 2026-10-13 (*"a tmux session shows only 'tmux', and its outer terminal comes from whoever started the tmux server"*); NOOK-310, 2026-10-13 (*"jump and send address tmux panes on the default server, ignoring the session's tmux - socket"*); NOOK-788, 2026-10-22 (*"a remote reply inside a private tmux server resolves to - nothing"*). -- **Claim:** seven terminal families, tmux panes and private tmux servers included. + socket"*). +- **Claim:** seven terminal families and tmux panes included. Remote panes are not claimed here; + the remote launch story is still held. - **Audience:** anyone whose workflow is tmux-first. - **Channel:** `/faq`. - **Owner:** CMO writes; CTO confirms. - **Date:** CTO confirmation 2026-11-03; publish 2026-11-06. -- **Must be true:** `Sources/NookCore/Terminal` still resolves those seven identities, and - `RemotePaneHop` still walks every tmux server's socket directory by ancestry. This entry is - **report-sourced, not ask-sourced**; if a captured ask never arrives, it is still publishable - because the reports are real, but it ranks below E1–E3 until one does. +- **Must be true:** `Sources/NookCore/Terminal` still resolves those seven identities and still + addresses a session's own tmux pane. This entry is **report-sourced, not ask-sourced**; if a + captured ask never arrives, it is still publishable because the reports are real, but it ranks + below E1–E3 until one does. ### E5 · "Do I need a Mac with a notch?" @@ -226,8 +224,9 @@ check. > **The Mac app does.** The island, agent cards, permission cards and fan control work with no > network; the hooks talk to the app over a local socket. The network is used for update checks, -> licence activation and the optional trial email. The phone link is the exception: when you are away -> from your Mac, the phone reaches it through our relay, so that part needs a connection. +> licence activation, crash reports and the optional trial email. The phone link is the exception: +> when you are away from your Mac, the phone reaches it through our relay, so that part needs a +> connection. - **Question source:** live `/faq`, 2026-10-29; NOOK-494, 2026-10-16 (*"iOS: the main list gives no sign the phone is offline from the Mac"*). @@ -237,8 +236,8 @@ check. - **Owner:** CMO writes; CTO confirms. - **Date:** CTO confirmation 2026-11-03; publish 2026-11-06. - **Must be true:** the only network calls at the shipped commit are the update check, licence - activation, the optional trial email, and the phone relay; `/privacy` lists the same set. This - entry shares its gate with the privacy correction below. + activation, crash reporting, the optional trial email, and the phone relay; `/privacy` lists the + same set. This entry shares its gate with the privacy correction below. --- diff --git a/marketing/drafts/faq-page.patch b/marketing/drafts/faq-page.patch index 5896417..0193118 100644 --- a/marketing/drafts/faq-page.patch +++ b/marketing/drafts/faq-page.patch @@ -1,5 +1,5 @@ diff --git a/src/routes/nook/faq.tsx b/src/routes/nook/faq.tsx -index 03d135a..6c2da28 100644 +index 03d135a..539a909 100644 --- a/src/routes/nook/faq.tsx +++ b/src/routes/nook/faq.tsx @@ -1,8 +1,7 @@ @@ -22,7 +22,7 @@ index 03d135a..6c2da28 100644 + "Does it work with my agent — and can I approve from the notch, or only watch?", answer: - "No. The hooks and plugins that connect your agents to The Nook send session metadata only — which agent is running, which session, which event happened, which terminal it lives in. No prompt text and no code content leaves your device. Two things do leave the device, and we'd rather say so plainly: anonymous usage telemetry, and your email address if you choose to give it at trial start. That's the whole list." -+ "It depends on the agent, and Cursor is the useful example. Cursor is watched, not gated: its sessions, finished turns and errors appear in the island, but when Cursor asks for permission the prompt stays in Cursor. That is deliberate — Cursor blocks the action when a permission hook runs and prints nothing, so gating it would override Cursor's own prompts. Other agents do hand the decision to The Nook, so a tool call waits and you tap Allow or Deny from the card. /agents lists which is which for every agent. One limit: cursor-agent -p one-shot runs send no turn end, so they appear but do not get a completion card." ++ "It depends on the agent, and Cursor is the useful example. Cursor is watched, not gated: its sessions, finished turns and errors appear in the island, but when Cursor asks for permission the prompt stays in Cursor. That is deliberate — Cursor blocks the action when a permission hook runs and prints nothing, so gating it would override Cursor's own prompts. Other agents do hand the decision to The Nook, so a tool call waits and you tap Allow or Deny from the card. One limit: cursor-agent -p one-shot runs send no turn end, so they appear but do not get a completion card." }, { - question: "Do I need a Mac with a notch?", @@ -42,7 +42,7 @@ index 03d135a..6c2da28 100644 + question: "Does it work with my terminal, including tmux?", answer: - "The Nook is a small native UI, not a background agent — it watches the agents you're already running; it doesn't run anything itself. The heaviest thing it does is read and write your Mac's fan and charging controllers, which is a lightweight sensor read. If you're running enough coding agents to need it, those agents dwarf the app's own draw." -+ "Yes — Terminal.app, iTerm2, Warp, Ghostty, kitty, WezTerm and tmux. A session is tied to the terminal that started it, so Jump lands in the right window and, in tmux, the right pane. Replies type back into that same pane. A remote agent's pane is resolved by walking the process tree, including panes on a private tmux server." ++ "Yes — Terminal.app, iTerm2, Warp, Ghostty, kitty, WezTerm and tmux. A session is tied to the terminal that started it, so Jump lands in the right window and, in tmux, the right pane. Replies type back into that same pane." }, { - question: "What permissions does it need?", @@ -66,7 +66,7 @@ index 03d135a..6c2da28 100644 question: "Does it work offline?", answer: - "Yes. Everything The Nook does — the agent grid, permission cards, fan and thermal control — works with no network at all, and your agents' hooks talk to the app over a local socket. The network is only used for update checks, license activation, and the optional trial email." -+ "The Mac app does. The island, agent cards, permission cards and fan control work with no network; the hooks talk to the app over a local socket. The network is used for update checks, licence activation and the optional trial email. The phone link is the exception: when you are away from your Mac, the phone reaches it through our relay, so that part needs a connection." ++ "The Mac app does. The island, agent cards, permission cards and fan control work with no network; the hooks talk to the app over a local socket. The network is used for update checks, licence activation, crash reports and the optional trial email. The phone link is the exception: when you are away from your Mac, the phone reaches it through our relay, so that part needs a connection." } ];