What We Shipped This Week: September 3 – 10, 2026

A week about Sabi doing what you asked, quietly and on time: 32 updates shipped and 148 customer-reported issues resolved. Here's everything, in plain English.

---

📊 The Week in Numbers

• 32 updates shipped to production
• 148 support tickets resolved
• One Sunday fix-a-thon closed 35 tickets across three problems — time zones, task edits, and "bug report submitted" errors
• The "Saved status only; nothing was verified" line that opened 396 replies to 103 customers last week is gone for good

---

🤫 "Only Tell Me If Something Happens" Now Means Exactly That

• Silent watches — if you ask Sabi to "let me know when a lead comes in" or "tell me if anything urgent lands in Discord," she now sets up a recurring check and only texts you when there's actually something to say. No more "Nothing new, staying silent as planned" messages every 15 minutes. Twelve customers had tasks stuck in that loop; all fixed.
• You can see and change it on the Tasks board — every task card now shows whether it messages you every time, only when it finds something, or never. There's a "Message me" control in the task editor, or just tell Sabi "stop texting me when there's nothing."
• Silent doesn't mean lazy — quiet runs still do the work and keep a receipt of what they checked, so "did it actually look?" always has an answer. And a real finding can never be suppressed.

🧠 Sabi Acts Instead of Narrating

• The "Saved status only" disclaimer is gone — one in five people who texted Sabi last week got a reply that opened with "Saved status only; nothing was verified this turn," usually on a message that had nothing to do with app status. That line, and "that run got cut off, tell me to continue," came from a safety layer we've now removed at the root. Ask "is my Gmail connected?" and Sabi goes and looks, then answers from what she found.
• Reconnect links come with the answer — if an app isn't connected or has stopped cooperating, Sabi sends the link to fix it in the same message instead of offering to check.
• Scheduled tasks no longer text "Can you try rephrasing?" — to customers who never said anything. A task with nothing to say now says nothing.
• Sabi finishes what she started — if she gets cut off mid-work, she picks the thread back up herself before telling you anything.

🕐 Time Zones: Confirmed by You, Not Guessed

• No more Eastern-time assumption — many accounts were quietly set to Eastern and there was no way to fix it by telling Sabi. Now, the first time you schedule something, Sabi asks one quick question ("you're on Eastern time, right?"), saves your answer, and never asks again. "I'm on Central time now" updates your account and every live task, keeping the same wall-clock time. Cleared 5 tickets from 4 customers.
• Task edits actually land — "pause it," "move it to 6am," and brief changes were being confirmed by Sabi but never applied. Pausing, resuming, rescheduling, and editing a task now go through, and Sabi tells you the real next run time. Seven customers reported this; all fixed.

💬 Web Chat That Doesn't Lose Your Replies

• Replies stay on screen — Sabi's previous answers used to vanish from the web chat the moment you sent your next message. They now stay put. This one fixed a group of 9 tickets from 7 customers.
• Long jobs no longer look broken — when Sabi is deep in a 5–15 minute task, the chat used to flash a red error at the two-minute mark even though she was still working. Now it shows a calm "your reply will appear here when it's ready" and the answer lands when it lands, even if you switched tabs.
• Busy-moment errors handled gracefully — during brief capacity blips you'd see "bug report submitted." Sabi now retries quietly, and if things really are down you get an honest one-liner instead. Cleared 16 tickets from 12 customers.

🔌 New Apps You Can Connect

• Fathom — connect your AI meeting-notes account and ask Sabi about meetings, transcripts, and summaries. Requested by a customer on the feedback board.
• Wave — Sabi can now answer invoice, customer, and product questions from Wave, the same way she does for Xero.
• RainFlow and FG Funnels — both are built on HighLevel, and Sabi now knows it. Click either tile on Connections and you'll sign in through HighLevel (that's expected). Customers were being told these weren't supported; 12 tickets closed.
• Clearer permission messages — when HighLevel blocks something Sabi doesn't have access to, she now tells you plainly what's going on instead of sending you to regenerate an API key on a settings page that doesn't exist.

✉️ Email & Calendar

• "Never send — draft only" is honored everywhere — including scheduled tasks. If your standing rule says Sabi shouldn't send email on your behalf, you get drafts, full stop. A task's own instructions can never count as your approval.
• iCloud calendar moves actually move — asking Sabi to move events from one iCloud calendar to another used to report success while leaving everything where it was. Bulk moves now work.
• Custom-domain mailboxes — support for connecting any custom or self-hosted mailbox (not just Gmail, iCloud, and Yahoo) is built and rolling out; the Connections card will appear once we flip it on.

🧠 Smarter Memory

• Standing facts stay put — permanent details like your name, pronouns, and preferences were being crowded out of Sabi's memory on roughly half of all conversations, which is why she sometimes seemed to "reset." Those facts now have a protected spot and can't be pushed out.

👥 Community & Blog

• Photos in Community posts — the composer now has a Photo button. Attach an image (with or without text), preview it, and post.
• Weekly updates on the blog — these "What We Shipped" posts now live at meetsabi.com/posts, so you can catch up any time.

🛡️ Reliability Behind the Scenes

• Morning check-ins arrive on time — for three weeks, the 9 AM wave was landing 25–90 minutes late for many customers. The scheduler now clears the queue continuously, and timed tasks always go ahead of overnight research work.
• Servers heal themselves — a frozen background worker used to sit dead for hours until someone noticed. It now detects the problem and restarts within about five minutes, and we fixed the memory leak that was causing the freezes in the first place.
• Fewer mid-conversation stumbles — oversized app responses and mistyped tool requests used to derail a reply; both now recover on their own.

---

Questions or something not working the way you'd expect? Just tell Sabi — every piece of feedback lands on our board and gets looked at quickly.