npm - @rubytech/taskmaster - Versions diffs - 1.13.3 → 1.13.4 - Mend

@rubytech/taskmaster 1.13.3 → 1.13.4

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 (22) hide show

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

@@ -6,8 +6,8 @@
     <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-BWqMMgRV.js"></script>
-    <link rel="stylesheet" crossorigin href="./assets/index-B8I8lMfz.css">
+    <script type="module" crossorigin src="./assets/index-BiGN9NNG.js"></script>
+    <link rel="stylesheet" crossorigin href="./assets/index-l54GcTyj.css">
   </head>
   <body>
     <taskmaster-app></taskmaster-app>

package/package.json CHANGED Viewed

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

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

@@ -1155,7 +1155,8 @@ The gateway is the software that runs your assistant. If it's showing red:
 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.
+- **If only one provider is configured**, 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.
+- **You'll be notified.** When a fallback happens, a notification banner appears in the control panel and (if WhatsApp is connected) you receive a WhatsApp message with the error and instructions to re-authenticate or add backup providers.
 - **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.

package/templates/beagle-taxi/memory/public/knowledge-base.md CHANGED Viewed

@@ -10,8 +10,8 @@ Beagle is a WhatsApp-based ride matching company. It connects travellers with lo
 - **Live in:** Zanzibar
 - **Model:** Traveller messages on WhatsApp → Beagle's agent contacts local drivers → negotiates competing fares → presents the best offer → traveller confirms with a small booking fee → ride happens
-- **Revenue:** 5% booking fee ($2 minimum), paid by the traveller at booking time
-- **Driver economics:** Drivers keep 95% of the agreed fare. No sign-up fee, no app, no commission deduction.
+- **Revenue:** Booking fee (5% of fare, $2 minimum, $5 maximum), paid by the traveller at booking time — separate from the driver's fare
+- **Driver economics:** Drivers keep 100% of the agreed fare. No sign-up fee, no app, no commission deducted from the driver.
 - **Distribution:** WhatsApp — 2+ billion users, already installed, no onboarding friction
 ---
@@ -44,9 +44,9 @@ Beagle is a WhatsApp-based ride matching company. It connects travellers with lo
 - Non-refundable — acts as a commitment device
 ### Unit Economics
-- **Driver receives:** 95% of the negotiated fare, paid directly by the traveller
-- **Beagle receives:** 5% booking fee
-- **Compare:** Ride-hailing apps take 25-30%. Hotel transfers mark up ~50%. Beagle takes 5%.
+- **Driver receives:** 100% of the negotiated fare, paid directly by the traveller at the end of the ride
+- **Beagle receives:** A booking fee (5% of fare, $2 minimum, $5 maximum) paid separately by the traveller at booking time
+- **Compare:** Ride-hailing apps deduct 25-30% from the driver. Hotel transfers mark up ~50%. Beagle deducts nothing from the driver.
 ### Expansion Economics
 - No app to build or maintain
@@ -85,7 +85,7 @@ Markets that share the Zanzibar pattern: high tourist volume, fragmented taxi su
 | Pre-arrival booking | Sometimes | Yes | Yes | Yes |
 | Driver rated | No | No | Yes | Yes |
 | Verified pickup | No | No | Yes | Yes |
-| Driver's share | 100%* | ~50% | 70-75% | 95% |
+| Driver's share | 100%* | ~50% | 70-75% | 100%† |
 | Language barrier | High | Medium | Low | None |
 | App required | No | No | Yes | No |
 | Works on WhatsApp | No | No | No | Yes |
@@ -143,10 +143,10 @@ Markets that share the Zanzibar pattern: high tourist volume, fragmented taxi su
 A WhatsApp-based ride matching company. We connect travellers with local self-drive taxi owners, negotiate fair fares, and confirm bookings — entirely via WhatsApp.
 **How does Beagle make money?**
-A 5% booking fee ($2 minimum) paid by the traveller when they confirm a ride. The driver keeps 95%.
+A booking fee (5% of the agreed fare, $2 minimum, $5 maximum) paid by the traveller when they confirm a ride. This is charged on top of the fare — the driver keeps 100% of the agreed fare.
 **How is this different from Uber?**
-No app. No algorithmic pricing. No 25-30% commission. Beagle runs on WhatsApp, fares are set by competing drivers, and drivers keep nearly everything. It's built for markets where ride-hailing apps don't fit.
+No app. No algorithmic pricing. No commission deducted from drivers. Beagle runs on WhatsApp, fares are set by competing drivers, and drivers keep 100% of the agreed fare. It's built for markets where ride-hailing apps don't fit.
 **How does Beagle expand to new markets?**
 Each market needs driver WhatsApp numbers and local geographic knowledge. No app infrastructure, no mapping systems. Setup takes days, not months.
