Abhishek | Klio + Vex

Cooking something new for @X and on X. We all can build apps but #distribution is the challenge. Let's #fix this one and for all.

Persistent memory isn't a nice-to-have anymore. It's the baseline. When your agent forgets context mid-task, you don't have an agent. You have an expensive autocomplete. Stop patching stateless loops. Build for memory from day one. #AIAgents

@getsendops @useSend_com Agreed there are surely some trade-offs but aren't those easy fix if we spend a day or two with a Claude Agent to guide through ?

Open-source stacks + SES reduce vendor lock-in and cost but be ready for trade-offs: more DIY maintenance, ops overhead, and slower support than a dedicated control plane like SendOps. Sometimes the middle ground—cost-effective, no-code layers—best balances control with operational sanity.

🚀 Want to build a #Resend-like product (dev-friendly transactional email API with templates, analytics, webhooks) but 5-10x cheaper? Skip Resend's markup + #Amazon SES costs. Use open-source @useSend_com + ZeptoMail. Full control, no vendor lock-in. Thread 👇

Most AI agents fail in production because nobody defined what "good enough" looks like before shipping. Here's how we think about it: 1. Define your failure modes first. Not edge cases. The actual ways your agent can silently go wrong. Hallucination, drift, low confidence outputs, blocked actions. 2. Set a threshold before you deploy. What confidence score triggers a human review? What output pattern gets flagged automatically? Write it down before your first real user hits it. 3. Log everything from day one. Not just errors. Every input, every decision, every output. You can't debug drift you didn't capture. 4. Build a feedback loop into the product itself. Not a quarterly eval. Something that surfaces degradation in real time so you can act before users notice. 5. Treat your verification layer like infrastructure. Not an afterthought. It belongs in your architecture the same way logging and auth do. Most teams skip all of this until something breaks. Then they're debugging blind with production data and frustrated users. Define what failure looks like before it finds you.

The most dangerous assumption is thinking you need a finished product to start building in public. Ship the idea. Get the feedback. Then build what people actually want. Building in the open from day one. #BuildInPublic

@TTrimoreau Distribution is the only thing that will solve the problem after a product is developed. Building is no longer a problem to be solved. It is being creative identifying an idea and then just pure distribution.

What’s the biggest risk for a startup today? -building too long -launching too late -no distribution -copying competitors

@elonmusk This is interesting and really great for educational purposes too. It helps us to understand what does it take to go viral on @X .

The latest 𝕏 algorithm has been published to GitHub github.com/xai-org/x-algo…

Ready to ship your own email infra? Star the @useSend_com repo, try ZeptoMail's free credits, and fork it today. Questions? Drop them below - happy to share code snippets or Docker compose. What would YOU build with this? 👇 #BuildInPublic #DevTools #EmailAPI #OpenSource

Why this beats Resend/SES: - 80-90% cheaper at scale - Full ownership (self-hosted) - Same dev DX - Better for transactional-only (ZeptoMail's specialty) - No surprises on bill Already seeing people self-host UseSend on SES → this is the smarter evolution.

Bonus tips for pro setup: - Use ZeptoMail "Agents" to segment different apps/clients. - Add custom features like delayed sending or basic "unsend" queue if you want (easy in your fork). - Monitor with Unsend's dashboard + ZeptoMail logs. - Scale with multiple regions if needed (ZeptoMail handles high volume reliably). Total cost? Just ZeptoMail credits + your cheap VPS (~$5-10/mo hosting).

Step-by-step how to do it: 1 - Sign up for ZeptoMail → verify your domain + generate API token (super quick). 2 - Deploy Unsend (one-click on Coolify/Easypanel or Docker). 3 - Fork the Unsend repo (it's open source!). 4 - Replace the SES SDK calls with ZeptoMail's REST API (or SMTP if you prefer). Code is straightforward — their docs have Node.js/Python/etc. examples. 5 - Add your ZeptoMail token as env var. 6 - (Optional) Keep Unsend's React Email editor + webhooks/analytics — they work independently of the backend.