@rubytech/taskmaster 1.3.0 → 1.4.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rubytech/taskmaster",
3
- "version": "1.3.0",
3
+ "version": "1.4.1",
4
4
  "description": "AI-powered business assistant for small businesses",
5
5
  "publishConfig": {
6
6
  "access": "public"
@@ -202,6 +202,32 @@ If you forget your PIN, you'll need to edit the configuration file on the device
202
202
 
203
203
  ---
204
204
 
205
+ ## Secure Connection (HTTPS)
206
+
207
+ Taskmaster automatically uses a secure (HTTPS) connection when you access it from another device on your network. This is required for features like voice notes, which need microphone access — browsers only allow microphone use on secure connections.
208
+
209
+ ### First-Time Certificate Warning
210
+
211
+ The first time you open Taskmaster in your browser, you'll see a security warning that says something like **"Your connection is not private"** or **"This site's certificate is not trusted."** This is normal and expected.
212
+
213
+ Taskmaster creates its own security certificate so your connection is encrypted. Because it's self-issued (not from a public authority like Google or Let's Encrypt), your browser doesn't recognise it automatically. Your data is still encrypted — the warning is about trust, not security.
214
+
215
+ **To proceed:**
216
+
217
+ - **Chrome / Edge:** Click **Advanced**, then **Proceed to taskmaster.local (unsafe)**
218
+ - **Safari:** Click **Show Details**, then **visit this website**, then confirm
219
+ - **Firefox:** Click **Advanced**, then **Accept the Risk and Continue**
220
+
221
+ You only need to do this once per browser. After accepting, the warning won't appear again until the certificate expires (1 year).
222
+
223
+ > **Tip (Mac):** To permanently trust the certificate and remove the warning entirely, open Terminal and run:
224
+ > ```
225
+ > sudo security add-trusted-cert -d -r trustAsRoot -k /Library/Keychains/System.keychain ~/.taskmaster/tls/gateway-cert.pem
226
+ > ```
227
+ > Enter your Mac password when prompted. After this, all browsers on that Mac will trust Taskmaster's certificate.
228
+
229
+ ---
230
+
205
231
  ## Two Assistants, One WhatsApp
206
232
 
207
233
  Taskmaster runs two assistants on the same WhatsApp number, each with a different job:
@@ -247,7 +273,7 @@ You can record and send voice notes directly from the Chat page. When the messag
247
273
  - **Tap** the microphone to start recording. A recording indicator with a timer appears. Tap the **send button** to send, or the **trash button** to discard.
248
274
  - **Press and hold** the microphone to record hands-free. Release to send automatically, or slide left to cancel.
249
275
 
250
- Your assistant transcribes the voice note and responds to the content, the same as a WhatsApp voice note.
276
+ Your assistant transcribes the voice note and responds to the content, the same as a WhatsApp voice note. Sent voice notes appear as audio players in the conversation so you can replay them.
251
277
 
252
278
  ### Sending Messages While the Assistant is Working
253
279
 
@@ -977,7 +1003,7 @@ If the Pi checks pass but the control panel still doesn't load from another devi
977
1003
  If you can't load the Control Panel in your browser:
978
1004
 
979
1005
  1. **Same network?** — Make sure your device is on the same WiFi or LAN as Taskmaster
980
- 2. **Check the URL** — go to **http://taskmaster.local:18789**. Make sure you're using `http` (not `https`) and port `18789`
1006
+ 2. **Check the URL** — go to **http://taskmaster.local:18789** (the browser will redirect to HTTPS automatically). If you see a certificate warning, see "Secure Connection (HTTPS)" above
981
1007
  3. **Wait for boot** — after powering on the device, it takes 2–3 minutes for everything to start. If you just plugged it in, give it a moment
982
1008
  4. **Try a different browser** — some browsers (especially on older devices) have trouble with `.local` addresses. Try Chrome or Safari
983
1009
  5. **Use the IP address** — if `.local` doesn't resolve, find the device's IP address on your router and go to `http://<ip-address>:18789` instead