Reading up on Loops

We’ve been improving Loops a lot to automate work that should be automated In @slack or @linear just tell the agent you want to make a loop for something. The loop can auto pick models, connect to external services through MCP, can be triggered or scheduled. Some example loops from our team: * Investigate incoming bugs and propose fixes with browser tests * Find new Sentry errors and open fix PRs * Turn meeting action items into issues * Monitor engineering alerts and unusual cost spikes * Surface untracked container vulnerabilities * Scan and remove old feature flags * Watch feedback on workflows or product areas and keep an running document, slack or other sources

@karrisaarinen

Congrats to the Orchid team! This is the second acquisition of a Loops customer by Figma.

@frantzfries

We just released a new marketing site and I wanted to talk through some of the changes that we made and why. Design thinking is the other side of the feed, it's usually more nuanced than the flashier parts and typically doesn't hold up as well to a quick scroll. Doesn't bode well for this thread! But, this will be my attempt to talk through the changes made and why. First up, this is our new hero. At @loops, our goal right now is to be the only platform you need to email your users The H1 matches that intention and the subheader reinforces it. We also wanted it to be clear we ship fast and often, so we added a pill showing the latest featured changelog. Agents are part of how people build software today, so we wanted to give that the second most important placement on the page, right after signup. Finally, the logo strip should not distract too much, but it should still help people understand these are users, not just logos. So we added the date of first payment from Stripe next to each logo. Next up, more things!

@frantzfries