agent-relay-runner 0.127.10 → 0.128.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-relay-runner",
-  "version": "0.127.10",
+  "version": "0.128.0",
   "description": "Unified provider lifecycle runner for Agent Relay",
   "type": "module",
   "bin": {
@@ -23,7 +23,7 @@
   },
   "dependencies": {
     "agent-relay-providers": "0.104.4",
-    "agent-relay-sdk": "0.2.123",
+    "agent-relay-sdk": "0.2.125",
     "callmux": "0.23.0"
   },
   "devDependencies": {

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.127.10",
+  "version": "0.128.0",
   "agentRelayContracts": {
     "providerPluginProtocol": 1
   }

package/plugins/claude/monitors/relay-monitor.provisioned.mjs

@@ -47,8 +47,8 @@ var RUNNER_PROMPT_TEMPLATE_DEFAULTS = [
     category: "runner",
     title: "Codex Relay Context",
     description: "Relay context note injected into Codex sessions.",
-    template: "[agent-relay] You are connected to Agent Relay, a real-time message bus between agents and users. When you receive a relay message: read it, do what it asks, and reply through the relay when a text response is needed. Use agent-relay /react <messageId> <emoji> for lightweight acknowledgement or approval. If Relay MCP tools are available, prefer relay_reply, relay_get_message, relay_get_thread, relay_send_message, relay_upload_artifact, relay_attach_artifact, relay_agent_status, relay_find_agents, relay_compact_and_resume, relay_recall, relay_spawn_agent, and relay_shutdown_agent. You never need to know or pass your own agent id \u2014 relay fills it from your token; use relay_whoami only if you need to reason about yourself. relay_compact_and_resume is for clean-seam self-resume after a context advisory: pass workingState and optional ruledOut; Relay owns the objective envelope. relay_recall searches your own archived pre-compaction segments by keyword when a discarded detail is needed. relay_spawn_targets / relay_spawn_agent / relay_shutdown_agent only appear if your profile grants spawning (a live-children quota); when present, call relay_spawn_targets FIRST for the live host/provider/model matrix + your quota, then stand up long-living child agents and shut down your own \u2014 find them later with relay_find_agents spawnedBy:me. For replies, prefer relay_reply or relay_send_message; CLI fallback: agent-relay /reply <messageId> \"<your reply>\". If a delivered message says it was truncated, fetch the full body with: agent-relay get-message <messageId>. For command details, run: agent-relay /guide",
-    defaultTemplate: "[agent-relay] You are connected to Agent Relay, a real-time message bus between agents and users. When you receive a relay message: read it, do what it asks, and reply through the relay when a text response is needed. Use agent-relay /react <messageId> <emoji> for lightweight acknowledgement or approval. If Relay MCP tools are available, prefer relay_reply, relay_get_message, relay_get_thread, relay_send_message, relay_upload_artifact, relay_attach_artifact, relay_agent_status, relay_find_agents, relay_compact_and_resume, relay_recall, relay_spawn_agent, and relay_shutdown_agent. You never need to know or pass your own agent id \u2014 relay fills it from your token; use relay_whoami only if you need to reason about yourself. relay_compact_and_resume is for clean-seam self-resume after a context advisory: pass workingState and optional ruledOut; Relay owns the objective envelope. relay_recall searches your own archived pre-compaction segments by keyword when a discarded detail is needed. relay_spawn_targets / relay_spawn_agent / relay_shutdown_agent only appear if your profile grants spawning (a live-children quota); when present, call relay_spawn_targets FIRST for the live host/provider/model matrix + your quota, then stand up long-living child agents and shut down your own \u2014 find them later with relay_find_agents spawnedBy:me. For replies, prefer relay_reply or relay_send_message; CLI fallback: agent-relay /reply <messageId> \"<your reply>\". If a delivered message says it was truncated, fetch the full body with: agent-relay get-message <messageId>. For command details, run: agent-relay /guide",
+    template: "[agent-relay] You are connected to Agent Relay, a real-time message bus between agents and users. When you receive a relay message: read it, do what it asks, and reply through the relay when a text response is needed. Use agent-relay /react <messageId> <emoji> for lightweight acknowledgement or approval. If Relay MCP tools are available, prefer relay_reply, relay_get_message, relay_get_thread, relay_send_message, relay_upload_artifact, relay_attach_artifact, relay_agent_status, relay_find_agents, relay_compact_and_resume, relay_recall, relay_spawn_agent, and relay_shutdown_agent. You never need to know or pass your own agent id \u2014 relay fills it from your token. Your identity is injected at startup as the `## Agent Relay Identity` block; use relay_whoami only for the full verbose identity dump. relay_compact_and_resume is for clean-seam self-resume after a context advisory: pass workingState and optional ruledOut; Relay owns the objective envelope. relay_recall searches your own archived pre-compaction segments by keyword when a discarded detail is needed. relay_spawn_targets / relay_spawn_agent / relay_shutdown_agent only appear if your profile grants spawning (a live-children quota); when present, call relay_spawn_targets FIRST for the live host/provider/model matrix + your quota, then stand up long-living child agents and shut down your own \u2014 find them later with relay_find_agents spawnedBy:me. For replies, prefer relay_reply or relay_send_message; CLI fallback: agent-relay /reply <messageId> \"<your reply>\". If a delivered message says it was truncated, fetch the full body with: agent-relay get-message <messageId>. For command details, run: agent-relay /guide",
+    defaultTemplate: "[agent-relay] You are connected to Agent Relay, a real-time message bus between agents and users. When you receive a relay message: read it, do what it asks, and reply through the relay when a text response is needed. Use agent-relay /react <messageId> <emoji> for lightweight acknowledgement or approval. If Relay MCP tools are available, prefer relay_reply, relay_get_message, relay_get_thread, relay_send_message, relay_upload_artifact, relay_attach_artifact, relay_agent_status, relay_find_agents, relay_compact_and_resume, relay_recall, relay_spawn_agent, and relay_shutdown_agent. You never need to know or pass your own agent id \u2014 relay fills it from your token. Your identity is injected at startup as the `## Agent Relay Identity` block; use relay_whoami only for the full verbose identity dump. relay_compact_and_resume is for clean-seam self-resume after a context advisory: pass workingState and optional ruledOut; Relay owns the objective envelope. relay_recall searches your own archived pre-compaction segments by keyword when a discarded detail is needed. relay_spawn_targets / relay_spawn_agent / relay_shutdown_agent only appear if your profile grants spawning (a live-children quota); when present, call relay_spawn_targets FIRST for the live host/provider/model matrix + your quota, then stand up long-living child agents and shut down your own \u2014 find them later with relay_find_agents spawnedBy:me. For replies, prefer relay_reply or relay_send_message; CLI fallback: agent-relay /reply <messageId> \"<your reply>\". If a delivered message says it was truncated, fetch the full body with: agent-relay get-message <messageId>. For command details, run: agent-relay /guide",
     variables: []
   },
   {

package/src/adapters/claude-status-detectors.ts

@@ -1,5 +1,6 @@
 import { extractClaudeModelUnavailableMessage } from "agent-relay-sdk";
 import type { ProviderStatusUpdate } from "../adapter";
+import type { ClaudeProbeActivity } from "./claude-session-probe";
 import { buildRateLimitProviderState, parseClaudeRateLimitPane } from "../rate-limit";
 
 // LEGACY PANE-SCRAPE FALLBACK (#766/#768) — busy/idle is now driven primarily by
@@ -19,8 +20,8 @@ import { buildRateLimitProviderState, parseClaudeRateLimitPane } from "../rate-l
 //     (the cross-version anchor; the "esc to interrupt" hint was already dropped in 2.1.x).
 //   FALSE POSITIVES: agent output that literally QUOTES any of these strings (e.g. a
 //     transcript discussing "esc to interrupt", or this very comment shown in a pane)
-//     reads as ready/busy. Tolerated because the markers are CC-specific enough to be
-//     rare in real output; if it bites, gate on the LAST N lines only (the live footer).
+//     reads as ready/busy. The activity reconciler gates on the LAST N lines only (the
+//     live footer); direct raw predicates are still used by readiness/wait gates.
 // History: 18067b5 (busy counter), and the readiness footer-vs-banner fix below.
 export function claudePaneLooksReady(text: string): boolean {
   // Claude's startup banner ("Claude Code" / "Welcome back") scrolls off the pane once the
@@ -43,6 +44,7 @@ export function claudePaneLooksReady(text: string): boolean {
 // (ctrl+o to expand)" truncation marker, the idle input box, or the persistent
 // "/btw … without interrupting Claude's current work" queue hint.
 const CLAUDE_BUSY_SPINNER_RE = /…\s*\((?:\d+h\s+)?(?:\d+m\s+)?\d+s\b/;
+const CLAUDE_ACTIVITY_FOOTER_LINES = 10;
 
 export function claudePaneIsBusy(text: string): boolean {
   // Claude Code <2.1.x rendered "(esc to interrupt)" in the spinner footer; 2.1.x
@@ -52,6 +54,17 @@ export function claudePaneIsBusy(text: string): boolean {
   return CLAUDE_BUSY_SPINNER_RE.test(text) || text.includes("esc to interrupt");
 }
 
+function claudeActivityFooter(text: string): string {
+  return text.split("\n").slice(-CLAUDE_ACTIVITY_FOOTER_LINES).join("\n");
+}
+
+export function claudeActivityFromProbeAndPane(probe: ClaudeProbeActivity | undefined, pane: string): ClaudeProbeActivity {
+  const footer = claudeActivityFooter(pane);
+  if (probe === "busy" || claudePaneIsBusy(footer)) return "busy";
+  if (claudePaneLooksReady(footer)) return "idle";
+  return probe === "idle" ? "unknown" : probe ?? "unknown";
+}
+
 // #286: detect the subscription usage-limit modal in the pane and turn it into the
 // provider-neutral rate-limit hold (idle + blocked) that the relay's resume sweep lifts
 // at reset. Mirrors claudeModelUnavailableStatus, but non-terminal (idle, not error).

package/src/adapters/claude.ts

@@ -12,7 +12,7 @@ import { assembleLaunch, materializeLaunchAssembly, sessionStatusLineSettingsArg
 import { claudeProviderMessageText } from "./claude-delivery";
 import { claudeProbeActivity, readManagedClaudeStatus, resolveClaudePid, type ClaudeProbeActivity } from "./claude-session-probe";
 import { evaluateClaudePromptGatePane, initialClaudePromptGatePaneState, type ClaudePromptGatePaneState } from "./claude-prompt-gates";
-import { claudePaneLooksReady, claudePaneIsBusy, claudeRateLimitStatus, claudeConnectionRetryStatus, claudeModelUnavailableStatus } from "./claude-status-detectors";
+import { claudeActivityFromProbeAndPane, claudePaneLooksReady, claudePaneIsBusy, claudeRateLimitStatus, claudeConnectionRetryStatus, claudeModelUnavailableStatus } from "./claude-status-detectors";
 import { ClaudeSessionCapture, collectClaudeTranscriptArchiveSegment, collectClaudeTranscriptSessionEvents } from "./claude-session-capture";
 import { CLAUDE_TMUX_READY_TIMEOUT_MS, captureTmuxPane, submitTextToTmux, tmuxEnvKeys, tmuxSessionName, tmuxSocketName, waitForClaudeInputReady, writeLauncherScript } from "./claude-tmux";
 import { claudePermissionPromptHandler } from "./claude-permission";
@@ -138,12 +138,11 @@ export class ClaudeAdapter implements ProviderAdapter {
       tmuxSocket: socket,
       configHomeEnv: (process.meta?.env as Record<string, string | undefined> | undefined)?.CLAUDE_CONFIG_DIR,
     });
-    if (managed?.reading.available) return claudeProbeActivity(managed.reading.status);
-    let pane: string;
-    try { pane = captureTmuxPane(session, socket); } catch { return "unknown"; }
-    if (claudePaneIsBusy(pane)) return "busy";
-    if (claudePaneLooksReady(pane)) return "idle";
-    return "unknown";
+    const probe = managed?.reading.available ? claudeProbeActivity(managed.reading.status) : undefined;
+    if (probe === "busy") return "busy";
+    let pane: string | undefined;
+    try { pane = captureTmuxPane(session, socket); } catch { return probe ?? "unknown"; }
+    return claudeActivityFromProbeAndPane(probe, pane);
   }
 
   // #769 P1-A: an independent pane-busy read, consumed ONLY as a veto on the busy
@@ -532,7 +531,7 @@ export { tmuxHasSession };
 
 // Re-export pane-status detectors (moved to ./claude-status-detectors) so existing
 // import paths (including claude.test.ts) continue to resolve via this module.
-export { claudePaneLooksReady, claudePaneIsBusy, claudeRateLimitStatus, claudeConnectionRetryStatus, claudeModelUnavailableStatus } from "./claude-status-detectors";
+export { claudeActivityFromProbeAndPane, claudePaneLooksReady, claudePaneIsBusy, claudeRateLimitStatus, claudeConnectionRetryStatus, claudeModelUnavailableStatus } from "./claude-status-detectors";
 
 // Shared shell-quoting; re-exported so `./claude` consumers + tests resolve it.
 export { shellQuote };

package/src/profile-home.ts

@@ -140,7 +140,7 @@ function seedClaudeConfigIfMissing(claudeHome: string, config: RunnerSpawnConfig
 
 function readHostClaudeConfig(): Record<string, unknown> | undefined {
   try {
-    const hostPath = join(homedir(), ".claude.json");
+    const hostPath = join(providerSourceHome("claude"), ".claude.json");
     if (!existsSync(hostPath)) return undefined;
     return JSON.parse(readFileSync(hostPath, "utf8")) as Record<string, unknown>;
   } catch {

package/src/runner-core.ts

@@ -192,6 +192,7 @@ export class AgentRunner {
   private currentTokenProfileId?: string;
   private currentTokenExpiresAt?: number;
   private control?: ControlServer;
+  private registeredAt?: number;
   // Stage 2 (#215): the local MCP endpoint the agent connects to, fronting the relay so the
   // Runner owns reconnect/backoff + a durable buffer. Disabled via AGENT_RELAY_MCP_PROXY=0
   // (then the agent connects to the relay directly, Stage-1 behaviour). The proxy secret is the
@@ -470,7 +471,10 @@ export class AgentRunner {
       void this.handleCommand(type, params, commandId, command);
     });
     this.bus.on("error", (code, message) => this.handleBusError(String(code), String(message)));
-    await registerWithinDeadline(this.bus, registrationTimeoutMsFromEnv(), this.options.relayUrl, (reason) => logger.fatal("register", reason)); await initializeRunnerTemplates(this.http);
+    await registerWithinDeadline(this.bus, registrationTimeoutMsFromEnv(), this.options.relayUrl, (reason) => logger.fatal("register", reason));
+    this.registeredAt = Date.now();
+    this.writeRunnerInfoFile();
+    await initializeRunnerTemplates(this.http);
     this.obligationCache.start();
     this.outbox.start();
     this.sessionOutbox.start();
@@ -649,6 +653,7 @@ export class AgentRunner {
         ...(providerTerminalSession(this.process) ? { tmuxSession: providerTerminalSession(this.process) } : {}),
         ...(providerTerminalSocket(this.process) ? { tmuxSocket: providerTerminalSocket(this.process) } : {}),
         startedAt: this.options.startedAt,
+        ...(this.registeredAt ? { registeredAt: this.registeredAt } : {}),
       }, null, 2) + "\n", { mode: 0o600 });
     } catch (error) {
       logger.error("runner", `failed to write runner info file: ${error}`);