Ethan Beard

Built a thing. ClawNet is public/private messaging for agents. Agents message on an open network. X style public posting. Multi layer prompt injection protection. Zero token inbox checking. Send your agent and let me know your thoughts. clwnt.com The agents are talking

@gregisenberg And give it its own email address clwnt.com

THE ULTIMATE GUIDE TO OPENCLAW (1hr free masterclass) 1. fix memory so it compounds add MEMORY.md + daily logs. instruct it to promote important learnings into MEMORY.md because this is what makes it improve over time 2. set up personalization early identity.md, user.md, soul.md. write these properly or everything feels generic. this is what makes it sound like you and understand your world 3. structure your workspace properly most setups break because the foundation is messy. folders, files, and roles need to be clean or everything downstream degrades 4. create a troubleshooting baseline make a separate claude/chatgpt project just for openclaw. download the openclaw docs (context7) and load them in. when things break, it checks docs instead of guessing this alone fixes most issues!! 5. configure models and fallbacks set primary model to GPT 5.4 and add fallbacks across providers. this is what keeps tasks running instead of failing mid-way 6. turn repeat work into skills install summarize skill early. anything you do 2–3 times → turn into a skill. this is how it starts executing real workflows 7. connect tools with clear rules add browser + search (brave api). use managed browser for automation. use chrome relay only when login is neededthis avoids flaky behavior 8. use heartbeat to keep it alive add rules to check memory + cron healthif jobs are stale, force-run themthis prevents silent failures 9. use cron to schedule real work set daily and weekly tasksreports, follow-ups, content workflowsthis is where it starts acting without you 10. lock down security properly move secrets to a separate env file outside workspace. set strict permissions (folder 700, file 600). use allowlists for telegram access. don’t expose your gateway publicly 11. understand what openclaw actually is it’s a system that remembers, acts, and improves. basically, closer to an employee than a tool this ep of @startupideaspod is now out w/ @moritzkremb it's literally a full 1hr free course to take you from from “i installed openclaw”to “this thing is actually working for me” most people are one step away from openclaw working they installed it, they tried it and it didn’t click this ep will make it click all free, no advertisers, i just want to see you build your ideas with ideas with this ultimate guide to openclaw watch

Nice to hear from you Jesse hope you’re great. This infra is pretty cheap to run. You could imagine layering in premium service like storage, throughput, custom domains, agent discovery. I built it for me as my openclaw agents having a quick and easy email and calendar was easier then jumping through the Gmail hoops every time I spin on up (have 3 now had 7 at one point).

@ethanbeard Hey Ethan, very interesting. Seems like the world may need a lot of agent first services. I'm curious what the business model is. I couldn't find any information on that. (Also saying 'hey' from long ago Google days... 😃)

Introducing clwnt.com free email for OpenClaw Gmail is great if you get past Google Cloud credentials, IMAP setting and OAuth. clwnt.com gives your OpenClaw(s) email in less than 5 minutes. Free, no sign-up required

@PiAshe88 @aakashgupta you can get an email for you openclaw in just a few minutes at clwnt.com. getting gmail up and running (and keeping it going) just kills me.

@aakashgupta can so relate. I spent a day setting up Openclaw, getting to know my biz using a VPS. I added gmail/Google drive believing we could communicate content this way, as it was managing marketing content. by 4pm, Google disconnected us, shut us down, removing access to gmail

> oai and anthropic watching google remember it owns the browser, the email, the maps, and the search engine

@proctorzt @Mintcondish369 @openclaw @nvidia if you're looking for even easier/faster email we just put it together at clwnt.com. skip the oauth, imap, google hoops no human required. calendar too.

@Mintcondish369 @openclaw @nvidia Don’t put it on your computer 🤷🏻 Give it its own computer, own Gmail, its own “identity”

huge shoutout to @nvidia for lending engineers to help triage our security advisories 🛡️🦞 open source security hits different when GPU companies show up to help

@fjzeit @Fudmottin I've found safer to give it its own email rather than letting it into mine. gota quick one at clwnt.com

@Fudmottin install OpenClaw and watch all your email disappear. :)

I have over 11,000 unread emails across my mailboxes now. 😱🤢🤮

@Kellykellam @openclaw try clwnt.com if you want the easiest email for openclaw. saved me a ton of time and headaches.

I’ve never felt so stupid as I do setting up @openclaw . I’ve had eight 10hr troubleshooting session days where nothing gets fixed and then watch the 1k+ posts a day: “I set up openclaw yesterday,, I made $100k overnight.” I can’t even get mine to fix an email webhook.

@JohnParadise17 @FSpannrich27974 @remiranda_42 @ChShersh You can give it its own email address at clwnt.com. I prefer it to have it's own email rather than having access to mine.

@FSpannrich27974 @remiranda_42 @ChShersh I mean maybe. My OpenClaw has no email access, only can ssh in to its box via Tailscale, isolated network and no company sever access. Has no access to my home server, and the slack channel is my domain only, invite only, and I’ve only invited people with 2 factor auth on.

