@spunto/build 0.11.0 → 0.12.0

package/README.md

@@ -12,6 +12,8 @@ on*.
 npm install @spunto/build
 ```
 
+**Documentation: https://spunto.net/documentation/packages/build**
+
 ## What's in it
 
 ### `@spunto/build/steps` — the build-log protocol

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spunto/build",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "Spunto's shared Build engine — the devcontainer image protocol and VS Code extension registry clients, with no database, no HTTP framework and no UI.",
   "type": "module",
   "license": "MIT",

package/src/agent-stream/agent-stream.ts

@@ -122,6 +122,37 @@ export function interruptLine(protocol: AgentProtocol, requestId: string): strin
   return `${JSON.stringify({ type: "control_request", request_id: requestId, request: { subtype: "interrupt" } })}\n`
 }
 
+/**
+ * Ask the harness to **name the conversation**, or null for a dialect that cannot be asked.
+ *
+ * Claude Code used to do this on its own within seconds of the first turn, headless included —
+ * that title is what `sessionTitleProbe` reads. Measured on 2.1.296 (October 2026), it no longer
+ * does for a session driven over `--input-format stream-json`: the transcript gets `atis-latch`
+ * and `last-prompt` lines and never an `ai-title`, so every task kept its placeholder. What it
+ * still answers is the SDK's own `generate_session_title` control request — the call its
+ * TypeScript SDK makes — with `{"title":…}` in a `control_response` on stdout, and `persist`
+ * writes the same `ai-title` line to the transcript as before.
+ *
+ * Asking is not naming: the harness still picks the words, from the human's prompt (the
+ * `description`), exactly as it would have unprompted. Nothing of ours ends up in the title.
+ *
+ * The request id carries `TITLE_REQUEST_PREFIX` so the answer can be told apart from every other
+ * `control_response` (an interrupt's, say) without keeping state between write and read.
+ */
+export function sessionTitleRequestLine(protocol: AgentProtocol, requestId: string, description: string): string | null {
+  if (protocol !== "claude-stream") return null
+  const text = description.trim()
+  if (!text) return null
+  return `${JSON.stringify({
+    type: "control_request",
+    request_id: `${TITLE_REQUEST_PREFIX}${requestId}`,
+    request: { subtype: "generate_session_title", description: text, persist: true },
+  })}\n`
+}
+
+/** Marks the `control_request`s that ask for a title, and so the `control_response`s that answer. */
+const TITLE_REQUEST_PREFIX = "spunto-title-"
+
 /**
  * A shell that prints the line where the harness wrote **the name it gave the conversation**, or
  * null for a dialect that has no such thing.
@@ -143,6 +174,9 @@ export function interruptLine(protocol: AgentProtocol, requestId: string): strin
  * `--no-session-persistence` writes no transcript, and then this finds nothing — which is a
  * normal answer, not an error.
  *
+ * Since Claude Code 2.1.296 an interactive session only writes that line once asked
+ * (`sessionTitleRequestLine`); a one-shot `claude-json` run has no stdin to be asked on.
+ *
  * `jsonl` gets no probe on purpose: a harness speaking our vocabulary says the name in band,
  * `{"type":"session.title","title":"…"}`, and pays nothing for it.
  */
@@ -383,6 +417,16 @@ function adaptClaudeJson(obj: Record<string, unknown>): NormalizedEvent[] {
     return events
   }
 
+  // The answer to `sessionTitleRequestLine`. Only ours, recognised by request id: a
+  // `control_response` is also how an interrupt is acknowledged, and that one is no name.
+  if (type === "control_response") {
+    const response = (obj.response ?? {}) as Record<string, unknown>
+    const inner = (response.response ?? {}) as Record<string, unknown>
+    const requestId = typeof response.request_id === "string" ? response.request_id : ""
+    const title = response.subtype === "success" && requestId.startsWith(TITLE_REQUEST_PREFIX) ? cleanTitle(inner.title) : null
+    if (title) return [{ type: "session.title", payload: { title } }]
+  }
+
   // Known-but-uninteresting (`rate_limit_event`, `system/thinking_tokens`) and anything the CLI
   // grows next land here rather than being dropped: an unknown event is information about the
   // harness, and the UI keeps it behind a toggle.

package/src/agent-stream/index.ts

@@ -25,6 +25,7 @@ export {
   parseStreamLine,
   readsTitleOutOfBand,
   sessionTitleProbe,
+  sessionTitleRequestLine,
   splitCompleteLines,
   summarizeUsage,
   TASK_EVENT_TYPES,