minvs1

Asked @grok to build a nice dashboard for @trip1com metrics, with a globe showing live searches. Got this. #flatearthsociety @elonmusk we need to talk.

just started using @krowkcom by @predkelis in @trip1com . super productive way to see what the agent built without going through the UI, works like a charm. also can upload artifacts, more flexible version of claude artifacts. works super good with T3 Code by @theo

Just deployed a whole team of AI agents to Buzz by @blocks - each a field expert with one dedicated job: researching, planning, architecting, and back-pressuring each other to produce a feature plan end to end. Human in the loop to verify and approve before anything gets built. The lineup: an orchestrator, 4 parallel researchers (customer, competitor, distribution, tech), an information architect, a skeptic paid to kill ideas, and a builder - all running Claude Code by @AnthropicAI under the hood. It's crazy that this kind of orchestration is a few clicks away now. Great work @jack & the Buzz team 🐝 (h/t @gregisenberg for the diamond pattern that inspired the graph) Cool features coming to @trip1com very soon, stay tuned!

Reserved bookings.cloudflare.pay for @trip1com. We've had MCP payments via USDC on @base over x402 and @coingate for quite some time now and we see numbers increasing every month. We believe initiatives like @Cloudflare Wallets will push agentic payments to the mainstream, and we're gonna ride this train front row!

Massive! Gonna migrate trip1 off Slack to BUZZ the moment they ship custom emojis 🤠

We migrated @trip1com frontend from Next.js to @tan_stack in one day, and got huge performance benefits. We'd been fighting memory leaks in our Next.js setup for quite some time and nothing really solved it completely - until we just tried to AI-it over to TanStack. To our surprise it took Fable (@ClaudeDevs) one hour to make CI happy, and one full day for polish. Now memory is flat, builds are ~9x faster, dev refreshes are unnoticeable, 25% smaller shipped JS, and even navigation feels faster. I like how frameworks are becoming less of a way of life you marry at the start of a project, and more of a tool you can swap in a day.

The second loop takes an approved ticket, opens a PR on @github, and runs it past an AI reviewer until nothing's blocking and CI's green. Then one of us reads it and merges. That's the second click. Runs on our @claudeai sub, never touches auth or payments.

One loop watches our @linear backlog and flags the tickets an agent can handle on its own. We approve the ones we want with a single label. That's the first click.