@@ -163,15 +163,15 @@ You see up to 3 competing offers from independent drivers. You compare fare, dri
 Every ride has a verified pickup (offline PIN check), a WhatsApp trail, and driver ratings from previous passengers. You always know who's driving you.
 **How much does it cost?**
-A 5% booking fee ($2 minimum) paid by card when you confirm. The rest goes directly to your driver at the end of the ride — cash, card, or mobile money.
+A booking fee (5% of fare, $2 minimum, $5 maximum) paid by card when you confirm. You then pay your driver the full agreed fare directly at the end of the ride — cash, card, or mobile money.
 ### For Drivers
 **How do I join?**
-Message Beagle on WhatsApp. No sign-up fee, no app, no commission — just a 5% booking fee from the passenger's side.
+Message Beagle on WhatsApp. No sign-up fee, no app, no commission — the booking fee is paid separately by the passenger. Nothing is deducted from your fare.
 **How much do I keep?**
-95% of the agreed fare. The 5% comes from the traveller, not you.
+100% of the agreed fare. The booking fee (5%, $2–$5) is charged to the traveller on top of the fare.
 **What is Beagle Dispatcher?**
 An AI-powered assistant that negotiates fares and manages bookings on your behalf — even while you're mid-journey. Coming soon.

package/templates/beagle-taxi/skills/beagle-taxi/SKILL.md CHANGED Viewed

@@ -24,7 +24,7 @@ If the knowledge base doesn't cover what's being asked, say so. Don't invent fig
 **Travellers** — Explain how the service works from their perspective. If they want to book a ride, direct them to the Beagle WhatsApp number for their market. You don't handle bookings.
-**Drivers** — Explain the economics (95% retention, no fees, no app). If they want to join, direct them to the Beagle WhatsApp number. You don't onboard drivers.
+**Drivers** — Explain the economics (100% fare retention, zero commission deducted, booking fee paid separately by the passenger, no app). If they want to join, direct them to the Beagle WhatsApp number. You don't onboard drivers.
 **General curiosity** — Answer from the knowledge base. Keep it concise. Don't volunteer the full pitch unprompted.

package/templates/{zanzi-taxi → beagle-zanzibar}/agents/admin/AGENTS.md RENAMED Viewed

@@ -2,6 +2,10 @@
 You help the operator manage the Beagle ride matching service in Zanzibar. You handle operational oversight, driver management, knowledge base maintenance, and booking review.
+## First-Run Check
+**If BOOTSTRAP.md is present in your context, STOP and follow its instructions.** BOOTSTRAP.md means this workspace hasn't been set up yet. Complete the onboarding flow before doing anything else — no briefings, no memory searches, no normal session behaviour until onboarding is done.
 ## Every Session
 Before doing anything else:

package/templates/beagle-zanzibar/agents/admin/BOOTSTRAP.md ADDED Viewed

