Introducing https://t.co/fL3P4Hmfxg: web hosting for AI agents.
Your agent builds apps. But where do they go?
https://t.co/fL3P4Hmfxg gives every project a live URL, a container, a database, and an OpenClaw that monitors it 24/7.
Tell your agent "deploy to https://t.co/fL3P4Hmfxg" -- live in seconds.
Free, no sign-up required.
Introducing Minds by @animocabrands, the AI agent for you and the people around you to share.
It remembers, it connects, it simplifies. So you don't have to do it all alone.
An AI with your best interest at heart.
Built VibeKit β an iOS app + Telegram bot that ships full-stack apps from your phone.
How I built it: I was running an OpenClaw agent on an EC2 box that also hosted one of my projects. Drove the agent from Discord on my phone β chat in, code committed, deployed in place. Realized that workflow should be a product.
Architecture: Node + Express gateway on a single EC2, per-user AWS Fargate containers (one per app) each holding the user's repo + an OpenClaw agent, nginx routes <subdomain>.vibekit.bot to the right Fargate task, Supabase for users/apps/agent_messages/billing, Stripe for payments.
BYOK Anthropic/OpenAI routes direct (no markup), otherwise OpenRouter (Qwen free, others +20%). iOS is pure SwiftUI native. Telegram bot uses the same backend and talks to the same agents.
Build insight I didn't expect: keeping the agent in the SAME container as the user's repo is the unlock. Cursor/Lovable bolt an AI onto your editor; this bolts an AI directly onto your deployed app. The agent can git status, run your tests, hot-restart your server, all in one place. iOS becomes the chat surface, container does the work.
Hardest parts: Stripe webhook silent failures (metadata field-name drift), Fargate task rehydration across deploys, container disk quotas.
https://t.co/fL3P4Hmfxg for the demo. Feedback welcome on the wedge, the pricing, the arch.
25+ free models now on VibeKit! Today's @OpenRouter integration unlocks the entire free pool.
More of VibeKit is free to use than ever β build, ship, iterate without a credit card.
VibeKit 1.4.1 is live.
We spent this release reducing friction and improving latency.
Long-session chats are faster, the Remote tab is cleaner, and the whole app feels snappier.
Also shipped custom app icons.
@VibeKitBot iOS v1.4.0 is out!
β Multi-agent Remote tab: each machine its own tile + chat
β Rename machines in remote mode (push notifs use the new name too)
β Model picker is HERE.
β Health drawer with past-hour CPU & Memory charts
v1.3.7 LIVE in the App Store!
β’ New Repos tab β deploy any GitHub repo with one tap
β’ Per-app traffic counters (1d / 7d) on every tile
β’ Refined drawer styling across the app
β’ Remote chat now recovers automatically after your computer sleeps
This is my 3rd week as VP of Engineering DeFi at @Polymarket , and I'm going to be straight: the traction @Polymarket has seen has massively outpaced our infrastructure, and we haven't done nearly enough to scale to keep up. I hear you, and fixing this is our entire focus. We're a major company now, and we need to engineer like one. Here's exactly what we're doing:
- Onchain data latency. We're working on making this near-instant so the experience is incredible.
- Chain migration. We need more block space, cheaper gas and much smaller block times so settlement is instant.
- Transactions are getting cancelled. We understand this is one of the most frustrating issues right now, and we have a complete fix coming very soon.
- Massive focus on the website to make it faster, more responsive, and with better UX.
- We added observability everywhere. Proper alerting so we catch issues ourselves, market makers should not be the ones telling us something is down. That's been unacceptable, and we know it.
- E2e tests throughout, starting with the CLOB, so issues get caught in CI before anything ships.
- CLOBv2 is not a rewrite. It won't improve performance or stability on its own; it's an upgrade that unlocks us to move fast right after. We'll do better with communication next time.
- We are rebuilding the CLOB from the ground up. Most important thing we're doing. Without it, we can't be the best DeFi exchange in the world. We know it, we're on it, it's mission critical.
- Unified TypeScript SDK for all APIs, which is shipping soon.
- Unified API. One WS connection for everything, with a schema that's actually readable.
- New Polymarket contract in the works that unlocks things that are simply impossible on the current protocol.
- New hires: Head of QA Automation, Head of Dev Tooling, Head of Internal Tooling, Head of Data Engineering.
- Smaller, dedicated teams. Fewer focus points per person, clearer ownership. People do what they're good at and are accountable for it.
- Working closely with customer support to give them real debugging tools so any user issue gets properly diagnosed, not lost.
- Proper communication with marketing and market makers so everyone knows what's coming and when, and MM can submit feature requests with a clear path to get them into engineering and shipped.
- Working with 4 security teams daily to ensure we're super secure and that funds are always safe.
- Perps incoming. Brand new contracts and a backend built from scratch in Rust. We're proud of this one.
- A lot of other fixes are running in parallel right now.
Starting next Friday, I will be posting weekly engineering updates.
I joined because I genuinely believe in what @Polymarket is trying to do. @shayne_coplan built this so the world has somewhere to go to find out what's actually going to happen, not what the media thinks, not what a pundit says, but what thousands of people are willing to put money on. But right now, our engineering isn't living up to that. We've let people down, and I'm not going to dress that up. I came here to fix it, and that's exactly what we're going to do. The next few months are going to speak for themselves. Stay with us.