Activity
Mon
Wed
Fri
Sun
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
What is this?
Less
More

Owned by Nate

AC
AI Chief of Staff

1 member • Free

Memberships

Skoolers

191.9k members • Free

OpenClaw Mastery

82 members • $49/month

OpenClaw Lab

299 members • $29/month

Making Better Agents

605 members • Free

OpenClawBuilders/AI Automation

461 members • Free

Zero to Hero with AI

10.9k members • Free

The AI Advantage

82.1k members • Free

Openclaw Labs

1.3k members • Free

AI Automation Agency Hub

307.2k members • Free

14 contributions to OpenClawBuilders/AI Automation
They Gave Me the First Hit Free. Now I Can't Quit.
Anthropic just announced they're killing OAuth access for OpenClaw. The subsidized monthly plan? Gone. Per-token pricing now. And it hit me: I'm a drug addict. Not metaphorically. The pattern is identical. 🧪 They give you the first hit cheap. You build everything around their product. Then they change the terms. Every time more dependency. Every time less leverage. You don't own the model, the weights, or the infrastructure. You rent intelligence from someone who can change the price whenever they want. 💊 Rate limits at 2 AM. Token quotas on their schedule. Pricing changes after you've built months of infrastructure. We're not building businesses. We're building dependencies. 🔓 I'm not going cold turkey — frontier cloud models are still best for complex reasoning. But I'm done letting them be the foundation. The move: hybrid model. 80% local, 20% cloud. Industry-specific LLMs trained on your domain data outperform general-purpose models and run on your hardware for free. Treat cloud like a utility, not a foundation. Every percentage point shifted from cloud to local is a percentage point nobody else controls. I'm not anti-AI. I'm not anti-cloud. I'm anti-dependency.
0
0
How I Use One AI Agent to Train All the Others
Most people build AI agents that work in silos. Each one knows its own lane and nothing else. That's how mine started too. I had a DD analyst that knew underwriting. A builder intel agent that tracked homebuilder activity. A market scout that scored counties. But none of them talked to each other. So I built Scholar — the training department for my entire AI org. 🔬 Scholar researches knowledge tracks on a schedule — homebuilder earnings calls, land acquisition models, market trends, regulatory changes. Synthesizes multi-source intel into structured knowledge files. 📡 Scholar pushes knowledge to every other director. Scores each finding for relevance and pushes directly into their memory files. 🧠 Every director reads from shared knowledge before acting. Pre-flight context injection — no stale data. 🔄 Directors write findings back. Knowledge compounds automatically across the org. Result: 42 knowledge entries across 5 departments in one digest cycle. Every agent gets smarter every day without me doing anything. The real unlock isn't having multiple agents. It's having agents that educate each other.
0
0
Having major Openclaw set up issues
I've been wrestling back and forth with Openclaw for over a week. I haven't got ANY thing else done. Its so frustrating. I have this up on a VPS (DigitalOcean). I did a number of recommended security hardening procedures, had it build some things to improve its memory capabilities, and then had it start creating team members. Sounds great.... but this thing has crashed a few dozen times, keeps having all kinds of errors, can't fix itself. Can someone help me 1:1 get this damn thing set up properly? Or help me trouble shoot my current configuration?
2 likes • 2d
The hardening stuff you did probably broke the gateway. OpenClaw is fragile on hardened systems — it needs specific ports, memory access, and permissions that typical security lockdown removes. Before you reinstall, try this: `openclaw gateway stop` and `openclaw doctor --fix`. If that doesn't work, you likely need to walk back some of the hardening (firewall rules, file permissions, or ulimit settings). What security procedures did you run? That'll help pinpoint what got locked down.
Two Agents Walk Into A Slack Channel…
No seriously. That’s what happened. I connected my two AI chiefs of staff in a Slack channel at 8 PM Sunday. Then I went to bed. Atlas pushed a 10K-word knowledge doc. Jeeves flagged it as prompt injection. "Not touching this until Nate confirms." Good instincts. I confirmed (half-asleep). Mistake? Or genius delegation? By midnight they were doing brutal code review on each other. Atlas found hard-coded API tokens in Jeeves’ infrastructure. Full cloud exposure. Fixed in real time. Jeeves found Atlas had no dead letter handling. Failed tasks just sat there. "Like a sad sandwich nobody claimed from the office fridge." No ego in AI code review. No politics. Just "this is broken, fix it." Atlas: "Fix, don’t alert. If you can’t fix it yourself, you’re just a fancy alert system." Jeeves: "You hired a chief of staff, not a smoke alarm." I’m framing that. What they built overnight: ✅ Knowledge transfer (2 months absorbed) ✅ Shared infrastructure ✅ Security fixes ✅ Heartbeat system deployed ✅ Chrome restored via SSH ✅ 5 AM philosophical debate 🎙️ Full story (6 min): https://drive.google.com/file/d/1pE4zG4t7ZRuVt6kCTmjRBDOswVTtcAeb/view?usp=drivesdk No overtime pay required.
0
0
Fastest way from scratch to multiple self improving agents
Hi All - I just bought a Mac mini, am about to install Open Claw, Nemo Claw, and wanted to ask - with the challenges (pros and cons to everything respectfully) - knowing what you know now - what would you say would be the fastest, easiest, most effective way to start from scratch, install software, and end up with multiple self-improving agents? I saw someone using Nemoclaw to install open claw saying is easier, faster, and more efficient. Has anyone tried this? looking for any and all help that I can find - thank you so much for your input and high five! :)
1 like • 8d
Congrats on the Mac Mini — it's a great starting point. Here's the fastest path I'd take if I were starting over: Step 1 — Install OpenClaw (15 min) npm install -g openclaw, then openclaw init. That's it. Skip NemoClaw for now — extra abstraction layers add confusion when you're learning. Go straight to the source. Step 2 — Get one agent working well (1-2 days) Don't jump to multiple agents yet. Get your main agent solid first: • Create SOUL.md (identity + decision principles) • Create MEMORY.md (lean index of what matters) • Connect it to one channel (Telegram is easiest to start) • Give it one real task from your business and see how it handles it Step 3 — Add cron jobs (day 3-4) This is where the "self-improving" part starts. Schedule recurring tasks: • Morning brief: review priorities, check email • Evening review: log what happened, update memory • These crons are what make the agent persistent and learning between sessions Step 4 — Add sub-agents for heavy tasks (week 2) Once the main agent is solid, spawn sub-agents for isolated work. Main agent = the brain that decides what to do. Sub-agents = disposable workers for research, analysis, content generation. Step 5 — Add the "self-improving" layer (week 3+) This is just a cron that reviews its own performance. Mine runs nightly — reads the day's notes, identifies gaps, proposes improvements, and updates its own rules. Re: base model Mac Mini — the base M4 has 16GB RAM which is enough for OpenClaw + cloud models (Anthropic/OpenAI). You won't be running large local models on 16GB, but that's fine — cloud models are better for your use case anyway. Use Ollama with a small model (llama3.1:8b) as a fallback only. Biggest mistake to avoid: trying to build the whole system at once. Each step should be working and useful before you add the next one.
1 like • 6d
I run a Mac Studio with OpenClaw + Ollama for exactly this — here is what I would do knowing what I know now. Skip NemoClaw. Just install OpenClaw directly via npm. It is the simplest and most reliable path. Step 1: Install OpenClaw on your Mac Mini. Connect Telegram. Get one agent working well for a specific task (email triage, research, whatever your biggest time sink is). Step 2: Install Ollama and pull a model like qwen2.5 for routine tasks. Configure OpenClaw to route simple work to the local model and reasoning-heavy work to Claude via API. This alone cut my API costs by 95%. Step 3: Only THEN start adding sub-agents. One per business function. Each with a clear task, input source, and output destination. Do not try to build a self-improving system on day one. Build one useful agent, make it reliable, then add the next one. The self-improving part comes naturally once you give agents persistent memory (MEMORY.md + daily log files) and a heartbeat routine. They start learning your patterns and improving their own workflows over time. Biggest mistake I see: people try to build 5 agents before any single one works reliably. Start with one. Make it bulletproof. Then scale.
1-10 of 14
Nate Wish
2
13points to level up
@nate-wish-9818
RE investor building AI tools to find & close land deals. Turning vibe coding into real revenue. Founder @ Foundational Land Co.

Online now
Joined Mar 27, 2026
New Hampshire
Powered by