@rubytech/taskmaster 1.0.63 → 1.0.65

package/taskmaster-docs/USER-GUIDE.md

@@ -394,18 +394,25 @@ All outreach messages are sent as your assistant — customers reply normally an
 
 ### Conversations & Sessions
 
-Your assistant can review conversation history and check what customers have been asking about.
+Your assistant has full access to conversation history across all channels — WhatsApp, webchat, iMessage, and group chats. It can find specific messages, review entire conversations, and give you an overview of all activity.
 
 | Capability | Description |
 |------------|-------------|
-| List conversations | See who has been messaging and when |
+| List conversations | See who has been messaging and when — across all channels |
 | Review history | Read back through past conversations with a specific contact |
+| Search messages | Find messages containing specific words or topics |
+| Filter by channel | Show only WhatsApp, webchat, or iMessage messages |
+| Filter by time | Narrow results to a specific date or time range |
+| All activity | Get a summary of messages across all customers and groups at once |
 | Send between sessions | Send a message to a customer outside of an active conversation |
-| Check session status | See whether your assistant is currently in a conversation |
 
 **Try asking:**
-- "Who messaged today?"
-- "What did Sarah ask about yesterday?"
+- "Who messaged today?" — lists all conversations with recent activity
+- "What did Sarah ask about yesterday?" — reviews a specific contact's history
+- "Find any messages that mention boiler" — searches across conversations
+- "Show me all WhatsApp messages from today" — filters by channel
+- "What happened between 9am and 10am?" — filters by time range
+- "Show me all customer messages from today" — aggregates across all conversations
 - "Send a follow-up to the customer who asked about the boiler"
 
 ### Admin Management
@@ -624,6 +631,179 @@ You can filter by:
 
 Both views support **auto-follow** (keeps the view scrolled to the latest entries) and **export** to download a log file.
 