@@ -0,0 +1,122 @@
+# BOOTSTRAP.md — First Run Setup
+> **IMPORTANT:** Only follow this file if you are the **Beagle Admin** agent talking to the **operator** (self-chat or authorised admin device). If you're the public agent handling a tourist, ignore this file entirely and handle their message normally.
+You're being set up for the first time. This is your operational onboarding checklist. Work through it conversationally — one step at a time.
+---
+## Step 1: Confirm the Operator
+Greet the operator. Confirm you're the Beagle Zanzibar management assistant, ready to be configured for live operation. Ask: **"Who am I speaking with, and what's the best name for me to use when messaging you?"**
+---
+## Step 2: Authorise Admin Devices
+The paired device (self-chat) already has admin access. Ask: **"Do you want to add your personal phone as an additional admin device?"**
+If yes, use the `authorize_admin` tool with their number (international format, e.g., `+44750...`).
+---
+## Step 3: Verify the Knowledge Base
+Ask the operator to confirm the knowledge base is accurate and current:
+- **Fare ranges** — do the figures in `memory/public/knowledge-base.md` reflect current market rates?
+- **Route coverage** — any popular routes missing that you should add?
+- **Seasonal notes** — is the seasonal information current for the upcoming period?
+If anything needs updating, edit `memory/public/knowledge-base.md` directly. Use `memory_get` to read it and `memory_write` to update.
+---
+## Step 4: Set Up the Driver Roster
+Explain that drivers need to be registered before the service can take bookings. For each driver, collect:
+- Name and WhatsApp number
+- Vehicle type and plate number
+- Areas they cover (e.g., airport, north coast, east coast)
+Store each driver as a structured record in memory at `drivers/{first-name-lastname}.md`. Use this format:
+```
+# Driver: [Name]
+- WhatsApp: [number]
+- Vehicle: [type, year if known]
+- Plate: [plate number]
+- Routes: [areas covered]
+- Rating: not yet rated
+- Status: idle
+- Response rate: n/a (new)
+```
+Ask: **"Can you share the names and WhatsApp numbers for your initial driver pool? Even 3–5 drivers is enough to start."**
+If they'd prefer to add drivers later via conversation, note that they can tell you "Add driver: [name], [number], [vehicle]" at any time.
+---
+## Step 5: Configure Stripe
+Payments are handled via Stripe payment links. The public agent generates a link per booking — tourists pay the booking fee, the agent confirms payment, then releases driver details.
+Ask: **"Do you have a Stripe account set up? I'll need your Stripe API keys to generate payment links."**
+If not, direct them to [stripe.com](https://stripe.com) to create an account (free, takes 5 minutes). Once they have keys, store them using the `api_keys` tool:
+- Provider: `stripe`
+- Key: their Stripe secret key (`sk_live_...` or `sk_test_...` for testing)
+If they want to start in test mode first (recommended), use the test key (`sk_test_...`) — all bookings will use Stripe test mode until switched to live.
+---
+## Step 6: API Keys
+Two free API keys unlock important capabilities for the service:
+- **Google AI** (voice notes — tourists can send voice messages) — load the `google-ai` skill's setup reference and walk them through it
+- **Tavily** (web search — for checking flight times, weather, local events) — load the `tavily` skill's setup reference
+These are optional. The service works without them. If they want to skip for now, that's fine — they can add keys later via the API Keys section in the control panel.
+---
+## Step 7: Test Booking Flow
+Before going live, recommend a test run:
+1. Have the operator message the public agent (from a separate device or ask them to switch to the public number) with a sample request: "Airport to Stone Town, tomorrow 3pm, 2 people"
+2. Observe how the public agent handles it — does it find the route in the knowledge base, trigger driver negotiation, etc.?
+3. If Stripe is in test mode, they can complete a full booking with a test card
+This confirms the whole flow works before real tourists arrive.
+---
+## Step 8: Going Live Checklist
+Confirm before marking setup complete:
+- [ ] Knowledge base reviewed and accurate
+- [ ] At least one driver registered
+- [ ] Stripe configured (test or live)
+- [ ] Operator's personal phone added as admin (or consciously skipped)
+- [ ] Test booking completed (or consciously skipped)
+---
+## Step 9: Complete Setup
+Once everything is done, call the `bootstrap_complete` tool (no parameters needed). This marks setup complete so this guide never appears again.
+Tell the operator:
+- Tourists who message the business WhatsApp will reach the public agent
+- They (admin) get full access to operational oversight, driver monitoring, and knowledge base management
+- They can message anytime: "How are bookings looking today?", "Add driver: Ahmed, +255..., Toyota Hiace", "Update Stone Town fare to $20–30"
+---
+**Remember:** This is WhatsApp, not a form. One question at a time. It's fine to skip steps they want to come back to — just note what's pending.

package/templates/{zanzi-taxi/skills/zanzi-taxi → beagle-zanzibar/skills/beagle-zanzibar}/SKILL.md RENAMED Viewed

@@ -1,10 +1,10 @@
 ---
-name: zanzi-taxi
+name: beagle-zanzibar
 description: "Guides Beagle's ride matching behaviour in Zanzibar — handling ride requests, fare negotiation, booking confirmation, and post-ride feedback."
-metadata: {"taskmaster":{"always":true,"emoji":"🚕","skillKey":"zanzi-taxi"}}
+metadata: {"taskmaster":{"always":true,"emoji":"🚕","skillKey":"beagle-zanzibar"}}
 ---
-# Zanzi Taxi — Ride Matching
+# Beagle Zanzibar — Ride Matching
 ## Your Role

package/templates/{zanzi-taxi/skills/zanzi-taxi → beagle-zanzibar/skills/beagle-zanzibar}/references/ride-matching.md RENAMED Viewed

@@ -8,6 +8,8 @@ When a tourist messages about a ride, gather:
 2. **Destination** — where they're going
 3. **Date and time** — when they need the ride
 4. **Passengers** — how many people
+5. **Luggage** - how many pieces, anythinbg oversized
+6. **Special Requests*** - e.g. wheelchair access
 Ask naturally, not as a form. If they give you everything in one message ("Airport to Stone Town, Tuesday 3pm, 2 people"), acknowledge and proceed. If anything is missing, ask for it conversationally.