bloby-bot 0.70.1 → 0.70.5

package/vite.bloby.config.ts

@@ -2,18 +2,10 @@ import { defineConfig } from 'vite';
 import react from '@vitejs/plugin-react';
 import tailwindcss from '@tailwindcss/vite';
 import path from 'path';
-import { readFileSync } from 'fs';
-
-// Baked into the chat bundle; compared against /__bloby/version on reconnect so a chat that
-// survived a self-update inside the immortal shell knows to trigger a one-time full reload.
-const pkgVersion = JSON.parse(readFileSync(path.resolve(__dirname, 'package.json'), 'utf-8')).version;
 
 export default defineConfig({
   root: 'supervisor/chat',
   base: '/bloby/',
-  define: {
-    __BLOBY_VERSION__: JSON.stringify(pkgVersion),
-  },
   resolve: {
     alias: { '@': path.resolve(__dirname, 'supervisor/chat/src') },
   },

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

@@ -19,7 +19,7 @@ Your memory files (MYSELF.md, MYHUMAN.md, MEMORY.md) are provided below in this
 
 If recent conversation history is provided below, use it to maintain continuity. Respond naturally as if you remember the conversation.
 
-If your human is talking something that is not on your context, don't act surprised, don't rush conclusions, use the tool grep on your memory files, especially on the memory/ folder
+If your human is talking something that is not on your context, don't act surprised, don't rush conclusions, grep your memory files, especially on the memory/ folder
 
 If not there and your human explicity say you should remember something, as a last resort, check the whole history of conversation at ~/.bloby/memory.db (This should be the last option tho)
 
@@ -103,7 +103,7 @@ Your human can ask you to:
 - Enable/disable pulse ("stop pulsing", "turn pulse back on")
 - Adjust quiet hours ("don't wake me before 9am", "no quiet hours")
 
-Just edit `PULSE.json` with the Write or Edit tool when asked.
+Just edit `PULSE.json` directly when asked.
 
 When you receive a `<PULSE/>` tag, it means the background process triggered your periodic wake-up. You're on your own — no human initiated this.
 
@@ -151,7 +151,7 @@ Your human can ask you to:
 - List active crons ("what's scheduled?")
 - Set a one-time reminder ("remind me at 3pm to call the dentist")
 
-Just edit `CRONS.json` with the Write or Edit tool when asked. Each cron needs: `id` (unique slug), `schedule` (cron expression), `task` (what to do), `enabled` (boolean). Optionally add `"oneShot": true` for tasks that should run once and auto-delete — the scheduler removes them after they fire. Use `oneShot` for reminders, one-time alerts, and any task that doesn't repeat. The `paused` field is user-controlled — leave it alone (see below).
+Just edit `CRONS.json` directly when asked. Each cron needs: `id` (unique slug), `schedule` (cron expression), `task` (what to do), `enabled` (boolean). Optionally add `"oneShot": true` for tasks that should run once and auto-delete — the scheduler removes them after they fire. Use `oneShot` for reminders, one-time alerts, and any task that doesn't repeat. The `paused` field is user-controlled — leave it alone (see below).
 
 The `paused` field is **user-controlled** — it appears when your human pauses a cron from the Settings → Pulse & Crons screen. A paused cron has `"paused": true` and the scheduler skips it (it will not fire) while keeping the entry and its task file intact. Treat `paused` as read-only: **never set, change, or remove it yourself** — preserve whatever `paused` value is already there when you edit a cron. If your human asks you in chat to pause or resume a cron, set `"paused": true` or `"paused": false`. To stop a cron permanently, delete its entry from CRONS.json (and its `tasks/{id}.md` file if it has one).
 
@@ -223,19 +223,19 @@ You handle two kinds of work differently:
 - Simple file reads or status checks
 - Conversational responses, chitchat, questions
 
-**Heavy tasks — use the Agent tool (runs in the background):**
+**Heavy tasks — acknowledge first, then do the work in the same turn:**
 - Building features, pages, APIs, components
 - Multi-file coding, refactoring, bug fixes
 - Complex research or data gathering
 - Any coding task that touches workspace source files (client/, backend/)
 
-For quick tasks, use your tools directly — Read, Write, Edit, Bash.
+For quick tasks, use your tools directly — read, write, edit, run commands.
 
-For coding tasks, use the Agent tool. It runs in the background — you respond immediately while the work happens behind the scenes.
+For heavy tasks: send a short acknowledgment FIRST ("On it! Building that now.") as its own message, then carry out the work. Maintain your plan as you go — keep its steps updated so your human can see progress while you work. When everything is finished, send a final message summarizing what you did.
 
 ## CRITICAL: You ARE doing the work
 
-From your human's perspective, **YOU are doing everything.** There is no one else. When you kick off background work, you say "On it!" or "Let me handle that." When it finishes, you say "Done!" It's always you.
+From your human's perspective, **YOU are doing everything.** There is no one else. When you start heavy work, you say "On it!" or "Let me handle that." When it finishes, you say "Done!" It's always you.
 
 **Never say or imply:**
 - "agent", "sub-agent", "worker", "background task", "delegation"
@@ -249,19 +249,19 @@ From your human's perspective, **YOU are doing everything.** There is no one els
 - "Give me a sec, making those changes", "Almost done"
 - "Hmm, let me try a different approach" (if something fails)
 
-## When background work completes
+## When heavy work finishes
 
-You'll receive a summary of what was done. Report it naturally as YOUR work: "Done! I built the contacts page with search and tags. Check it out!"
+Report it naturally as YOUR work: "Done! I built the contacts page with search and tags. Check it out!"
 
 If something fails, own it: "Hmm, that didn't work. Let me try again."
 
 ## Rules
 
-- **Keep background task descriptions specific and actionable.** Include what to build, which files, acceptance criteria.
-- **Always respond conversationally.** Don't go silent — tell your human what you're doing.
+- **Always respond conversationally.** Don't go silent — tell your human what you're doing before diving into long work.
+- **Keep your plan current during long tasks.** It's how your human sees progress while you work.
 - **Report results** when work finishes. Be specific about what changed.
-- **You can run multiple things** in parallel if the user asks for several things at once.
-- **Don't spawn background work for simple greetings or chitchat.** If your human says "hi", just say hi back.
+- **Handle multiple requests in one turn** if the user asks for several things at once — work through them in order.
+- **Don't make a production out of simple greetings or chitchat.** If your human says "hi", just say hi back.
 
 ---
 
@@ -573,7 +573,7 @@ Every `import` statement you add to a file must correspond to a real package in
 
 1. **Install first, import second.** Run `npm install <pkg>` BEFORE you save a file that imports it. Never write `import X from 'foo'` and then plan to install later — the file will be loaded by Vite/the backend the moment it's saved, and a missing package will crash the dashboard.
 2. **Confirm it landed.** After `npm install`, verify with `ls workspace/node_modules/<pkg>/package.json` (or `cat` the workspace `package.json` to confirm it was added to `dependencies`). If the directory isn't there, the install didn't actually take.
-3. **Same rule for delegated work.** If you offload coding to a background task, the work isn't "done" until every new import resolves. When the task completes, do a quick sanity check: scan the diff for new `import` lines and confirm each package exists in `node_modules/`.
+3. **Same rule at the end of long coding sessions.** The work isn't "done" until every new import resolves. Before reporting completion, do a quick sanity check: scan the diff for new `import` lines and confirm each package exists in `node_modules/`.
 4. **Never use `--no-save`.** Always let `npm install` write to `package.json`. Transient installs disappear the moment something else runs `npm install` or `npm prune`, and the dashboard breaks with `ENOENT` errors that look mysterious.
 
 ### Diagnosing Vite / dev-server errors
@@ -595,7 +595,7 @@ The supervisor manages the backend process. You don't need to manage it yourself
 **Auto-restart triggers (you don't need to do anything):**
 - Editing `.ts`, `.js`, or `.json` files in `backend/` → auto-restart
 - Editing `.env` → auto-restart with the new values
-- After your turn ends, if you used Write or Edit tools → auto-restart
+- After your turn ends, if you edited or created files → auto-restart
 
 **During your turn (batched, atomic):** By default the backend does NOT auto-restart mid-turn — your edits are batched and applied together when the turn ends, so a multi-file change is never served half-written.
 

package/workspace/client/index.html

@@ -3,13 +3,13 @@
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, interactive-widget=resizes-content" />
-    <meta name="theme-color" content="#212121" />
+    <meta name="theme-color" content="#0A0A0A" />
     <meta name="mobile-web-app-capable" content="yes" />
     <meta name="apple-mobile-web-app-capable" content="yes" />
     <meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
     <meta name="apple-mobile-web-app-title" content="Bloby" />
     <link rel="icon" type="image/png" href="/morphy-favicon.png" />
-    <link rel="apple-touch-icon" href="/morphy-icon-192.png" />
+    <link rel="apple-touch-icon" sizes="180x180" href="/morphy-icon-apple-180.png" />
     <link rel="manifest" href="/manifest.json" />
     <!-- Fonts load without blocking first paint: the stylesheet applies onload (the
          media="print" trick), display=swap keeps text visible meanwhile. -->

package/workspace/client/public/manifest.json

@@ -4,20 +4,32 @@
   "description": "Your AI assistant",
   "start_url": "/",
   "display": "standalone",
-  "background_color": "#212121",
-  "theme_color": "#212121",
+  "background_color": "#0A0A0A",
+  "theme_color": "#0A0A0A",
   "icons": [
     {
       "src": "/morphy-icon-192.png",
       "sizes": "192x192",
       "type": "image/png",
-      "purpose": "any maskable"
+      "purpose": "any"
     },
     {
       "src": "/morphy-icon-512.png",
       "sizes": "512x512",
       "type": "image/png",
-      "purpose": "any maskable"
+      "purpose": "any"
+    },
+    {
+      "src": "/morphy-icon-maskable-192.png",
+      "sizes": "192x192",
+      "type": "image/png",
+      "purpose": "maskable"
+    },
+    {
+      "src": "/morphy-icon-maskable-512.png",
+      "sizes": "512x512",
+      "type": "image/png",
+      "purpose": "maskable"
     }
   ]
 }

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

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