oomi-ai 0.9.0 → 0.9.1

package/README.md

@@ -109,7 +109,7 @@ oomi connect --runtime hermes --name hermes --app-url https://www.oomi.ai
 oomi connect --runtime command --name my-agent --command '["/absolute/path/to/adapter"]' --app-url https://www.oomi.ai
 ```
 
-Use the user's app URL when provided. Hermes supports `--profile <profile>` and `--resume <exact-session-id>`. Without `--resume`, Oomi starts a persistent conversation with the same configured agent. Do not use `latest` or claim that an existing chat session was transferred unless its exact ID was selected. With oomi-ai 0.8.2+, an already-open Hermes conversation uses its existing local gateway owner and exact profile/session. Oomi attaches as another client; it never closes desktop, clears history, deletes a session lock, or substitutes a new chat. When no live owner exists, an Oomi-owned conversation (no `--resume`) runs on a warm `hermes acp` process with oomi-ai 0.9.0+: replies stream as they are written and stop when the person interrupts. Hermes permission requests are denied, as `chat --quiet` denies dangerous commands; ordinary file edits run as they do in quiet mode. A conversation moving from the CLI starts a new Hermes session that receives the recent Oomi history. `--resume` conversations, Hermes without ACP, and `--hermes-transport cli` use `chat --quiet --query-file -` and resume the exact returned `session_id` on subsequent turns.
+Use the user's app URL when provided. Hermes supports `--profile <profile>` and `--resume <exact-session-id>`. Without `--resume`, Oomi starts a persistent conversation with the same configured agent. Do not use `latest` or claim that an existing chat session was transferred unless its exact ID was selected. With oomi-ai 0.8.2+, an already-open Hermes conversation uses its existing local gateway owner and exact profile/session. Oomi attaches as another client; it never closes desktop, clears history, deletes a session lock, or substitutes a new chat. When no live owner exists, an Oomi-owned conversation (no `--resume`) runs on a warm `hermes acp` process with oomi-ai 0.9.0+: replies stream as they are written and stop when the person interrupts. From 0.9.1 the bridge starts Hermes and reopens recent conversations ahead of time (at bridge start and when a call opens), so the first message doesn't wait for Hermes to start. Hermes permission requests are denied, as `chat --quiet` denies dangerous commands; ordinary file edits run as they do in quiet mode. A conversation moving from the CLI starts a new Hermes session that receives the recent Oomi history. `--resume` conversations, Hermes without ACP, and `--hermes-transport cli` use `chat --quiet --query-file -` and resume the exact returned `session_id` on subsequent turns.
 
 Shared desktop conversations require Hermes's loopback WebSocket gateway, active-session discovery, and durable prompt/reply row IDs. Busy conversations ask you to retry after the current task. If a simultaneous desktop send queues your message without a reply receipt, or the connection drops after sending, check the same Hermes chat before resending. Oomi cannot safely repeat an uncertain action. Human approvals stay in the existing Hermes desktop UI. Shared photo submission is not yet supported; use Hermes desktop for that photo. Older or terminal-only owners without a shared gateway receive an actionable error, never a competing process. The shared owner keeps its existing environment, so use the explicit Oomi `--connection NAME` for account commands.
 

package/bin/oomi-ai.js

@@ -2539,6 +2539,7 @@ async function startOpenclawBridge(flags) {
   const localRuntime = bridgeState.localAgent
     ? new LocalAgentRuntime({ ...bridgeState.localAgent, connection: bridgeConnectionName }, path.dirname(resolveBridgeStatePath()), (health) => updateBridgeStatus(health))
     : null;
+  localRuntime?.warm();
   const gateway = localRuntime ? { gatewayUrl: 'local-agent:', configPath: resolveBridgeStatePath() } : readOpenclawGatewayConfig();
   if (!localRuntime && !gateway.token && !gateway.password) {
     throw new Error(`Gateway auth token/password not found in ${gateway.configPath}.`);
@@ -3600,6 +3601,8 @@ async function startOpenclawBridge(flags) {
         const sessionId = String(payload.sessionId || '').trim();
         if (!sessionId) return;
         bridgeDebugLog(`[bridge] client.open ${sessionId}`);
+        // A call is starting: make sure the agent is awake before the caller's first words.
+        if (classifyBridgeSessionScope(sessionId) === 'voice') localRuntime?.warm();
         getOrCreateGatewaySession(sessionId);
         return;
       }

package/lib/hermesAcp.js

@@ -196,7 +196,7 @@ class HermesAcpClient {
    * The ACP session for a conversation in this process: the one it already has, a stored one
    * reloaded from Hermes's history, or a new one. `created` says whether history was lost.
    */
-  async openSession(sessionId) {
+  async openSession(sessionId, { create = true } = {}) {
     const cwd = this.config.cwd;
     if (sessionId && this.loaded.has(sessionId)) return { sessionId, created: false };
     if (sessionId) {
@@ -213,6 +213,7 @@ class HermesAcpClient {
         if (err.code === 'hermes_acp_exited') throw err;
       } finally { this.replayed.delete(sessionId); }
     }
+    if (!create) return null;
     const created = await this.request('session/new', { cwd, mcpServers: [] });
     if (typeof created?.sessionId !== 'string' || !created.sessionId) throw unavailable();
     await this.prepare(created.sessionId);
@@ -342,6 +343,16 @@ function promptBlocks(request, seed) {
   return blocks;
 }
 
+/**
+ * Starts Hermes ahead of the first message and reopens recent conversations, so a call's first
+ * turn doesn't wait for Hermes to start (about 3.5 s on the maintainer's Mac).
+ */
+export async function warmHermesAcp(config, sessionIds = []) {
+  const client = hermesAcpClient(config);
+  await client.start();
+  for (const sessionId of sessionIds) await client.openSession(sessionId, { create: false }).catch(() => null);
+}
+
 /** One Hermes turn over ACP. Returns the reply and the ACP session that holds the conversation. */
 export async function runHermesAcpTurn(config, request, { signal, timeoutMs = 180000, onText } = {}) {
   const client = hermesAcpClient(config);

package/lib/localAgent.js

@@ -5,7 +5,7 @@ import { spawn } from 'node:child_process';
 import { EventEmitter } from 'node:events';
 import { createHash, randomUUID } from 'node:crypto';
 import { runSharedHermesTurn, hermesRefusal } from './hermesGateway.js';
-import { runHermesAcpTurn, hermesAcpAvailable, resetHermesAcp } from './hermesAcp.js';
+import { runHermesAcpTurn, hermesAcpAvailable, resetHermesAcp, warmHermesAcp } from './hermesAcp.js';
 import { grokbotConfig, runGrokbotTurn, completedGrokbotTurn } from './grokbotRuntime.js';
 
 const IMAGE_EXTENSIONS = { 'image/jpeg': '.jpg', 'image/png': '.png', 'image/webp': '.webp', 'image/gif': '.gif' };
@@ -275,6 +275,24 @@ export class LocalAgentRuntime {
   }
   socket() { return new LocalAgentSocket(this); }
   close() { if (this.config.runtime === 'hermes') resetHermesAcp(this.config); }
+  /** Gets Hermes ready before a message arrives: at bridge start and when a call opens. */
+  warm() {
+    if (this.config.runtime !== 'hermes' || !usesHermesAcp(this.config)) return Promise.resolve();
+    return warmHermesAcp(this.config, this.recentAcpSessions(2)).catch(() => {});
+  }
+  recentAcpSessions(limit) {
+    const directory = path.join(this.directory, 'conversations');
+    let files;
+    try { files = fs.readdirSync(directory).filter((name) => name.endsWith('.json')); } catch { return []; }
+    return files
+      .map((name) => { const file = path.join(directory, name); try { return { file, modified: fs.statSync(file).mtimeMs }; } catch { return null; } })
+      .filter(Boolean)
+      .sort((a, b) => b.modified - a.modified)
+      .map(({ file }) => readJson(file, {}))
+      .filter((state) => state.runtimeTransport === 'acp' && state.runtimeSessionId)
+      .slice(0, limit)
+      .map((state) => state.runtimeSessionId);
+  }
 }
 
 class LocalAgentSocket extends EventEmitter {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oomi-ai",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Connect OpenClaw, Hermes, Grok Bot, and other agents to Oomi with verified runtime adapters",
   "bin": {
     "oomi": "bin/oomi-ai.js"

package/skills/oomi/SKILL.md

@@ -188,7 +188,7 @@ oomi connect --runtime hermes --name hermes --app-url https://www.oomi.ai
 oomi connect --runtime command --name my-agent --command '["/absolute/path/to/adapter"]' --app-url https://www.oomi.ai
 ```
 
