npm - @rubytech/taskmaster - Versions diffs - 1.5.1 → 1.5.2 - Mend

@rubytech/taskmaster 1.5.1 → 1.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

package/dist/control-ui/index.html CHANGED Viewed

@@ -6,7 +6,7 @@
     <title>Taskmaster Control</title>
     <meta name="color-scheme" content="dark light" />
     <link rel="icon" type="image/png" href="./favicon.png" />
-    <script type="module" crossorigin src="./assets/index-D-PHW4mO.js"></script>
+    <script type="module" crossorigin src="./assets/index-Ck-xl0xu.js"></script>
     <link rel="stylesheet" crossorigin href="./assets/index-D6WTmXJM.css">
   </head>
   <body>

package/package.json CHANGED Viewed

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

package/taskmaster-docs/USER-GUIDE.md CHANGED Viewed

@@ -994,6 +994,19 @@ If the Pi checks pass but the control panel still doesn't load from another devi
 2. **Check you're on the same network** — mDNS only works between devices on the same WiFi/LAN. It won't work across VLANs or guest networks.
 3. **Contact support** with: what you changed (port/hostname), the output of `hostname`, `grep 127.0.1.1 /etc/hosts`, and `taskmaster daemon status`.
+### Static IP Address
+You don't need to assign a static IP address — Taskmaster uses a `.local` hostname that resolves automatically via mDNS, even if the IP changes after a reboot or DHCP renewal. You'll always find your control panel at the same `.local` address.
+That said, if your IT team prefers to pin devices to static IPs (common on managed business networks), they can do so via DHCP reservation on your router. They'll need the device's MAC address:
+1. SSH into the Pi (see "Enabling SSH" below)
+2. Run: `ip link show`
+3. Look for the `link/ether` line under the active interface (`eth0` for wired, `wlan0` for WiFi)
+4. Give that MAC address to your IT team to create a DHCP reservation
+This is entirely optional and is a network preference, not a Taskmaster requirement.
 ---
 ## Troubleshooting
@@ -1061,6 +1074,21 @@ The gateway is the software that runs your assistant. If it's showing red:
 3. Wait 30 seconds for it to come back online
 4. If still not working, try unplugging your Taskmaster device, waiting 10 seconds, and plugging it back in
+### Assistant not replying during an AI service outage?
+Occasionally, AI providers like Claude experience temporary outages or slowdowns. When this happens, Taskmaster automatically tries to get a reply from a different AI provider instead. Here's how it works:
+- **If you have backup providers configured** (e.g., a Google AI key or OpenAI key added on the Setup page), your assistant switches to those automatically. You don't need to do anything — replies keep coming, just from a different AI model behind the scenes.
+- **If you only have one provider** (e.g., Claude with no other API keys), messages sent during the outage won't get a reply. The customer's message is received but the assistant can't respond until the service recovers.
+- **Messages are not queued.** If a message arrives during an outage and all providers are down, it won't be retried automatically. The customer (or you) will need to send the message again once the service is back.
+- **Your conversation history is safe.** An outage doesn't corrupt or lose any previous conversations. Once the service recovers, everything picks up where it left off.
+**What you can do to stay protected:**
+1. **Add backup API keys** — Go to the **Setup** page, tap **API Keys**, and add keys for Google AI and/or OpenAI alongside your Claude connection. These act as automatic backups.
+2. **Check your logs** — If replies are failing, open **Advanced → Logs → Session Logs** and filter by "errors" to see what's happening.
+3. **Wait it out** — Most AI service outages resolve within minutes to hours. Your assistant will automatically use the primary provider again once it's back.
 ### "sudo: unable to resolve host taskmaster" warning?
 This harmless warning appears when the Pi's hostname isn't listed in `/etc/hosts`. Every `sudo` command still works — it's just a cosmetic message. To fix it, open a terminal on the Pi and run:

package/templates/customer/agents/admin/BOOTSTRAP.md CHANGED Viewed

@@ -64,7 +64,7 @@ If the admin prefers to do it themselves later, they can manage API keys through
 These keys are optional — the assistant works without them. Don't pressure. If the admin wants to skip this and come back later, that's fine.
-If they need help with anything at all — setup, API keys, or general questions — suggest they reach out to **Dave at Taskmaster** via WhatsApp: [wa.me/447591215452](https://wa.me/447591215452).
+If they need help with anything at all — setup, API keys, or general questions — suggest they reach out to **Tuesday at Taskmaster** via WhatsApp: [wa.me/447591215452](https://wa.me/447591215452).
 ## Step 7: Rename the Account