@rubytech/taskmaster 1.0.10 → 1.0.12

package/dist/gateway/server-methods/sessions-transcript.js

@@ -39,7 +39,7 @@ function extractTextFromContentBlocks(blocks) {
     }
     return parts.join("\n");
 }
-function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs) {
+function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs, maxChars = CONTENT_MAX_CHARS) {
     const entries = [];
     const ts = resolveTimestamp(line, fileMtimeMs);
     const model = line.message?.model;
@@ -57,7 +57,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
             agentId,
             timestamp: ts,
             type: "error",
-            content: truncate(content, CONTENT_MAX_CHARS),
+            content: truncate(content, maxChars),
             ...(model ? { model } : {}),
         });
         return entries;
@@ -74,7 +74,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
             agentId,
             timestamp: ts,
             type: "tool",
-            content: truncate(content, CONTENT_MAX_CHARS),
+            content: truncate(content, maxChars),
             ...(line.toolName ? { toolName: line.toolName } : {}),
             ...(model ? { model } : {}),
         });
@@ -93,7 +93,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
                 agentId,
                 timestamp: ts,
                 type: entryType,
-                content: truncate(msg.content, CONTENT_MAX_CHARS),
+                content: truncate(msg.content, maxChars),
                 ...(model ? { model } : {}),
             });
             return entries;
@@ -113,7 +113,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
                     agentId,
                     timestamp: ts,
                     type: "thinking",
-                    content: truncate(text, CONTENT_MAX_CHARS),
+                    content: truncate(text, maxChars),
                     ...(model ? { model } : {}),
                 });
             }
@@ -127,7 +127,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
                     agentId,
                     timestamp: ts,
                     type: "tool",
-                    content: truncate(content, CONTENT_MAX_CHARS),
+                    content: truncate(content, maxChars),
                     ...(toolName ? { toolName } : {}),
                     ...(model ? { model } : {}),
                 });
@@ -143,7 +143,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
                     agentId,
                     timestamp: ts,
                     type: entryType,
-                    content: truncate(text, CONTENT_MAX_CHARS),
+                    content: truncate(text, maxChars),
                     ...(model ? { model } : {}),
                 });
             }
@@ -161,7 +161,7 @@ function expandLineToEntries(line, sessionId, sessionKey, agentId, fileMtimeMs)
                     agentId,
                     timestamp: ts,
                     type: entryType,
-                    content: truncate(text, CONTENT_MAX_CHARS),
+                    content: truncate(text, maxChars),
                     ...(model ? { model } : {}),
                 });
             }
