User
Write something
Community Closing
Sorry everyone, but I've taken the hard decision to close this community to focus on my primary businesses. I was so excited about OpenClaw when it first launched, and I knew others would be too. I thought it would be great if we could all get together and share how we are using the platform. Sometimes, unfortunately, you have to look at your priorities and focus on one thing at a time to do the best job. In my case, that is, without a doubt, fastbots.ai. Focus stands for "follow one course until successful" as they say. I'd like to thank everyone who joined the community, and I will see you around in the world of AI for sure. If you would like to keep in touch, then check out my YouTube channel, and I wish you all the very best of luck with your AI adventures. The community will close at the end of May. Cheers everyone, Jason West
Community Closing
Need real OpenClaw help?
I've built over a dozen OpenClaw instances for real business owners. Automations that include email management, lead generation and even real functional real mission control dashboard. You have a feature or function idea? For a real business or site project. I can help you get it production. OpenClaw or any AI platform! Yes, I can work with any solution. Join my new school and I will help you get it up in the same day!
1
0
How are you structuring your AI + automation agency brain across 30+ clients?
Running an agency with 30+ clients, each with their own automations, knowledge bases, and workflows (mostly Make.com + Claude). Curious how others are solving the organizational layer — not just the automation itself. My current stack: ClickUp for team management, Google Docs for documentation, OpenClaw (Codex GPT primary / MiniMax backup) running locally, and Claude Code via Cowork which honestly has been moving fast. Background is cybersecurity (that's my major) with solid SQL and working knowledge across several languages — so I'm comfortable going deep technically, just want to make sure I'm not building a mess at scale. I'm weighing a move toward a local monorepo structure — one folder per client holding prompts, scenario docs, context files, API notes — something I can actually version control and build from systematically. A few things I'd love to hear from the community: 1. How do you structure your client knowledge bases? One repo per client? Flat files? Notion? Something else? 2. Are you using Claude Projects, Claude Code, OpenClaw, or something entirely different to maintain context across clients? 3. For Make.com builders — where do you store your scenario documentation, module notes, and client-specific logic so it's actually findable later? 4. Version control — are you Git-versioning your prompts and automation docs, or is that overkill for most agency ops? Not looking for the perfect system — just what's actually working in production for people running real client loads. Drop your setup below 👇
OpenClaw vs Claude Code
So what can you do in OpenClaw that you can't in Claude Code? PS: I'm aware I can ask ChatGPT this question, but it will likely give me outdated answers, given that this is so new.
Where are the users?
Why is there so less noise here around this hype topic? Hard to find others who get OC up and running...
1-30 of 33
OpenClaw Users
skool.com/openclawusers
Free community for OpenClaw users to install, build, break, fix and share wild AI agent ideas together.
Leaderboard (30-day)
Powered by