+### Changing Network Settings
+
+You might need to change two network settings after your Pi is deployed:
+
+- **Port** — The number at the end of your control panel URL (e.g., `http://taskmaster.local:18789`)
+- **mDNS hostname** — The friendly name before `.local` (e.g., `taskmaster` in `taskmaster.local`)
+
+#### What is the port and why would I change it?
+
+The port is like an apartment number for your Taskmaster server. The default is 18789.
+
+**When to change it:**
+- Another device on your network is already using port 18789
+- Your router or firewall blocks that port
+- You're running multiple Taskmaster instances and need them on different ports
+
+**What happens when you change it:** Your control panel URL changes. If you set the port to 19000, you'll access Taskmaster at `http://taskmaster.local:19000`.
+
+#### What is the mDNS hostname and why would I change it?
+
+The mDNS hostname is the friendly name you use to access your Pi on your local network. The default is `taskmaster`, so your control panel is at `taskmaster.local`.
+
+**When to change it:**
+- You're running multiple Taskmaster instances on the same network (they'll conflict if they all use `taskmaster.local`)
+- You want custom branding (e.g., `dave.local`, `assistant.local`, `plumbing-helper.local`)
+
+**What happens when you change it:** Your control panel URL changes. If you set the hostname to `dave`, you'll access Taskmaster at `http://dave.local:18789`.
+
+#### How to make these changes
+
+You have two options for accessing your Pi:
+
+**Option 1: Direct Access (Keyboard + Monitor)**
+1. Plug a keyboard and monitor into your Pi
+2. Log in (default user: `taskmaster`, password: `taskmaster`)
+3. Follow the instructions below
+
+**Option 2: SSH (from another computer)**
+1. Open Terminal (Mac/Linux) or PowerShell (Windows)
+2. Connect to your Pi: `ssh admin@taskmaster.local`
+3. Enter the password when prompted (default: `password`)
+4. Follow the instructions below
+
+#### Changing the Port
+
+Once you're logged in (either method):
+
+**Step 1:** Update the configuration
+
+```bash
+taskmaster config set gateway.port 19000
+```
+
+(Replace `19000` with whatever port you want)
+
+**Step 2:** Reinstall the daemon service (this rewrites the service file with the new port)
+
+```bash
+taskmaster daemon install --force
+```
+
+> **Important:** Do not use `taskmaster daemon restart` here — that restarts the service with the old port. You must use `taskmaster daemon install --force` to pick up the new port from the configuration.
+
+**Step 3:** Access the control panel at the new URL: `http://taskmaster.local:19000` (use your new port number)
+
+#### Changing the mDNS Hostname
+
+Once you're logged in (either method):
+
+**Step 1:** Set the new hostname
+
+```bash
+sudo hostnamectl set-hostname dave
+```
+
+(Replace `dave` with whatever name you want — letters and hyphens only, no spaces)
+
+> You will see a warning on every `sudo` command until Step 2 completes: `sudo: unable to resolve host dave: Name or service not known`. This is normal — the hostname was changed but the system hasn't been told where to find it yet. Every command still succeeds despite the warning.
+
+**Step 2:** Update `/etc/hosts` to match
+
+```bash
+sudo sed -i "s/127\.0\.1\.1.*/127.0.1.1\tdave/" /etc/hosts
+```
+
+(Replace `dave` with the same name you used in Step 1. You'll see the same warning one last time — after this command, it's gone.)
+
+**Step 3:** Restart the mDNS service
+
+```bash
+sudo systemctl restart avahi-daemon
+```
+
+> **If you're connected via SSH**, your connection will stop working after this step because the old hostname is no longer valid. Reconnect using the new hostname: `ssh admin@dave.local`
+
+**Step 4:** Access the control panel at the new URL: `http://dave.local:18789` (use your new hostname)
+
+> **Note:** This changes the hostname for the entire Pi, not just Taskmaster.
+
+#### Changing Both
+
+If you need to change both the port and hostname:
+
+1. Change the port first (Steps 1–2 under "Changing the Port")
+2. Change the hostname (Steps 1–2 under "Changing the mDNS Hostname")
+3. Access the control panel at the new combined URL: `http://dave.local:19000` (use your new hostname + new port)
+
+#### Verifying Your Changes
+
+After completing the steps above, run these checks **on the Pi** to confirm everything is correct.
+
+**Check the hostname is set:**
+
+```bash
+hostname
+```
+
+This should print your new hostname (e.g. `dave`).
+
+**Check `/etc/hosts` matches:**
+
+```bash
+grep 127.0.1.1 /etc/hosts
+```
+
+This should show `127.0.1.1` followed by your new hostname (e.g. `127.0.1.1  dave`).
+
+**Check avahi is broadcasting the new hostname:**
+
+```bash
+avahi-resolve -n dave.local
+```
+
+(Replace `dave` with your hostname.) This should print your Pi's IP address. If it says "Failed to resolve", restart avahi: `sudo systemctl restart avahi-daemon` and try again.
+
+**Check the gateway is running on the correct port:**
+
+```bash
+taskmaster daemon status
+```
+
+This shows the port the gateway is listening on. Confirm it matches what you set.
+
+**Test locally on the Pi:**
+
+```bash
+curl -s -o /dev/null -w "%{http_code}" http://localhost:18789
+```
+
+(Use your new port number.) If this prints `200`, the gateway is running. If it fails, restart: `taskmaster daemon restart`.
+
+#### Flushing DNS Cache on Other Devices
+
+The Pi broadcasts its new hostname immediately, but the device you're browsing from (your phone, laptop, etc.) may have cached the old name. If the control panel doesn't load from another device after the Pi checks above all pass, flush the DNS cache on that device:
+
+| Device | Command |
+|--------|---------|
+| **Mac** | `sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder` |
+| **Windows** | `ipconfig /flushdns` (run in PowerShell or Command Prompt) |
+| **Linux** | `avahi-resolve -n dave.local` (probes directly, bypasses cache) |
+| **iPhone / iPad** | Toggle Airplane Mode on and off, or toggle WiFi off and on |
+| **Android** | Toggle WiFi off and on |
+
+After flushing, open your browser and navigate to the new URL (e.g. `http://dave.local:19000`). If you still can't connect, try a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) or open a new private/incognito window to rule out browser caching.
+
+#### Still Can't Connect?
+
+If the Pi checks pass but the control panel still doesn't load from another device:
+
+1. **Use the IP address directly** — on the Pi, run `hostname -I` to get its IP address, then open `http://192.168.1.XXX:18789` (use your IP and port) from the other device. If this works, the problem is mDNS resolution, not the gateway.
+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`.
+
 ---
 
 ## Troubleshooting