@@ -217,6 +217,7 @@ export const sessionsTranscriptHandlers = {
         const limit = p.limit ?? DEFAULT_LIMIT;
         const maxBytesPerFile = p.maxBytesPerFile ?? DEFAULT_MAX_BYTES_PER_FILE;
         const inputCursors = p.cursors ?? {};
+        const contentMaxChars = p.full ? Infinity : CONTENT_MAX_CHARS;
         const agentFilter = p.agents && p.agents.length > 0 ? new Set(p.agents) : null;
         try {
             const cfg = loadConfig();
@@ -285,7 +286,7 @@ export const sessionsTranscriptHandlers = {
                     catch {
                         continue;
                     }
-                    const expanded = expandLineToEntries(parsed, sessionId, sessionKey, agentId, result.fileMtimeMs);
+                    const expanded = expandLineToEntries(parsed, sessionId, sessionKey, agentId, result.fileMtimeMs, contentMaxChars);
                     allEntries.push(...expanded);
                 }
             }

package/dist/gateway/server-methods.js

@@ -16,6 +16,7 @@ import { filesHandlers } from "./server-methods/files.js";
 import { healthHandlers } from "./server-methods/health.js";
 import { licenseHandlers } from "./server-methods/license.js";
 import { logsHandlers } from "./server-methods/logs.js";
+import { memoryHandlers } from "./server-methods/memory.js";
 import { recordsHandlers } from "./server-methods/records.js";
 import { modelsHandlers } from "./server-methods/models.js";
 import { nodeHandlers } from "./server-methods/nodes.js";
@@ -88,6 +89,7 @@ const READ_METHODS = new Set([
     "records.search",
     "workspaces.list",
     "workspaces.scan",
+    "memory.status",
 ]);
 const WRITE_METHODS = new Set([
     "send",
@@ -172,7 +174,8 @@ function authorizeGatewayMethod(method, client) {
         method === "records.setField" ||
         method === "records.deleteField" ||
         method === "workspaces.create" ||
-        method === "workspaces.remove") {
+        method === "workspaces.remove" ||
+        method === "memory.reindex") {
         return errorShape(ErrorCodes.INVALID_REQUEST, "missing scope: operator.admin");
     }
     return errorShape(ErrorCodes.INVALID_REQUEST, "missing scope: operator.admin");
@@ -209,6 +212,7 @@ export const coreGatewayHandlers = {
     ...filesHandlers,
     ...browserScreencastHandlers,
     ...licenseHandlers,
+    ...memoryHandlers,
     ...recordsHandlers,
     ...workspacesHandlers,
 };

package/dist/memory/manager.js

@@ -1297,6 +1297,8 @@ export class MemoryIndexManager {
         }
         const vectorReady = await this.ensureVectorReady();
         const meta = this.readMeta();
+        const sourcesChanged = meta?.sources != null &&
+            JSON.stringify([...meta.sources].sort()) !== JSON.stringify([...this.sources].sort());
         const needsFullReindex = params?.force ||
             !meta ||
             meta.model !== this.provider.model ||
@@ -1304,7 +1306,16 @@ export class MemoryIndexManager {
             meta.providerKey !== this.providerKey ||
             meta.chunkTokens !== this.settings.chunking.tokens ||
             meta.chunkOverlap !== this.settings.chunking.overlap ||
-            (vectorReady && !meta?.vectorDims);
+            (vectorReady && !meta?.vectorDims) ||
+            sourcesChanged;
+        // Detect missing memory index: source enabled but no files indexed (legacy DB or failed initial sync)
+        if (!needsFullReindex && this.sources.has("memory") && !this.dirty) {
+            const memoryFileCount = this.db.prepare("SELECT COUNT(*) as c FROM files WHERE source = ?").get("memory").c;
+            if (memoryFileCount === 0) {
+                log.info("memory source enabled but no memory files indexed — marking dirty");
+                this.dirty = true;
+            }
+        }
         try {
             if (needsFullReindex) {
                 await this.runSafeReindex({
@@ -1331,6 +1342,10 @@ export class MemoryIndexManager {
             else {
                 this.sessionsDirty = false;
             }
+            // Persist sources to meta if missing (backfill for legacy databases)
+            if (meta && !meta.sources) {
+                this.writeMeta({ ...meta, sources: Array.from(this.sources) });
+            }
         }
         catch (err) {
             const reason = err instanceof Error ? err.message : String(err);
@@ -1455,6 +1470,7 @@ export class MemoryIndexManager {
                 providerKey: this.providerKey,
                 chunkTokens: this.settings.chunking.tokens,
                 chunkOverlap: this.settings.chunking.overlap,
+                sources: Array.from(this.sources),
             };
             if (this.vector.available && this.vector.dims) {
                 nextMeta.vectorDims = this.vector.dims;

package/dist/memory/memory-schema.js

@@ -60,6 +60,10 @@ export function ensureMemoryIndexSchema(params) {
             const message = err instanceof Error ? err.message : String(err);
             ftsAvailable = false;
             ftsError = message;
+            // Drop orphaned FTS shadow tables when the fts5 module is unavailable.
+            // Leaving them in the DB can cause "no such module: fts5" errors on
+            // unrelated operations if SQLite touches the virtual table machinery.
+            dropOrphanedFtsTables(params.db, params.ftsTable);
         }
     }
     ensureColumn(params.db, "files", "source", "TEXT NOT NULL DEFAULT 'memory'");
@@ -68,9 +72,27 @@ export function ensureMemoryIndexSchema(params) {
     params.db.exec(`CREATE INDEX IF NOT EXISTS idx_chunks_source ON chunks(source);`);
     return { ftsAvailable, ...(ftsError ? { ftsError } : {}) };
 }
+/**
+ * When fts5 module is unavailable but the virtual table and its shadow tables
+ * exist from a previous run, drop them to prevent "no such module" errors.
+ * Shadow tables follow the pattern: {ftsTable}_config, _content, _data, _docsize, _idx.
+ */
+function dropOrphanedFtsTables(db, ftsTable) {
+    const shadowSuffixes = ["_config", "_content", "_data", "_docsize", "_idx"];
+    for (const suffix of shadowSuffixes) {
+        try {
+            db.prepare(`DROP TABLE IF EXISTS ${ftsTable}${suffix}`).run();
+        }
+        catch { }
+    }
+    try {
+        db.prepare(`DROP TABLE IF EXISTS ${ftsTable}`).run();
+    }
+    catch { }
+}
 function ensureColumn(db, table, column, definition) {
     const rows = db.prepare(`PRAGMA table_info(${table})`).all();
     if (rows.some((row) => row.name === column))
         return;
-    db.exec(`ALTER TABLE ${table} ADD COLUMN ${column} ${definition}`);
+    db.prepare(`ALTER TABLE ${table} ADD COLUMN ${column} ${definition}`).run();
 }

package/dist/web/auto-reply/monitor.js

@@ -230,7 +230,7 @@ export async function monitorWebChannel(verbose, listenerFactory = monitorWebInb
                     heartbeatLogger.warn(logData, "⚠️ web gateway heartbeat - no messages in 30+ minutes");
                 }
                 else {
-                    heartbeatLogger.info(logData, "web gateway heartbeat");
+                    heartbeatLogger.debug(logData, "web gateway heartbeat");
                 }
             }, heartbeatSeconds * 1000);
             watchdogTimer = setInterval(() => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/taskmaster",
-  "version": "1.0.10",
+  "version": "1.0.12",
   "description": "AI-powered business assistant for small businesses",
   "publishConfig": {
     "access": "public"

package/taskmaster-docs/USER-GUIDE.md

@@ -38,7 +38,7 @@ You'll need a monitor, keyboard, and mouse connected to the Pi.
 1. Open **Terminal** from the desktop taskbar (or press Ctrl+Alt+T)
 2. Run:
 
-```
+```bash
 curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 ```
 
@@ -51,7 +51,7 @@ curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 
 Open **Terminal** (search for "Terminal" in Spotlight) and run:
 
-```
+```bash
 curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 ```
 
@@ -59,10 +59,12 @@ This installs Node.js (if needed), Taskmaster, and sets up the background servic
 
 **Custom port:** If you're running multiple Taskmaster instances (e.g., one on a Pi and one on a Mac), give each a different port:
 
-```
+```bash
 curl -fsSL https://taskmaster.bot/install.sh | sudo bash -s -- --port 19000
 ```
 
+When using a custom port, the hostname includes the port to avoid conflicts. The setup URL becomes `http://taskmaster-19000.local:19000/setup`.
+
 ### Option D: Install from a package file
 
 If you received a `.tgz` package file (for offline install or when the install script isn't available):
@@ -70,7 +72,7 @@ If you received a `.tgz` package file (for offline install or when the install s
 1. **Install Node.js** (version 22 or later) from [nodejs.org](https://nodejs.org) if you don't have it
 2. Open a terminal and run:
 
-```
+```bash
 npm install -g ~/Downloads/rubytech-taskmaster-2026.2.14.tgz
 taskmaster provision
 ```
@@ -263,6 +265,8 @@ Your assistant can send messages, images, and reactions on your behalf — and r
 
 Your assistant can search, read, and update your business knowledge. It has full file access within your account workspace — it can create, read, update, and organise files. Files uploaded or dragged onto the Files page are automatically indexed for search.
 
+The Files page shows a **status indicator** next to the Re-index button — a green light means the index is up to date, red means files have changed since the last index. The indicator also shows the number of indexed files and chunks. If the light is red or search results seem stale, click **Re-index** to rebuild the search index.
+
 | Capability | Description |
 |------------|-------------|
 | Search knowledge | Find information across all your business files and notes |
@@ -345,6 +349,32 @@ Your assistant can manage recurring tasks, reminders, and automated routines. Yo
 - "Set up a daily briefing at 7am every weekday"
 - "Create a weekly reminder to check stock levels every Monday"
 
+### Proactive Outreach
+
+Your assistant doesn't just respond to incoming messages — it reaches out on your behalf to win work, chase payments, and keep customers engaged.
+
+| Capability | Description |
+|------------|-------------|
+| Quote follow-up | Automatically nudges customers who haven't responded to a quote (default: 3 days) |
+| Invoice reminders | Sends friendly payment reminders when invoices are overdue |
+| Service reminders | Contacts past customers when it's time for a repeat service or annual check |
+| Morning briefings | Sends you a daily schedule summary with jobs, pending quotes, and overdue invoices |
+| ETA updates | Proactively tells customers when you're running late, before they call to ask |
+| Re-engagement | Follows up on old enquiries to see if a customer is still interested |
+
+**How it works:**
+
+Your assistant learns your customers, their service history, and your pricing through normal conversations. It then uses scheduled events (visible under **Events** on the Advanced page) to trigger outreach at the right time. You don't need to configure anything manually — the assistant sets up follow-ups as part of its normal workflow.
+
+**What you can customise:**
+
+- Quote follow-up timing — tell your assistant "follow up on quotes after 5 days instead of 3"
+- Invoice reminder timing — "send invoice reminders after 7 days"
+- Morning briefing time — "send my briefing at 6:30am instead of 7am"
+- Service reminder intervals — "remind customers about annual services 11 months after their last visit"
+
+All outreach messages are sent as your assistant — customers reply normally and the conversation continues.
+
 ### Conversations & Sessions
 
 Your assistant can review conversation history and check what customers have been asking about.
@@ -451,7 +481,7 @@ The **Files** page shows your assistant's knowledge — everything it knows abou
 
 All files are markdown (`.md`) — plain text with simple formatting. You can upload new files by dragging them onto the Files page.
 
-When you add or change a file, your assistant picks it up automatically — no restart needed.
+When you add or change a file, your assistant picks it up automatically — no restart needed. The status light on the Files page turns red when files have changed since the last index, so you can see at a glance whether a re-index is needed.
 
 ---
 
@@ -664,7 +694,7 @@ iMessage support requires two things on your Mac **before** running Taskmaster s
    Homebrew needs a current version of Xcode to compile the iMessage helper. Check which situation applies to you:
 
    - **If you don't have Xcode at all** — open Terminal and run:
-     ```
+     ```bash
      xcode-select --install
      ```
      A dialog will appear — click **Install** and wait for it to finish.
@@ -672,13 +702,13 @@ iMessage support requires two things on your Mac **before** running Taskmaster s
    - **If you have Xcode from the App Store but it's outdated** — open the **App Store**, find Xcode, and click **Update**. This is the most common issue.
 
    - **If you don't want to update Xcode** — you can tell your Mac to use the standalone Command Line Tools instead (faster, no large download). Open Terminal and run:
-     ```
+     ```bash
      sudo xcode-select --switch /Library/Developer/CommandLineTools
      ```
      Enter your password when prompted. This leaves Xcode.app untouched but tells Homebrew to use the lightweight tools.
 
 2. **Homebrew** — if you don't already have it, open Terminal and run:
-   ```
+   ```bash
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
    ```
 
@@ -700,7 +730,7 @@ Taskmaster's iMessage helper needs permission to read the Messages database. mac
 
 Some Homebrew-installed binaries are unsigned. macOS Full Disk Access silently rejects unsigned binaries — they won't appear in the list even after you add them. Open Terminal and run:
 
-```
+```bash
 sudo codesign --force --sign - $(realpath $(which imsg))
 sudo codesign --force --sign - $(realpath $(which node))
 ```
@@ -722,7 +752,7 @@ You can verify it worked by running `imsg chats --limit 5` in Terminal — if yo
 The gateway runs as a background service using Node.js. Terminal's access doesn't apply to background services, so Node.js needs its own entry.
 
 1. Open Terminal and run:
-   ```
+   ```bash
    realpath $(which node)
    ```
    This prints the real path — something like `/usr/local/Cellar/node/23.3.0/bin/node` or `/Users/you/.nvm/versions/node/v22.22.0/bin/node`.
@@ -752,7 +782,7 @@ This means Homebrew found an outdated Xcode.app on your Mac. Three options:
 
 1. **Update Xcode** — open the App Store and update Xcode
 2. **Switch to Command Line Tools** (no download needed) — open Terminal and run:
-   ```
+   ```bash
    sudo xcode-select --switch /Library/Developer/CommandLineTools
    ```
 3. **Install Command Line Tools** (if you don't have them) — run `xcode-select --install`
@@ -805,7 +835,8 @@ You need the IP address to connect from another device on your network (e.g., SS
 **From your Mac or PC** (without a monitor on the Pi):
 
 - **Before install:** Run `ping -c 1 raspberrypi.local` — a fresh Pi advertises this hostname by default
-- **After install:** Run `ping -c 1 taskmaster.local` — the install changes the hostname to `taskmaster`
+- **After install (default port):** Run `ping -c 1 taskmaster.local` — the install changes the hostname to `taskmaster`
+- **After install (custom port):** Run `ping -c 1 taskmaster-19000.local` — when using `--port 19000`, the hostname includes the port
 - **Router:** Check your router's admin page (usually `192.168.1.1`) — look for a device called "taskmaster" or "raspberrypi" in the connected devices list
 
 Once you have the IP, you can access the setup page at `http://<your-pi-ip>:18789/setup` or connect via SSH with `ssh pi@<your-pi-ip>`.

package/templates/customer/agents/admin/AGENTS.md

@@ -42,14 +42,15 @@ Use the owner's name naturally in conversation (you'll find it in USER.md).
 
 ---
 
-## Activity = Sessions First
+## Activity & Recent History
 
-When asked about "activity", "what's happened", or similar:
+When asked about "activity", "what happened", or similar:
 
-1. **Sessions are the source of truth** — that's where conversations live
-2. **Memory is context** — notes, decisions, and summaries you stored about what happened
+1. **Your conversation log first** — `memory/admin/conversations/YYYY-MM.md` is your own record of what you said and did. This is the most complete source, especially when sessions have been reset.
+2. **Sessions (current + previous)** — use `sessions_list` to see active sessions. Each entry may have a `previousSessions` array listing archived sessions. Pass a previous `sessionId` to `sessions_history` to read its transcript.
+3. **Memory** — notes, decisions, and summaries you stored about what happened.
 
-Check sessions first, then enrich with memory.
+Do not rely solely on the current session. Sessions reset on `/new`, auto-recovery, and expiry — always check your conversation log and `previousSessions` for the full picture.
 
 ---
 

package/templates/customer/agents/admin/TOOLS.md

@@ -0,0 +1,36 @@
+# TOOLS.md - Local Notes
+
+Skills define *how* tools work. This file is for *your* specifics — the stuff that's unique to your setup.
+
+## What Goes Here
+
+Things like:
+- Camera names and locations
+- SSH hosts and aliases  
+- Preferred voices for TTS
+- Speaker/room names
+- Device nicknames
+- Anything environment-specific
+
+## Examples
+
+```markdown
+### Cameras
+- living-room → Main area, 180° wide angle
+- front-door → Entrance, motion-triggered
+
+### SSH
+- home-server → 192.168.1.100, user: admin
+
+### TTS
+- Preferred voice: "Nova" (warm, slightly British)
+- Default speaker: Kitchen HomePod
+```
+
+## Why Separate?
+
+Skills are shared. Your setup is yours. Keeping them apart means you can update skills without losing your notes, and share skills without leaking your infrastructure.
+
+---
+
+Add whatever helps you do your job. This is your cheat sheet.

package/templates/taskmaster/agents/admin/AGENTS.md

@@ -11,14 +11,15 @@ Before doing anything else:
 
 ---
 
-## Activity = Sessions First
+## Activity & Recent History
 
-When asked about "activity", "what's happened", or similar:
+When asked about "activity", "what happened", or similar:
 
-1. **Sessions are the source of truth** — that's where conversations live
-2. **Memory is context** — notes, decisions, and summaries you stored about what happened
+1. **Your conversation log first** — `memory/admin/conversations/YYYY-MM.md` is your own record of what you said and did. This is the most complete source, especially when sessions have been reset.
+2. **Sessions (current + previous)** — use `sessions_list` to see active sessions. Each entry may have a `previousSessions` array listing archived sessions. Pass a previous `sessionId` to `sessions_history` to read its transcript.
+3. **Memory** — notes, decisions, and summaries you stored about what happened.
 
-Check sessions first, then enrich with memory.
+Do not rely solely on the current session. Sessions reset on `/new`, auto-recovery, and expiry — always check your conversation log and `previousSessions` for the full picture.
 
 ## Multi-Channel
 
@@ -48,6 +49,7 @@ You have access to everything. Use it.
 Full access to all memory:
 - **Store:** Use `memory_write` freely
 - **Retrieve:** Use `memory_search` for any context
+- **Reindex:** Use `memory_reindex` with action `reindex` to rebuild the search index, or `status` to check index health
 - **Cross-agent:** You can see the public agent's conversations
 
 ### Finding Other Conversations

package/templates/tradesupport/agents/admin/AGENTS.md

@@ -42,14 +42,15 @@ Use the owner's name naturally in conversation (you'll find it in USER.md).
 
 ---
 
-## Activity = Sessions First
+## Activity & Recent History
 
-When asked about "activity", "what's happened", or similar:
+When asked about "activity", "what happened", or similar:
 
-1. **Sessions are the source of truth** — that's where conversations live
-2. **Memory is context** — notes, decisions, and summaries you stored about what happened
+1. **Your conversation log first** — `memory/admin/conversations/YYYY-MM.md` is your own record of what you said and did. This is the most complete source, especially when sessions have been reset.
+2. **Sessions (current + previous)** — use `sessions_list` to see active sessions. Each entry may have a `previousSessions` array listing archived sessions. Pass a previous `sessionId` to `sessions_history` to read its transcript.
+3. **Memory** — notes, decisions, and summaries you stored about what happened.
 
-Check sessions first, then enrich with memory.
+Do not rely solely on the current session. Sessions reset on `/new`, auto-recovery, and expiry — always check your conversation log and `previousSessions` for the full picture.
 
 ---