@cstart/coldstart 2.0.1 → 2.0.3

package/hooks/cursor-kb-elicit.mjs

@@ -152,11 +152,20 @@ function filesBlock(root, files) {
 }
 
 // --- The capture prompt (kept identical to the Codex/Claude capture prompt) ----
-function buildCapturePrompt(root, block, sid) {
+function buildCapturePrompt(root, block, sid, isSubagent) {
   return `You have completed a task now and have gathered knowledge as a part of that task or \
-process. We need to preserve the knowledge so that another agent in future can make use of your \
-findings. We are storing this in a notebook format and this notebook has to be backed by the \
-codebase you are working on.
+process — knowledge another agent in future could make use of.
+
+But before writing any notes, we need to decide whether the task you completed deserves a note. \
+If you were investigating on an older branch or doing a PR review, we may not need to save notes \
+because that code is not in the present — it's in the past or it's in the future. The notes that \
+we write are backed by the code in the present. This was an example to explain to you. As an \
+agent who worked on the current task, you know its exact intent and are best suited to decide \
+whether this task deserves a note. And if nothing about the current code is worth recording, \
+then no note is the right answer.
+
+Once you decide the task does deserve a note, we store it in a notebook format, and this \
+notebook has to be backed by the codebase you are working on.
 
 We need to save only the working knowledge of the codebase in a specific format so that it can \
 be searched and served to future cold agents. We don't need to store any general interaction you \
@@ -167,8 +176,9 @@ below format —
 
 THE NOTEBOOK HAS THREE CONTAINERS. Put each piece of knowledge in its one home:
 
-1. FILE notes — write one for EVERY file you actually read and understood this session. No \
-judgment call about whether it seems obvious. First decide the file's CHARACTER:
+1. FILE notes (if you decided to write a note for the entire task) — write one for EVERY file \
+you actually read and understood this session. No judgment call about whether it seems obvious. \
+First decide the file's CHARACTER:
    - hub    = the file has no single purpose (models.py, helpers, utils). Knowledge lives per \
 SYMBOL, as facets: one facet for each symbol you worked with this session. Only symbols you \
 have firsthand knowledge of — never enumerate the rest.
@@ -245,7 +255,9 @@ Spec shapes (only include fields you actually have):
                   "body":"what you looked for + that it is not there",
                   "scope":{"terms":["search","terms"]}}          (the search that proved it)
 
-When your notes are written, stop.`;
+${isSubagent
+  ? `Once you have handled the notebook — whether you wrote notes or decided none were needed — remember you were spawned as a subagent. The coordinator that spawned you receives ONLY your final message, so your last message must repeat, in full, the result you produced for it — your findings, not the notebook decision.`
+  : `When your notes are written, stop.`}`;
 }
 
 // --- stdin + guards -------------------------------------------------------------
@@ -324,7 +336,7 @@ process.on("unhandledRejection", (e) => { log(`unhandled ${e?.stack || e}`); pro
       process.exit(0);
     }
 
-    const prompt = buildCapturePrompt(root, filesBlock(root, files), sid);
+    const prompt = buildCapturePrompt(root, filesBlock(root, files), sid, event === "subagentStop");
     logCaptureEvent(root, { event: "elicit", session: sid, agent: aid, touched: files.length, hook: event });
     log(`ELICIT session=${sid} agent=${aid} touched=${files.length} promptBytes=${prompt.length} event=${event || "?"}`);
     process.stdout.write(JSON.stringify({ followup_message: prompt }));

package/hooks/kb-elicit.mjs

@@ -147,11 +147,20 @@ function filesBlock(root, files) {
 
 // --- The capture prompt (v4, 2026-07-07 — user-authored opening; validation-run
 // configuration: gates off via --force, capture-only) ---------------------------
-function buildCapturePrompt(root, block, sid) {
+function buildCapturePrompt(root, block, sid, isSubagent) {
   return `You have completed a task now and have gathered knowledge as a part of that task or \
-process. We need to preserve the knowledge so that another agent in future can make use of your \
-findings. We are storing this in a notebook format and this notebook has to be backed by the \
-codebase you are working on.
+process — knowledge another agent in future could make use of.
+
+But before writing any notes, we need to decide whether the task you completed deserves a note. \
+If you were investigating on an older branch or doing a PR review, we may not need to save notes \
+because that code is not in the present — it's in the past or it's in the future. The notes that \
+we write are backed by the code in the present. This was an example to explain to you. As an \
+agent who worked on the current task, you know its exact intent and are best suited to decide \
+whether this task deserves a note. And if nothing about the current code is worth recording, \
+then no note is the right answer.
+
+Once you decide the task does deserve a note, we store it in a notebook format, and this \
+notebook has to be backed by the codebase you are working on.
 
 We need to save only the working knowledge of the codebase in a specific format so that it can \
 be searched and served to future cold agents. We don't need to store any general interaction you \
@@ -162,8 +171,9 @@ below format —
 
 THE NOTEBOOK HAS THREE CONTAINERS. Put each piece of knowledge in its one home:
 
-1. FILE notes — write one for EVERY file you actually read and understood this session. No \
-judgment call about whether it seems obvious. First decide the file's CHARACTER:
+1. FILE notes (if you decided to write a note for the entire task) — write one for EVERY file \
+you actually read and understood this session. No judgment call about whether it seems obvious. \
+First decide the file's CHARACTER:
    - hub    = the file has no single purpose (models.py, helpers, utils). Knowledge lives per \
 SYMBOL, as facets: one facet for each symbol you worked with this session. Only symbols you \
 have firsthand knowledge of — never enumerate the rest.
@@ -239,7 +249,9 @@ Spec shapes (only include fields you actually have):
                   "body":"what you looked for + that it is not there",
                   "scope":{"terms":["search","terms"]}}          (the search that proved it)
 
-When your notes are written, stop.`;
+${isSubagent
+  ? `Once you have handled the notebook — whether you wrote notes or decided none were needed — remember you were spawned as a subagent. The coordinator that spawned you receives ONLY your final message, so your last message must repeat, in full, the result you produced for it — your findings, not the notebook decision.`
+  : `When your notes are written, stop.`}`;
 }
 
 // --- stdin + guards -------------------------------------------------------------
@@ -323,7 +335,7 @@ process.on("unhandledRejection", (e) => { log(`unhandled ${e?.stack || e}`); pro
       process.exit(0);
     }
 
-    const prompt = buildCapturePrompt(root, filesBlock(root, files), sid);
+    const prompt = buildCapturePrompt(root, filesBlock(root, files), sid, input.hook_event_name === "SubagentStop");
     logCaptureEvent(root, { event: "elicit", session: sid, agent: aid, touched: files.length, hook: input.hook_event_name });
     log(`ELICIT session=${sid} agent=${aid} touched=${files.length} promptBytes=${prompt.length} event=${input.hook_event_name || "?"}`);
     process.stdout.write(JSON.stringify({ decision: "block", reason: prompt }));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cstart/coldstart",
-  "version": "2.0.1",
+  "version": "2.0.3",
   "publishConfig": {
     "access": "public"
   },