open-claude-p 1.1.1 → 1.1.2

package/CHANGELOG.md

@@ -7,6 +7,45 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## [1.1.2] — 2026-05-19
+
+Recovery-path fixes for the sentinel-missing case. When the end-of-reply
+marker fails to land — usually because claude omitted it or the PTY
+frames were truncated — the driver's text extraction was returning
+either an empty string or, worse, the entire re-rendered transcript of
+a `--resume` session. Two changes correct that.
+
+### Fixed
+
+- **`extractAssistantText` no longer slices from the FIRST `⏺`** when
+  the sentinel is missing. On a `--resume` run the buffer carries old
+  history regions before the current response; anchoring on the first
+  `⏺` returned the oldest history turn plus everything after it,
+  silently leaking prior turns into `result.text`. The fallback now
+  uses `lastIndexOf('⏺')` so the slice always covers the current
+  turn's response. Fresh (non-resumed) sessions are unaffected because
+  the buffer only has one region marker, so first == last.
+
+### Added
+
+- **Degraded-capture notice prefix.** When `completionReason` is
+  `'idle'` (sentinel never seen, idle-fallback completed) or
+  `'jsonl-recovered'` (a stall was rescued by reading the upstream
+  JSONL session log), `result.text` is now prefixed with:
+
+  ```
+  [ocp] Streaming capture not detected — showing last result from {source}.
+  ```
+
+  where `{source}` is either `local session log` (JSONL had the
+  response) or `terminal buffer (best effort)` (JSONL was unavailable
+  and we fell back to the PTY slice above). Callers and chat UIs can
+  now distinguish a normal capture from a post-hoc recovery without
+  inspecting `completionReason`. The default success path
+  (`reason='sentinel'`) is unchanged — no prefix is added.
+
+---
+
 ## [1.1.1] — 2026-05-19
 
 Post-1.1.0 fixes driven by Cosmica integration testing. Several of

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-claude-p",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "A PTY-backed compatibility shim for `claude -p` (Claude Code headless/print mode). Drives the interactive `claude` CLI via node-pty and exposes the same option surface and stream-json contract. Ships as both a library and an `ocp` CLI binary.",
   "type": "module",
   "main": "./src/index.js",

package/src/index.js

@@ -775,6 +775,28 @@ class Driver {
       );
     }
 
+    // Degraded-capture notice. When the per-turn sentinel never landed
+    // (`reason='idle'`) or a stalled completion was rescued via JSONL
+    // (`reason='jsonl-recovered'`), the streamed PTY frames did NOT
+    // produce a clean end-of-reply boundary. The text we are returning
+    // is a post-hoc recovery — usually from the upstream JSONL session
+    // log, or as a best-effort tail of the PTY buffer when JSONL was
+    // unavailable. Prepend a one-line notice so the caller (and any
+    // chat UI rendering it) can tell this apart from a normal capture.
+    // The notice is intentionally a literal English prefix and only
+    // appears on the degraded path — the default success path
+    // (`reason='sentinel'`) is unchanged.
+    const captureFailed =
+      effectiveCompletion === 'idle' || effectiveCompletion === 'jsonl-recovered';
+    if (captureFailed && text) {
+      const source = jsonlExtraction?.text
+        ? 'local session log'
+        : 'terminal buffer (best effort)';
+      text =
+        `[ocp] Streaming capture not detected — showing last result from ${source}.\n\n` +
+        text;
+    }
+
     // For stall-style failures, capture the tail of the stripped PTY
     // buffer so the caller can see exactly what claude was rendering
     // when we gave up — that is usually the dialog or error that the
@@ -1144,9 +1166,12 @@ function extractAssistantText(stripped, nonce) {
     sentinelIdx = i;
   }
   if (sentinelIdx === -1) {
-    // Fall back to "everything after the first ⏺" — this preserves the
-    // legacy behavior when the model dropped the sentinel.
-    const ri = stripped.indexOf(marker);
+    // Sentinel-missing fallback. On a resumed session the buffer carries
+    // history regions before the current response, so anchoring on the
+    // FIRST `⏺` would slice from the oldest history turn and return the
+    // entire re-rendered transcript. Anchor on the LAST `⏺` instead —
+    // that's the region marker for the current turn even after `--resume`.
+    const ri = stripped.lastIndexOf(marker);
     return ri === -1 ? '' : stripped.slice(ri + marker.length).trim();
   }