Last day to buy your AIS Live tickets! We brought together real AI business owners to show you guys what they actually sell and how they do it. July 11th and 12th (this weekend) and completely virtual. Get your ticket HERE

When I started the AI Automation Society, I had no idea it would grow into this. Under two years later and we just crossed 400k. The largest AI automation community in the world. Yes, the space is exploding. But this community grew because you guys keep showing up, asking questions, dropping answers, sharing builds, and helping the person one step behind you. Huge thank you to the team that keeps this thing running, and to every single one of you who's posted, commented, or just been here. I feel lucky to get to do this. So excited to share with you guys what we've been quietly cooking up over here at AIS...👀 - Nate

So I'm sure you guys have heard the term "AI slop", and everyone sorta defines it differently. Maybe you think it's those TikToks of AI-generated fruits going on dates. Maybe it's infographics with misspelled words. Maybe it's something else entirely. But I want to talk about it in the context of communication. Internal, external, content you put out into the world. I write my LinkedIn posts with AI. My agent knows my business, how I write, how I speak. That's just how I work now. And there's nothing wrong with that. I think everyone should be using AI to write if it makes them more efficient. But this isn't a binary yes or no. It's a spectrum. Sometimes AI can draft and send automatically. Most of the time, I want it to just draft. Then I review. If someone sends me an email with em dashes everywhere, I don't actually care at all that they used AI. The fact that I can clearly tell it's AI-generated isn't the problem. What I do start asking is: → Did they proofread this? → Is this completely accurate? And subconsciously, I might start losing trust. Not just in the email but in the person who sent it. Our job here has changed from writer to reviewer. This quote has really stuck with me: "You can outsource your thinking, but you can never outsource your understanding." When your name is attached to the content, you take credit if it lands, as you should. But that also means you need to take accountability if it's incorrect. Taste and reviewing are becoming more important than ever. AI is super intelligent and powerful, but I don't want to see a world where we trust AI so much, that we stop reviewing things, and then the human on the other end of the content starts losing trust in us. That's why even though I write with AI, and people know that, I still try my best to disguise it and make it sound as "Nate" as possible. Check out the LinkedIn post I just wrote about this HERE

I stopped opening IDE's The setup Two windows: 1. Claude Desktop App (for research, planning, long conversations) 2. Mac terminal running Claude Code (for all execution) Why this works better than running Claude Code inside an IDE When Claude Code runs inside an IDE terminal, every file operation passes through the editor's plugin layer: file watchers, extensions, lock conflicts. In a standalone terminal, Claude Code talks directly to your filesystem. No interception, no translation. The practical difference: - File writes are instant. No "file changed externally, reload?" dialogs. - Git operations run clean. No source control extension competing for the same lock. - Shell access is unfiltered. Package installs, curl, deployment scripts, SSH tunnels. All native. - No extension memory overhead. My terminal session uses a fraction of what VSCode was consuming. - MCP servers (GitHub, databases, APIs) wire in directly without fighting IDE plugin architecture. What a real session looks like Last week I built a Cloudflare Worker with KV bindings. One terminal window: - Claude Code scaffolded the project structure - Wrote the Worker handler, wrangler config, and KV namespace bindings - Ran wrangler deploy - Tested the endpoint with curl - Fixed a routing issue based on the error response - Committed and pushed Total time: under 20 minutes. I never typed a line of code. I described what I needed, reviewed the output, approved the operations. You're not coding in a terminal. You're directing an agent that codes for you. How to set this up (10 minutes) If you have a Mac and Claude Pro or Max: (On a PC? Your setup instructions are in the attached file.) 1. Install Claude Code: open terminal, run the install command from Anthropic's docs. 2. Run "claude" in any project directory. You're in an agentic session. 3. Open Claude Desktop App alongside for planning, research, and longer thinking conversations. Optional but useful: - Set up a .claude directory in your project with a CLAUDE.md file. Same idea as onboarding docs, but for your coding agent. Persistent instructions about your project, coding standards, and preferences.

Make sure to take note of the name changes. It is now OpenClaw. Hopefully final :) Clawdbot -> Moltbot -> OpenClaw! https://openclaw.ai/blog/introducing-openclaw