agent-relay-runner 0.27.1 → 0.28.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-relay-runner",
-  "version": "0.27.1",
+  "version": "0.28.0",
   "description": "Unified provider lifecycle runner for Agent Relay",
   "type": "module",
   "bin": {
@@ -20,7 +20,7 @@
     "directory": "runner"
   },
   "dependencies": {
-    "agent-relay-sdk": "0.2.16"
+    "agent-relay-sdk": "0.2.17"
   },
   "devDependencies": {
     "@types/bun": "latest",

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "agent-relay-runner",
   "description": "Thin Agent Relay runner bridge for Claude Code",
-  "version": "0.27.1",
+  "version": "0.28.0",
   "agentRelayContracts": {
     "providerPluginProtocol": 1
   }

package/src/adapter.ts

@@ -211,9 +211,19 @@ function isPersistedRelayMessage(message: Message): boolean {
   return Number.isSafeInteger(message.id) && message.id > 0;
 }
 
+// #283 — one-line nudge that replaces the reply-scaffold footer for notification-class
+// (replyExpected:false) messages. Deliberately tiny so a bloated context can't drown the
+// no-reply rule established at session start. Shared with the Claude delivery path.
+export const NOTIFICATION_NUDGE = "↪ Notification — no reply needed.";
+
+// A notification is a persisted message the server marked replyExpected:false.
+export function isNotificationMessage(message: Message): boolean {
+  return isPersistedRelayMessage(message) && message.replyExpected === false;
+}
+
 function latestReplyableMessage(messages: Message[]): Message | undefined {
   return messages
-    .filter((message) => isPersistedRelayMessage(message) && !isMemoryInjection(message) && !isReactionNotification(message))
+    .filter((message) => isPersistedRelayMessage(message) && !isMemoryInjection(message) && !isReactionNotification(message) && message.replyExpected !== false)
     .at(-1);
 }
 
@@ -316,6 +326,9 @@ export function providerMessageText(messages: Message[]): string {
       "If you already delivered the useful response through Relay, do not send a separate status-only confirmation.",
       "If multiple messages arrived together, cover them in one reply instead of answering each line separately.",
     ].join("\n"));
+  } else if (messages.some(isNotificationMessage)) {
+    // #283 — pure notification batch: no scaffold, just the one-line no-reply nudge.
+    sections.push(NOTIFICATION_NUDGE);
   }
   return sections.join("\n\n");
 }

package/src/adapters/claude-delivery.ts

@@ -1,6 +1,6 @@
 import type { Message } from "agent-relay-sdk";
 import { isRecord } from "agent-relay-sdk";
-import { providerAttachmentText } from "../adapter";
+import { isNotificationMessage, NOTIFICATION_NUDGE, providerAttachmentText } from "../adapter";
 
 const PROVIDER_MESSAGE_BODY_PREVIEW_CHARS = 4000;
 const REMINDER_EVERY_DELIVERIES = 5;
