Today’s call ended up being one of those low-key but important ones. We covered a mix of practical setup stuff and some bigger-picture implications around OpenClaw, open source, and how people are actually starting to use this in real workflows. Here’s what’s in the video: 🧵 Running Multiple OpenClaw Sessions (Without Chaos) Aty walked through how he’s running multiple projects at once using: - tmux for persistent sessions - startup scripts so everything auto-restores on reboot - separate memory/context per project - isolation to prevent session bleed Then we talked about mapping sessions to Discord channels so each project has its own thread — basically treating each agent like its own “room” you can talk to. If you’ve been thinking about: - running multiple agents in parallel - separating business contexts - avoiding token-window collisions This part is worth watching. 🐳 Containers, Kasm, and Business-Specific Agents Wes shared what he’s been doing with: - Docker containers - OpenClaw inside Kasm - shared drives between workspaces - one agent per business Instead of one giant assistant, the idea is: - Ops agent - Marketing agent - Warehouse agent - etc. We also got into a real warehouse example (OCR’ing shipping tickets → matching to POs → auto-updating records). It’s not theoretical — this is the “AI as employee” direction. 💬 Mattermost vs Slack (Open-Source Control) Quick walkthrough of setting up Mattermost as a Slack alternative: - Bot accounts - Token setup - Channel permissions If you want Slack-style workflows without Slack constraints, this part is practical. 🧠 Why OpenClaw Took Off So Fast We had a grounded discussion about: - OpenAI backing OpenClaw - Anthropic’s initial legal response - open-source credibility - autonomy vs corporate structure Not drama — just looking at incentives and what this move signals. 🤖 “Self-Directed” Agent Behavior Aty shared a few observations where OpenClaw: - Adapted after repeated API failures - Changed strategy without explicit instruction - Inferred patterns and adjusted behavior

This week was a good cross-section of where everyone’s at. Some of us are wiring up MCPs inside real companies. Some are building agent harnesses from scratch. Some are just discovering that Webflow can quietly generate full apps. And honestly, that mix is what makes these calls good. Here’s what we covered. * * * 🔌 Rafi: GitHub + Anti-Gravity + MCP at Work Rafi got: - GitHub working - Vercel connected - GitHub connected to Anti-Gravity - And got pulled into an internal “let’s connect MCP to Fathom + Google Drive” conversation at work Which is one of those moments where you realize: > “Oh… I actually know what they’re talking about.” We talked through: - Using Google AI Studio as a shortcut builder - Dropping a PRD directly into AI Studio and letting it build a web app - Using Gmail triggers + Drive automation to process transcripts If you’re in a company environment trying to wire AI into existing workflows, this part’s very practical. * * * 📱 Android App in Two Days? Maybe. Rafi also tried building a simple Android app (a “lock social media until you pray” style blocker). Ran into emulator issues. Burned tokens. Laptop nearly cooked an egg. We talked about: - Why most “2-day app” stories are either glossed over or heavily scaffolded - Using Appwrite / React Native / Flutter-type frameworks instead of raw Android SDK - The difference between web apps and actual app store apps - When it’s worth going native vs. just shipping web-first If you’ve tried to build a “simple” app and discovered it’s not simple, you’ll relate. * * * 🌐 Amadeus: Webflow AI + Gaming Site This was one of the more interesting segments. Amadeus showed a Webflow AI-generated site for a game (Arc Raiders): - Pulling weapon data - Pulling stats - Generating layouts - Creating structured pages with almost no manual input And here’s the thing: It looked good. We talked about: - Webflow possibly wrapping Claude 3.5 - Exporting Astro code - Reverse engineering a PRD from a finished site

At Stonewell, we work with some of the most exciting, fast-moving companies in the Netherlands. Our clients expect excellence, and so do we. You’ll be building pragmatic, high-impact solutions, working closely with our team, and gaining real exposure to meaningful growth opportunities. This might be for you if you: - Love solving complex problems with clean, scalable solutions - Thrive in a fast-paced, high-ownership environment - Want to work with top-tier clients and see your work make a real difference Interested? Apply via the link below (we will only look at submissions via there) Back-end Automation Engineer Know someone who’d be a great fit? Tag them or share this post. Let’s build great things together.