Why does an agent need its own email inbox? The question which determines whether AgentMail lives or dies.

OK, I shipped it — v0.8.0 of Observational Memory now includes OM Mail, an experimental feature that gives agents their own @agentmail inboxes so they can mail each other memory: signed notes, encrypted context packs, recall requests. My favorite part is recall negotiation. Your agent emails mine a question; mine answers from its own local memory, signed and scope-filtered. Neither agent ever holds the other's memory, and they still help each other out. AgentMail made this almost too easy to build — an API that mints working inboxes for agents on demand was exactly the missing piece. Thanks @ryancarson and @adisingh for the push. Write-up 66s demo: x.com/intertwineai/status/20…

Introducing the new AgentMail team! All smiles at the @agentmail estate… #teamphoto #fablecrushwednesday

What would you like to see AgentMail build next??? Doing some roadmapping 👀

An agent that can't email is just talking to itself. Swipe below to learn more

Is anyone using @agentmail as portable durable context for agents? Seems like an interesting use case

As you know when it comes to testing your app, you need email addresses for all of the test users and you need your agent to be able to control those email addresses, read them, set them up, destroy them, and control them programmatically. You also want to be able to dip into those inboxes as a human and see what's going on and agentmail removes all of the friction there. I use Devin to do extensive end-to-end testing of all our features and it works really well for this. I decided to go for the $200/month plan because I wanted basically unlimited email inboxes and then every once in a while I'll have the agent clean them up and delete a bunch

Love this team! They never stop shipping! 🚀🔥

Your agent runs the email. When it needs you, it asks in the thread, then keeps going.

Today, we're officially introducing the new Vybe. We started as "Lovable for internal apps." We spent the last year building the infrastructure: permissions, integrations, databases, workflows. Everything companies need to actually trust software inside their business. Then, OpenClaw came out and started showing what was possible with agents for personal use cases. Everything clicked for us. The infrastructure we'd built wasn't just useful for humans anymore: it was exactly what agents needed to operate inside real companies and teams. What happens when agents can work 24/7, with the right context, the right permissions, and access to your company's tools? A founder becomes a one-person army. A small team operates like a much bigger one. That's the mission we fell in love with at @vybe_build. Our agents have names and roles. They have their own email, Slack, phone number. They prep meetings, follow up with leads, run ops, update CRMs, build internal tools. Vybe runs on Vybe. We're onboarding 10 teams a week to run AI-native companies.

too good to be true...