@@ -61,7 +61,7 @@ function shouldShowReplyReminder(deliveryCount: number): boolean {
 
 function latestReplyableMessage(messages: Message[]): Message | undefined {
   return messages
-    .filter((message) => isPersistedRelayMessage(message) && !isMemoryInjection(message) && !isReactionNotification(message))
+    .filter((message) => isPersistedRelayMessage(message) && !isMemoryInjection(message) && !isReactionNotification(message) && message.replyExpected !== false)
     .at(-1);
 }
 
@@ -121,9 +121,13 @@ export function claudeProviderMessageText(messages: Message[], options: ClaudeDe
   const relaySurface = options.relaySurface !== false;
   const sections = messages.map((message) => formatMessage(message, relaySurface));
   const replyable = latestReplyableMessage(messages);
-  // Isolated agents have no way to reply through Relay — never append the reminder.
+  // Isolated agents have no way to reply through Relay — never append the reminder/nudge.
   if (relaySurface && replyable && shouldShowReplyReminder(options.deliveryCount)) {
     sections.push(replyReminder(replyable, options.readOnly === true));
+  } else if (relaySurface && !replyable && messages.some(isNotificationMessage)) {
+    // #283 — pure notification batch (no message wants a reply): drop the scaffold, append the
+    // one-line nudge so a long context can't make the agent forget the session-start no-reply rule.
+    sections.push(NOTIFICATION_NUDGE);
   }
   return sections.join("\n\n");
 }

package/src/adapters/claude-transcript.ts

@@ -22,7 +22,7 @@ interface TranscriptBlock {
 }
 
 export interface TurnStep {
-  type: "reasoning" | "tool";
+  type: "narration" | "reasoning" | "tool";
   text: string;
   label?: string;
 }
@@ -147,10 +147,12 @@ export function extractFinalAssistantMessage(jsonl: string): string {
  * Thinking and tool_use blocks are dropped, matching extractLastAssistantTurn.
  */
 /**
- * Extract the ordered reasoning and tool steps for the most recent turn (since
- * the last real user prompt). Used by the reasoning tailer to stream discreet
- * progress into chat while a turn is in flight. Returns steps in transcript order
- * so the tailer can emit only the ones it hasn't seen yet by index.
+ * Extract the ordered narration, reasoning, and tool steps for the most recent
+ * turn (since the last real user prompt). Used by the reasoning tailer to stream
+ * progress into chat while a turn is in flight. `narration` is the assistant's
+ * intermediate `text` between tool calls (the terminal's `●` lines); it is the
+ * primary, default-visible turn content. Returns steps in transcript order so the
+ * tailer can emit only the ones it hasn't seen yet.
  */
 export function extractLatestTurnSteps(jsonl: string): TurnStep[] {
   const lines = jsonl.split("\n");
@@ -170,7 +172,9 @@ export function extractLatestTurnSteps(jsonl: string): TurnStep[] {
     }
     if (entry.type !== "assistant") continue;
     for (const b of blocks(entry.message)) {
-      if (b.type === "thinking" && typeof b.thinking === "string" && b.thinking.trim()) {
+      if (b.type === "text" && typeof b.text === "string" && b.text.trim()) {
+        steps.push({ type: "narration", text: b.text.trim() });
+      } else if (b.type === "thinking" && typeof b.thinking === "string" && b.thinking.trim()) {
         steps.push({ type: "reasoning", text: b.thinking.trim() });
       } else if (b.type === "tool_use" && typeof b.name === "string" && b.name) {
         steps.push({ type: "tool", label: b.name, text: summarizeToolUse(b.name, b.input) });

package/src/relay-instructions.ts

@@ -8,6 +8,7 @@ export const CLAUDE_RELAY_MANUAL = `# Agent Relay
 - If multiple Relay messages arrive together, answer once to the latest relevant message and cover the current request. Do not separately acknowledge stale greetings or context.
 - If the useful response was already delivered through Relay, do not send an extra "sent", "done", or "drafts sent" confirmation unless the user explicitly asked for one.
 - No reply is needed for pure info messages, passive acknowledgements, or reactions that do not ask for action.
+- NEVER reply to a notification-class message. The server marks these and renders a single \`↪ Notification — no reply needed.\` line instead of the reply reminder — it is a fire-and-forget signal (a merge notice, lifecycle event, or FYI). Act on the information if relevant, but do not send any reply, status confirmation, or reaction back.
 - Use \`agent-relay /react <messageId> <emoji>\` instead of a text reply for lightweight acknowledgement, approval, thanks, or "good job" after a completed work update.
 - Good reaction uses: acknowledge praise with 👍 or ❤️, mark a completed handoff as seen, approve a proposed next step, or acknowledge a passive FYI.
 - Do not use reactions when the user asked a question, gave a new task, reported a bug, or needs a textual result.

package/src/runner.ts

@@ -1481,10 +1481,12 @@ export class AgentRunner {
     }, INTERRUPT_RECONCILE_DELAY_MS);
   }
 
-  // --- Reasoning tailer (item 5) ------------------------------------------------------
-  // Tail the in-flight turn's Claude transcript and surface new reasoning/tool steps
-  // as discreet session events. Coalesced and coarse; the final response still comes
-  // through publishSessionTurn.
+  // --- Turn-step tailer (item 5) ------------------------------------------------------
+  // Tail the in-flight turn's Claude transcript and surface new narration/reasoning/tool
+  // steps as session events, in transcript order. `narration` (the agent's intermediate
+  // text) is the primary visible content; reasoning visibility is a client-side toggle.
+  // Coalesced and coarse; the final response still comes through publishSessionTurn.
+  // `reasoningCapture: false` disables the whole live trace (server-side kill switch).
   private startReasoningTail(transcriptPath: string): void {
     if (this.options.providerConfig.reasoningCapture === false) return;
     this.stopReasoningTail();