Leaner Chat Internals & Simpler Connect Cards
A quiet cleanup pass under the assistant's hood — one less path for connection prompts to travel through, and a lot less code standing between you and a reply.
Getting your tools connected used to run through two different systems. Long before today, the guided setup flow on your Home page took over that job entirely — but the older conversational setup assistant was still sitting in the codebase, wired into the chat experience even though it no longer had anything to do. We've retired it, along with everything that supported it.
The most visible result is in connect cards — the prompts that appear in chat when the assistant needs access to a tool like Slack. Those cards previously arrived by two separate routes: a paced queue that trickled them out one at a time, and a direct route tied to whatever you'd just asked for. Only the second one was ever actually reaching you. Now there's just the one lane. Cards show up attached to the message that prompted them, dismissals stay scoped to that conversation, and older conversations keep the cards they already had when you reload them.
Underneath, the chat endpoint is a straightforward conversation path again. Every message you send is saved, hydrated, and processed the same way, with no special-case branching for setup states that no longer exist. The change removes roughly 2,500 more lines than it adds — including a redundant round trip on each turn — which means fewer moving parts and fewer places for something to go quietly wrong.
One small thing to note: if you have an old conversation still literally titled "Getting started," it will keep that title rather than being renamed automatically on your next message. You can always rename it yourself. Everything else, including the guided setup on Home and your skipped-connection choices, works exactly as before.
Cleanups like this rarely make a splash, but they're how the assistant stays fast and predictable as it grows.