Show recap — 2026-08-19 — Another Orange Morning

From the show

Another Orange Morning Recap: August 19, 2026

Wednesday morning arrived without a Friend in the room. Zach was out, which left Casey and Chris to work the day's list as a pair, and Casey called the shape of it before the first update was open: this was a big Breeze Assistant day. Seven updates made the cut, and almost every one of them either was Breeze or was about the plumbing Breeze runs on.

Here is what we got into: an on-demand AI summary landing in the notification sidebar, eight Breeze Assistant connectors getting a retirement date, app marketplace submissions moving from total installs to active installs, the Social Content Agent still looking for testers, Buying Groups picking up drag and drop, Breeze Enhanced Search coming to Android, recommended video clips showing up in the social tool, and a Will It Breeze that did not breeze.

Seven Updates, and Breeze Runs Through Most of Them

An On-Demand AI Summary in the Notification Sidebar

HubSpot users can now generate an AI summary of their last twenty four hours of notifications from the notification sidebar, and receive it both in the sidebar and by email. It is public beta, free across all hubs and tiers, and English portals only for the moment.

The reaction in the room was that this one arrived quietly and is worth more than it looks. The notification sidebar has been a ninety nine plus badge that nobody opens, useful mainly for grabbing a file you missed the download prompt on. A digest changes what that surface is for. The version that really matters is the email, because that is where most people would rather receive this in the first place.

There is a second effect worth sitting with. Pressing the summary button is a signal about what you care about, so the more you use it the more it should learn what to put in front of you. That makes early use of this beta worth something beyond the summary itself.

Why it matters: Notification volume is a real tax on people who live in HubSpot all day, and the usual answer has been to turn everything off and miss things. A consolidated read, delivered where you already work, is a better answer than either extreme. For more details: the on-demand AI summary in the notification sidebar.

Eight Breeze Assistant Connectors Are Being Removed

Smartsheet, GitBook, Azure DevOps, Guru, ReadMe, Productboard, Helpjuice and Document360 are leaving the marketplace. New installs are already unavailable, and existing connections stop working on September 26. HubSpot's reason is that these were built on an older architecture it is no longer maintaining, and that removing them lets investment go to connectors that perform better inside Breeze Assistant.

The published update prints the year as 2025, which produced a nice moment of everyone briefly wondering what year it is. Take the date as September 26, 2026.

The read on air was that this connects directly to the new Breeze Assistant connectors covered about a week earlier. If that new infrastructure is replacing what these were built on, then a sunset notice for eight of them is a migration story rather than a retreat.

Why it matters: If you are running one of these eight, you have a real deadline and about five weeks. Nobody on the show had encountered most of them outside Smartsheet, so the practical blast radius is probably small, but small is not zero and the connection disappears on its own if you do nothing. For more details: the Breeze Assistant connector removals.

Marketplace Submission Eligibility Moves to Active Installs

Marketplace listing and certification submissions are now gated on active installs rather than total installs. Listing needs three active installs. Certification and recertification need sixty active installs and six months listed. Your active install count is now visible in the developer account so you can watch it move.

Active installs means unique, unaffiliated production accounts that have shown real app activity in the past thirty days, counting OAuth authenticated API requests and signed webhook or extension requests. Total installs counted any account where the app was sitting installed, active or not. The requirements themselves did not change. What changed is when you find out, so a developer gets blocked before submitting instead of denied afterward.

The conversation moved to the part that is harder to fix. Getting the first three installs means going and talking to people, usually starting with a network that already asked for the thing. But the warning a buyer sees before installing an uncertified app reads like the riskiest possible action to take on their portal, and that lives outside any developer's control. Education is the only lever there, and it would be good to see more help with it.

Why it matters: This is a clarity change more than a policy change, and clarity is the right thing to fix. Anyone building toward a listing should go look at the new count today and plan against the number that actually gates them. For more details: the marketplace submission eligibility changes.

The Social Content Agent Is Still Seeking Testers

The Social Content Agent is the next generation of the social post agent introduced at UNBOUND back when it was still called INBOUND. The original wrote from holidays and calendar events, which is how B2B marketers ended up with posts about days they would never have chosen. This one takes a topic from you, or offers ideas, then researches your industry, reviews how your past posts performed, and checks what your contacts are actually asking about in the CRM before it writes anything. It works in your brand voice, saves drafts into the social app, and supports LinkedIn today with more networks coming.