-Use the user's app URL when provided. Hermes supports `--profile <profile>` and `--resume <exact-session-id>`. Without `--resume`, Oomi starts a persistent conversation with the same configured agent. Do not use `latest` or claim that an existing chat session was transferred unless its exact ID was selected. With oomi-ai 0.8.2+, an already-open Hermes conversation uses its existing local gateway owner and exact profile/session. Oomi attaches as another client; it never closes desktop, clears history, deletes a session lock, or substitutes a new chat. When no live owner exists, an Oomi-owned conversation (no `--resume`) runs on a warm `hermes acp` process with oomi-ai 0.9.0+: replies stream as they are written and stop when the person interrupts. Hermes permission requests are denied, as `chat --quiet` denies dangerous commands; ordinary file edits run as they do in quiet mode. A conversation moving from the CLI starts a new Hermes session that receives the recent Oomi history. `--resume` conversations, Hermes without ACP, and `--hermes-transport cli` use `chat --quiet --query-file -` and resume the exact returned `session_id` on subsequent turns.
+Use the user's app URL when provided. Hermes supports `--profile <profile>` and `--resume <exact-session-id>`. Without `--resume`, Oomi starts a persistent conversation with the same configured agent. Do not use `latest` or claim that an existing chat session was transferred unless its exact ID was selected. With oomi-ai 0.8.2+, an already-open Hermes conversation uses its existing local gateway owner and exact profile/session. Oomi attaches as another client; it never closes desktop, clears history, deletes a session lock, or substitutes a new chat. When no live owner exists, an Oomi-owned conversation (no `--resume`) runs on a warm `hermes acp` process with oomi-ai 0.9.0+: replies stream as they are written and stop when the person interrupts. From 0.9.1 the bridge starts Hermes and reopens recent conversations ahead of time (at bridge start and when a call opens), so the first message doesn't wait for Hermes to start. Hermes permission requests are denied, as `chat --quiet` denies dangerous commands; ordinary file edits run as they do in quiet mode. A conversation moving from the CLI starts a new Hermes session that receives the recent Oomi history. `--resume` conversations, Hermes without ACP, and `--hermes-transport cli` use `chat --quiet --query-file -` and resume the exact returned `session_id` on subsequent turns.
 
 Shared desktop conversations require Hermes's loopback WebSocket gateway, active-session discovery, and durable prompt/reply row IDs. Busy conversations ask you to retry after the current task. If a simultaneous desktop send queues your message without a reply receipt, or the connection drops after sending, check the same Hermes chat before resending. Oomi cannot safely repeat an uncertain action. Human approvals stay in the existing Hermes desktop UI. Shared photo submission is not yet supported; use Hermes desktop for that photo. Older or terminal-only owners without a shared gateway receive an actionable error, never a competing process. The shared owner keeps its existing environment, so use the explicit Oomi `--connection NAME` for account commands.