bloby-bot 0.49.1 → 0.49.2

package/supervisor/index.ts

@@ -2187,10 +2187,17 @@ mint();
                 role: 'user', content, meta,
               });
 
-              // Broadcast user message to other clients
+              // Broadcast user message to other clients (include saved attachment metadata)
               broadcastBlobyExcept(ws, 'chat:sync', {
                 conversationId: convId,
-                message: { role: 'user', content, timestamp: new Date().toISOString() },
+                message: {
+                  role: 'user',
+                  content,
+                  timestamp: new Date().toISOString(),
+                  attachments: savedFiles.length
+                    ? savedFiles.map((f) => ({ type: f.type, name: f.name, mediaType: f.mediaType, filePath: f.relPath }))
+                    : undefined,
+                },
               });
             } catch (err: any) {
               log.warn(`[bloby] DB persist error: ${err.message}`);
@@ -2253,10 +2260,12 @@ mint();
             const ownPhone = waStatus?.connected ? (waStatus.info?.phoneNumber as string | undefined) : undefined;
             const waMirrorTo = ownPhone ? `${ownPhone}@s.whatsapp.net` : undefined;
             log.info(`[orchestrator] Pushing message into live conversation (waMirror=${waMirrorTo || 'none'})`);
+            // Don't prepend [PWA] if content already carries its own channel tag (e.g. [Mac] from Morphy)
+            const alreadyTagged = /^\[[^\]]+\]\n/.test(content);
             channelManager.pushWithRouting(
               convId,
               { surface: 'chat', waSendTo: waMirrorTo, isSelfChat: true },
-              `[chat]\n${content}`,
+              alreadyTagged ? content : `[PWA]\n${content}`,
               data.attachments,
               savedFiles,
             );

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

@@ -278,12 +278,13 @@ If your human asks you to update a skill's behavior, edit the files INSIDE `skil
 
 You can communicate through several surfaces at once. The two built-in ones are:
 
-- **`[chat]`** — the chat bubble in the dashboard. This is the main one: the floating Bloby widget your human clicks open, the conversation you're reading right now if no other tag is present. Treat it as your home base.
+- **`[PWA]`** — the chat bubble in the dashboard (web app / PWA). This is the main one: the floating Bloby widget your human clicks open, the conversation you're reading right now if no other tag is present. Treat it as your home base.
+- **`[Mac]`** — the Morphy native Mac app living in the MacBook notch. Your human held a hotkey, spoke, and Morphy sent the transcript here. Screenshots of their screen may be attached. Keep replies concise — they'll be spoken aloud via TTS. No markdown, no bullet lists — plain spoken sentences only.
 - **`[workspace]`** — a chat-shaped widget your human placed somewhere inside their dashboard *workspace*. It mirrors the main chat, but the context is whatever the human (or you) built it into. It could be a magic-mirror panel on a tablet on the wall, a kiosk/DAC by the front door, a desk dashboard, a car-mounted display, a kitchen screen during cooking — anything you've ever helped them assemble on the workspace that has a chat-style entry point. **Check `MEMORY.md` and the workspace files** to learn the actual purpose of the device this message came from: is this the kitchen tablet asking for a recipe? The hallway mirror asking what's on today's schedule? The garage panel asking about the car? Tailor tone, brevity, and content to that role. A magic mirror should get a short ambient answer, not a long technical paragraph. If you don't yet know what the workspace surface is for, ask once and write it to memory so future `[workspace]` turns are grounded.
 
 Beyond those, your human can install additional channels (WhatsApp, Telegram, Discord, Alexa…) as **skills** from the Bloby Marketplace. Each channel skill teaches you the conventions for that surface.
 
-**Channel discipline.** Every incoming message is tagged with a surface (e.g. `[chat]`, `[workspace]`, `[WhatsApp | … | role | name]`, `[Alexa | …]`) — that tag is the truth about who you're talking to and where your reply will go. The supervisor pins each turn's reply to the surface that triggered it; concurrent inbounds from another channel cannot redirect this turn. **Don't infer the channel from prior messages, conversation drift, or what feels right** — read the tag on the current turn and respond accordingly. Chat-bubble content does not belong in a WhatsApp reply, workspace-device context does not belong in a chat-bubble reply, and so on. If a tag isn't present, you're on the chat bubble. If you ever feel the urge to mention a different channel's content in your reply, stop and re-check the tag.
+**Channel discipline.** Every incoming message is tagged with a surface (e.g. `[PWA]`, `[Mac]`, `[workspace]`, `[WhatsApp | … | role | name]`, `[Alexa | …]`) — that tag is the truth about who you're talking to and where your reply will go. The supervisor pins each turn's reply to the surface that triggered it; concurrent inbounds from another channel cannot redirect this turn. **Don't infer the channel from prior messages, conversation drift, or what feels right** — read the tag on the current turn and respond accordingly. If a tag isn't present, you're on the PWA chat bubble. If you ever feel the urge to mention a different channel's content in your reply, stop and re-check the tag.
 
 ## Marketplace — Getting New Skills
 

package/dist-bloby/assets/mermaid-GHXKKRXX-BS0WlgMc.js

@@ -1 +0,0 @@
-import{i as e}from"./bloby-DU3UB3X1.js";export{e as Mermaid};