The entry point proved harder to find than the update suggested. The new path is meant to sit inside the existing social app and calendar, through the create post dropdown or the plus button on the calendar, and there are warnings on the older create with AI page that it is going away. Rather than click around live, the update itself went into Breeze to see what it would say, and Breeze confirmed the portal qualifies and is already enrolled.

Why it matters: The research happening before the writing is the part that makes this different from every generic drafting tool. Posts grounded in your own past performance and your own customer conversations sound like you because they come from you. It is a private beta and HubSpot is asking for beta tolerant testers, so go in expecting to give feedback. For more details: the Social Content Agent tester call.

Buying Groups Picks Up Drag and Drop

Buying Groups and account mapping both got a visual pass, and the new piece is drag and drop for adjusting a group. Buying Groups gives sales teams a picture of the stakeholders they are selling to. Account mapping gives a picture of how the company itself is structured, parent and child, so expansion opportunities are visible at a glance.

The segment came with a disclaimer that belongs to the show rather than to HubSpot. None of this does anything unless the data is already in the CRM, structured properly, and associated properly. You may not need every specialized label, but the records have to relate to each other before a visual tool can draw the picture. That is the work, and the drag and drop is the reward for having done it.

The wider point is that one contact per deal stopped describing reality a long time ago. If you are selling into anything large, there is a buying committee whether or not your CRM knows about it.

Why it matters: This has been circulating for a while and recently moved into a private beta aimed at sales and service. The visual layer keeps getting better, which raises the value of having your associations in order and raises the cost of not. For more details: Buying Groups and account mapping.

Breeze Enhanced Search Comes to Android

Breeze Enhanced Search brings Breeze and global search together into one mobile entry point. Instead of deciding up front whether you are searching CRM records or asking Breeze a question, you start in one place and choose to search or to ask. It is scheduled for August 27 on Android, arriving through the new Breeze Bar for anyone with Breeze Assistant enabled, with standard global search continuing for everyone else.

The obvious question came up immediately: why should a user have to decide at all? Bringing the two together is the engineering description of what happened. The version you would actually tell a customer is shorter. Click Breeze, type anything, stop worrying about whether you spelled the name right.

Why it matters: Searching for a record is one of the most common things anyone does on mobile, usually between meetings and usually in a hurry, with a partial name or a vague memory. Global search has gotten much better at catching those over the past year. Letting the same box answer a question instead of just finding a record is the natural next step. For more details: Breeze Enhanced Search on Android.

Will It Breeze: Who Should I Call Today?

Chris put a real question to Breeze Studio: using the service queue, tell me who to call today. It is exactly the kind of ask the tool should be built for, and it did not land. Breeze first reported that it could not reach the open ticket view, which was hard to accept given there are certainly open tickets to reach. After some negotiating it offered a link to the ticket index instead of an answer, and a second attempt from a fresh conversation failed on a direct CRM pull with the access path failing at skill load.

The verdict was called plainly on air. It did not breeze today. The screenshot is going to the product team, because Breeze has handled far more tickets than this in the past, and a skill that fails to load is a different problem from a tool that cannot do the thing.

One craft lesson came out of it that applies well beyond this segment. The first prompt was framed from the product updates page while asking about tickets, and that framing could not be recovered from inside the same conversation. Asking Breeze for a better prompt and starting fresh was the only way out. If your assistant is stuck in a bad frame, a new session beats another attempt.

The failure produced the better conversation anyway. Casey took the underlying question somewhere more useful: how do you decide who actually needs you today? She has a client in a quiet stretch where the next step is waiting on them, and other clients actively moving. The instinct is to chase the quiet one because it nags at you. A colleague had pointed out that there is real benefit in letting things ebb and flow, and that a project in a natural lull may not be the one to prioritize over projects that are moving. The same logic maps onto a ticket queue. A ticket someone emails about every day and a ticket that has gone quiet because the customer forgot are two different situations, and the second one might resolve with one nudge.

Nobody claimed to know the right equation. What became clear is what an answer would require, which is the full context of each relationship reconsidered whenever anything changes: how long it has been, whether they said they would be out, whether a holiday is in play, what the relationship is worth. That is more than a queue sorted by age can carry, and it is why account managers and delivery leads exist. It is also a fair description of what an AI teammate would need access to before its answer could be trusted.

The Rest of Wednesday's Updates

One more shipped Wednesday without making the show. Super admins and primary contacts can now view all of their subscription usage on the Other Limits page in Account and Billing, pulling entitlement usage into one place instead of scattering it across the product. Everything else that shipped is in the HubSpot updates feed.

The Sign-Off

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you tomorrow morning.

Produced by Value-First Media

Show recap — Wednesday, August 19, 2026