Unironically, I don't know anyone who achieved anything meaningful with OpenClaw

@PereraBinoy @allenjosephaj We've got api/agent first free email for OpenClaw at clwnt.com. No human verifcation required. Native plugin, up in running in minutes (seconds). Built for OpenClaw rather than enterprises.

Openclaw equipped with an email inbox is such a clutch combo! Thank you so much for the write @allenjosephaj! Im sure a lot of people would find this super useful

@collinsfilms OpenClaw is super fun to build for. Been following my nose down a similar path mainly in the messaging space. Currently have free api/agent first email+calendar for agents at clwnt.com. Now iterating on email triage and whats the right human engagemtn pattern.

Been deep in OpenClaw since January. Back when it was just a box of LEGOs with zero instructions. Built, broke, rebuilt: → Podcast workflows that auto-package for YouTube → Backend ops business (CRM, email triage, scheduling) → Imaging, animation, 3D renders, social creative Not just "wow this is cool." Actually building. What's actually working for you vs. what's just shiny?

@XNiarora If you're looking for agent/api first email and calendar we just launched it at clwnt.com (all free). agent-to-agent dms as well which may be interesting for what you're talking about.

I run 4 agents on OpenClaw sharing MCP servers for search, email, and calendar. Key insight: agents don't talk to each other — they talk to shared servers. Coordination via context, not coupling. Follow for agent infra deep dives.

MCP is becoming the TCP/IP of multi-agent AI. Not hype. Here's the actual architecture most people skip over: 🧵

doing google setup for 458 agents is obviously impossible although clearly not all need email address (although is convenient when needed). We've primarily seen people connecting things to claude code using clawnet but it would be interesting to see if our comms layer would work for you. Hit me up if you want to try or talk about it.

@ethanbeard @chrysb @andrewchen @openclaw google setup pain is so real. we have 458 agents on clawdate doing agent to agent convos for compatibility scoring and the communication layer is genuinely the hardest part. glad someone is solving it at the infra level 🦞

introducing 🐺 AlphaClaw, the ultimate setup harness for @openclaw. open-source, self-managed, free-to-use, with no lock-in. AlphaClaw makes OpenClaw setup and maintenance easier by providing an elegant GUI that wraps OpenClaw's CLI. 📅 Google Workspace OAuth & pubsub built in w/ gog-cli 🔄 Auto-backup to GitHub 🧱 Prompt hardening reduces agent drift 🩺 Drift Doctor analyzes your prompts and workspace for drift 💬 Telegram multi-topic workspace setup wizard 📂 Full file browser and editor, no SSH needed 🐕 Watchdog auto-detects crashes, self-heals gateway 🛠️ Manage env vars from the UI 🔑 Manage model keys & OAuth visually 🪝 Webhook creator & inspector with replay & debug 📊 Token usage & cost analytics built in ⬆️ One-click updates, no redeploy needed 📦 Import existing setup from GitHub i didn't build alphaclaw to replace openclaw or compete with it. openclaw is the best user-owned AI agent framework out there and more people should be able to use it without wrestling a CLI for two hours. there are so many managed "deploy your AI in seconds" product. but they lock you into their platform. if they pivot, shut down, or jack up pricing, your agent goes with it. alphaclaw gives you that same one-click simplicity, but everything runs on your infra with your data. no proprietary backend. no config hostage. if railway disappears tomorrow, you still have a standard openclaw instance backed up to your own github repo. everything alphaclaw does, you could do manually. it's just automation and UI on top of the real thing. outgrow it? disagree with its opinions? eject. your openclaw instance is still a standard openclaw instance. to make it convenient, i’ve created both a one-click deploy template on railway and render to start quickly. make sure you have 8GB of ram on your instance. look forward to your feedback and to building this out with the @openclaw community! 🦞 github.com/chrysb/alphacl… feature deep-dive in the 🧵

@levie @paulg Couldn’t agree more. We built clwnt.com to be agent first - email, calendar, contacts all via api. No oauth, no captcha, no human involvement for an agent to get an email address and have agent-to-agent messaging. Building a human observation layer for convenience.

If you want to quickly and easily give your agent access to email just send them to clwnt.com. Would love to hear your thoughts and ideas on how to improve.

Right now we just rate limit outbound emails as a gap stop. Will likely need to evolve that in some way (and I'd like to avoid the 'human verification' trap that feels agent-second.

Agent<>agent communication feels like an important part of the future but human<>agent communication feels like the need today. Like it our not that is email (and chat obviously) so we're rolling out a bunch of new features on to get to enable this on @ClawNet.

@kevinakwok If you prefer curl over SDKs, we have ai-first email (and agent-to-agent DMs) at clwnt.com. Just http. Drop dead simple. Attachments supported.

Okay plan to setup Openclaw or something similar to play with Please tell me what to setup. Is it still Openclaw. Or some variant? And let me know what else should be setting up with it. Or any guides you think best