@rubytech/taskmaster 1.11.2 → 1.12.1
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.
- package/dist/agents/skills/workspace.js +3 -0
- package/dist/agents/tools/brand-settings-tool.js +7 -2
- package/dist/agents/tools/channel-settings-tool.js +18 -4
- package/dist/agents/tools/public-chat-settings-tool.js +15 -5
- package/dist/agents/tools/system-status-tool.js +24 -6
- package/dist/build-info.json +3 -3
- package/dist/config/port-defaults.js +0 -8
- package/dist/config/zod-schema.js +24 -1
- package/dist/control-ui/assets/{index-s8s_YKvR.js → index-4h8fLLNN.js} +395 -381
- package/dist/control-ui/assets/index-4h8fLLNN.js.map +1 -0
- package/dist/control-ui/index.html +1 -1
- package/dist/gateway/control-ui.js +25 -10
- package/dist/gateway/public-chat/deliver-email.js +5 -5
- package/dist/gateway/public-chat/deliver-otp.js +50 -16
- package/dist/gateway/public-chat/deliver-sms.js +53 -14
- package/dist/gateway/public-chat-api.js +35 -15
- package/dist/gateway/server-methods/public-chat.js +13 -6
- package/package.json +1 -1
- package/skills/brevo/references/sms-credits.md +28 -20
- package/taskmaster-docs/USER-GUIDE.md +51 -8
- package/dist/control-ui/assets/index-s8s_YKvR.js.map +0 -1
|
@@ -557,6 +557,31 @@ Your assistant can manage who has admin access — the same as using the Admins
|
|
|
557
557
|
- "Who are my current admins?"
|
|
558
558
|
- "Remove the old number ending in 789 from admins"
|
|
559
559
|
|
|
560
|
+
### System Administration
|
|
561
|
+
|
|
562
|
+
Your assistant can check and manage many system settings directly through chat — the same things you'd normally check in the Setup page on the control panel. Think of it as a shortcut: instead of opening the control panel and navigating to the right setting, just ask.
|
|
563
|
+
|
|
564
|
+
| Capability | Description |
|
|
565
|
+
|------------|-------------|
|
|
566
|
+
| System status | Check gateway health, WhatsApp/iMessage connections, Claude authentication, license, software version |
|
|
567
|
+
| Usage and cost | See how many tokens you've used and what it's costing, broken down by provider |
|
|
568
|
+
| Channel settings | Change the AI model, thinking level, DM policy, or group chat policy for your WhatsApp accounts |
|
|
569
|
+
| Branding | Update your accent or background colour |
|
|
570
|
+
| Public chat | Enable or disable the public chat widget, change the greeting, set visitor verification |
|
|
571
|
+
| Skills | List, create, delete, or toggle skills |
|
|
572
|
+
| Logs | Review system and session logs for troubleshooting |
|
|
573
|
+
|
|
574
|
+
**Try asking:**
|
|
575
|
+
- "How's the system doing?"
|
|
576
|
+
- "What's my usage this month?"
|
|
577
|
+
- "Is WhatsApp connected?"
|
|
578
|
+
- "Switch WhatsApp to a cheaper model"
|
|
579
|
+
- "Change the accent colour to blue"
|
|
580
|
+
- "Enable public chat"
|
|
581
|
+
- "Show me the recent logs"
|
|
582
|
+
|
|
583
|
+
> **Note:** Some things still need the control panel: scanning WhatsApp QR codes, uploading logos, WiFi setup, Tailscale remote access, and PIN management. Your assistant will tell you when to open the control panel and where to go.
|
|
584
|
+
|
|
560
585
|
### Web Browsing
|
|
561
586
|
|
|
562
587
|
Your assistant can open and interact with websites in a built-in browser — filling in forms, clicking buttons, and navigating pages. You can watch what it's doing on the **Browser** page in real time, and take over if it needs help (for example, to complete a CAPTCHA or log in to a site).
|
|
@@ -1001,6 +1026,21 @@ If the Pi checks pass but the control panel still doesn't load from another devi
|
|
|
1001
1026
|
2. **Check you're on the same subnet** — mDNS only works between devices on the same network subnet. It won't work across separate subnets, VLANs, or guest networks. A common cause: the Pi is on Ethernet while your device is on WiFi, and your router assigns them to different subnets. Check by comparing the first three groups of your IP addresses (e.g. if the Pi is `192.168.88.4` and your laptop is `192.168.10.172`, they're on different subnets).
|
|
1002
1027
|
3. **Contact support** with: what you changed (port/hostname), the output of `hostname`, `grep 127.0.1.1 /etc/hosts`, and `taskmaster daemon status`.
|
|
1003
1028
|
|
|
1029
|
+
#### Hostname changed to `taskmaster-2.local` (or similar)
|
|
1030
|
+
|
|
1031
|
+
If your control panel URL suddenly stops working and you notice the hostname has a `-2` (or `-3`) suffix, the Pi detected a name conflict on the network and renamed itself.
|
|
1032
|
+
|
|
1033
|
+
**When this happens:** If you unplug the Ethernet cable while the Pi is already running on WiFi, the Pi briefly had two network connections active at the same time. Its hostname detection saw its own name coming from the Ethernet side and treated it as a conflict, adding a `-2` suffix.
|
|
1034
|
+
|
|
1035
|
+
**Fix:**
|
|
1036
|
+
|
|
1037
|
+
1. Power the Pi off completely (not just restart — fully power off)
|
|
1038
|
+
2. Wait at least 2 minutes (this lets the mDNS name cache clear on all devices on the network)
|
|
1039
|
+
3. Power the Pi back on
|
|
1040
|
+
4. Access the control panel using your normal URL
|
|
1041
|
+
|
|
1042
|
+
**To avoid this in future:** Connect via WiFi first, then remove the Ethernet cable — don't unplug Ethernet while the Pi is running with both cables connected.
|
|
1043
|
+
|
|
1004
1044
|
### Static IP Address
|
|
1005
1045
|
|
|
1006
1046
|
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.
|
|
@@ -1467,16 +1507,19 @@ By default, anyone who opens the public chat can start a conversation immediatel
|
|
|
1467
1507
|
1. Go to the **Setup** page
|
|
1468
1508
|
2. Find the **Public Chat** status card
|
|
1469
1509
|
3. Click the settings icon to open the verification settings modal
|
|
1470
|
-
4. Choose
|
|
1510
|
+
4. Choose an auth mode: **Anonymous** (no verification), **Verified** (must verify before chatting), or **Visitor chooses** (can chat immediately or verify for cross-device continuity)
|
|
1511
|
+
5. Select which verification channels to enable — three independent checkboxes:
|
|
1512
|
+
|
|
1513
|
+
| Channel | How it works | What you need |
|
|
1514
|
+
|---------|-------------|---------------|
|
|
1515
|
+
| **WhatsApp** | Verification code sent via WhatsApp | A connected WhatsApp account |
|
|
1516
|
+
| **SMS** | Verification code sent by text message | Same [Brevo](https://brevo.com) API key as email, plus prepaid SMS credits in your Brevo account |
|
|
1517
|
+
| **Email** | Verification code sent by email | A [Brevo](https://brevo.com) API key and a verified sender (free, no credit card) |
|
|
1471
1518
|
|
|
1472
|
-
|
|
1473
|
-
|--------|-------------|---------------|
|
|
1474
|
-
| **Anonymous** | No verification — visitors chat immediately | Nothing (default) |
|
|
1475
|
-
| **Email OTP** | Visitors enter their email, receive a one-time code | A [Brevo](https://brevo.com) API key and a verified sender (free, no credit card). The sender address is configured in Brevo, not in Taskmaster. |
|
|
1476
|
-
| **SMS OTP** | Visitors enter their phone number, receive a one-time code | Same [Brevo](https://brevo.com) API key as email, plus prepaid SMS credits in your Brevo account |
|
|
1519
|
+
When both WhatsApp and SMS are enabled, phone verification tries WhatsApp first and falls back to SMS. To use SMS only, uncheck WhatsApp.
|
|
1477
1520
|
|
|
1478
|
-
|
|
1479
|
-
|
|
1521
|
+
6. Enter your provider credentials — add the Brevo API key in the **API Keys** section on the Setup page. The same key serves both email and SMS verification. For SMS, purchase SMS credits in your Brevo dashboard.
|
|
1522
|
+
7. Settings auto-save when you change a checkbox or leave a field
|
|
1480
1523
|
|
|
1481
1524
|
Once enabled, visitors must authenticate before they can send their first message. Verified contact details are stored and available to the agent via the `verify_contact` tool, so your assistant knows who it's talking to.
|
|
1482
1525
|
|