bloby-bot 0.37.0 → 0.38.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bloby-bot",
-  "version": "0.37.0",
+  "version": "0.38.0",
   "releaseNotes": [
     "1. # voice note (PTT bubble)",
     "2. # audio file + caption",

package/supervisor/channels/manager.ts

@@ -736,13 +736,19 @@ export class ChannelManager {
           }).catch(() => {});
         }
 
-        // Handle turn completion — restart backend if file tools were used
-        if (type === 'bot:turn-complete' && eventData.usedFileTools) {
-          this.opts.restartBackend();
+        // Handle turn completion — restart backend if file tools were used,
+        // and tell every chat client the agent is idle so the typing dots
+        // stop. This callback owns the live conversation whenever a WhatsApp
+        // self-chat arrives before the dashboard does, so without this signal
+        // the dashboard's typing indicator would stay on forever.
+        if (type === 'bot:turn-complete') {
+          if (eventData.usedFileTools) this.opts.restartBackend();
+          broadcastBloby('bot:idle', { conversationId: convId });
+          return;
         }
 
         // Don't forward internal events to chat clients
-        if (type === 'bot:turn-complete' || type === 'bot:conversation-ended') return;
+        if (type === 'bot:conversation-ended') return;
 
         // Mirror streaming + task events to chat clients
         broadcastBloby(type, eventData);

package/supervisor/harnesses/codex.ts

@@ -571,6 +571,14 @@ async function spawnAndInitialize(
     conv.threadId = startResult.thread.id;
     conversations.set(conversationId, conv);
     log.ok(`[codex] thread started ${conv.threadId}`);
+
+    // Prime codex's per-thread skill cache with the workspace skills
+    // directory. Without this, codex only sees its system-scope skills and
+    // never discovers anything Bloby ships in `workspace/skills/*`. Fire and
+    // forget — failure here just means workspace skills won't be auto-routable
+    // for this thread, but the agent can still read SKILL.md files directly.
+    primeWorkspaceSkills(rpc);
+
     return conv;
   } catch (err: any) {
     rpc.close();
@@ -579,6 +587,28 @@ async function spawnAndInitialize(
   }
 }
 
+const SKILLS_DIR = path.join(WORKSPACE_DIR, 'skills');
+
+function primeWorkspaceSkills(rpc: CodexRpc): void {
+  rpc.request('skills/list', {
+    cwds: [WORKSPACE_DIR],
+    forceReload: true,
+    perCwdExtraUserRoots: [{
+      cwd: WORKSPACE_DIR,
+      extraUserRoots: [SKILLS_DIR],
+    }],
+  }).then((result: any) => {
+    const entry = result?.data?.[0];
+    const all = entry?.skills ?? [];
+    const workspace = all.filter((s: any) => s.scope !== 'system');
+    const errors = entry?.errors ?? [];
+    log.ok(`[codex] skills primed: ${workspace.length} workspace, ${all.length - workspace.length} system${errors.length ? `, ${errors.length} rejected` : ''}`);
+    for (const err of errors) log.warn(`[codex] skill load error: ${err.path} — ${err.message}`);
+  }).catch((err: any) => {
+    log.warn(`[codex] skills/list failed: ${err.message}`);
+  });
+}
+
 /* ── Harness implementation ────────────────────────────────────────────── */
 
 export function hasConversation(conversationId: string): boolean {
@@ -792,6 +822,10 @@ export async function runAgentQuery(req: AgentQueryRequest): Promise<AgentQueryR
       resolvedThreadId = r.thread.id;
     }
 
+    // Same priming as live conversations — workspace skills won't be visible
+    // to codex's router otherwise.
+    primeWorkspaceSkills(rpc);
+
     const turnParams: Record<string, any> = {
       threadId: resolvedThreadId,
       input: [{ type: 'text', text: req.message }],

package/worker/prompts/bloby-system-prompt.txt

@@ -266,9 +266,9 @@ If something fails, own it: "Hmm, that didn't work. Let me try again."
 
 ## Skills
 
-Skills live in `skills/` — each skill is a folder with instructions and resources. Each skill has a `SKILL.md` with instructions for you on how to use it.
+Skills live in `skills/` — each skill is a folder containing a `SKILL.md` that explains what the skill does and how to use it. When a user request matches a skill's purpose (e.g. they mention WhatsApp and a `whatsapp` skill exists), open that skill's `SKILL.md` and follow its guidance. List `skills/` whenever you're unsure what's installed.
 
-Your installed skills and their SKILL.md contents are injected into your context automatically. If your human asks you to update a skill's behavior, edit the files INSIDE `skills/{skill-name}/`.
+If your human asks you to update a skill's behavior, edit the files INSIDE `skills/{skill-name}/`.
 
 **IMPORTANT: When editing skill files, always use the full path inside the skill directory.**
 - Correct: `skills/my-skill/SCRIPT.md`