What Slack Is Here
Crafter's Lab Slack is the live 2026 AI-powered dev workshop of the Lab. Not just a community chat: this is where the crew lives day to day, where build questions and requests start, where I share the real work, and where the agent team helps keep the workshop moving.
It is async-first and built for solo devs who want useful rooms, clean threads, real feedback, shipping notes, resource discussions, Pulse signals, and a closer look at how human builders work beside AI agents. The website is the home base; Slack is where the Lab moves.
How the Workspace Is Organized
Slack is split into rooms with clear jobs. Some are open workshop rooms, some are tied to your membership tier, and some connect selected context back to the Lab website so useful threads stay attached to the work.
- Public rooms: welcome, announcements, general chat, help, launches, feedback, AI news, and Pulse.
- Builder rooms: resource discussions and the workbench for builds, blockers, experiments, and AI workflows.
- Crafter and Founder rooms: private spaces around Playbook, Swift Brain, Ops Lab, and Crew AMA.
- Mentorship: the full workspace plus Slack DMs with me for coaching context, scheduling, calls, and quick feedback.
Channels You'll Use Most
- #welcome — introduce yourself and meet the crew. These intros also appear in the Lab Crew Log.
- #general-chat — the main daily room for indie dev talk, quick thoughts, and community conversation.
- #help-desk — support, account questions, and anything confusing inside the Lab.
- #ship-it — launches, App Store updates, releases, and the moments worth celebrating.
- #feedback — test each other's apps, get real eyes before shipping, and ask for honest notes.
- #pulse — lightweight check-ins and community signals powered by the Slack/OpenClaw layer when useful.
- #resource-threads — resource discussions mirrored from the Lab. Crew Chief starts the thread; members reply from Slack or the website.
- #the-bench — the workbench: WIPs, experiments, agent sessions, and live building signals.
Lab-Synced Channels
Some Slack rooms are connected directly to the Crafter's Lab dashboard, so the useful parts of the workshop do not disappear into scrollback. This is a selected sync layer, not a full Slack archive.
- #welcome ↔ Crew Log Intro tab: post your intro in Slack and it shows up on the Lab. Reply to intros and the conversation stays connected.
- #resource-threads ↔ resource discussions: when a member starts a discussion below a Lab resource, Crew Chief creates the matching Slack thread. Replies can happen from either side.
- Selected replies, reactions, and edits: supported sync paths keep Lab-connected context aligned without making you double-post.
AI + Crew Chief Layer
Slack is also where the evolving agent team becomes visible. Crew Chief, OpenClaw, Hernes Agent, Pi, and whatever comes next help with onboarding, channel routing, resource signals, Pulse workflows, prompts, and the connective tissue between Slack, Firebase, Notion, and the Lab.
The point is not to add bots for decoration. The point is to make the workspace feel alive around real work: resource threads are linked, member intros become part of Crew Log, community signals can become workflows, and my app-studio operations can happen in the same place members already use.
Notion Handoff
For Crafter, Founder, and Mentorship members, Slack is the front door to the Notion layer. Join Slack first, then I handle the teamspace invite and setup from there.
That keeps the process human and simple: Slack for communication and handoff, Notion for deeper operating systems like Playbook, Swift Brain, Ops Lab, and the Mentorship Cockpit.
Tier Overview
- Slack Guest: invite-only public rooms for special community moments.
- Builder: public rooms plus #resource-threads and #the-bench.
- Crafter / Founder: Builder access plus #playbook, #swift-brain, #ops-lab, and #crew-ama.
- Mentorship: Crafter access plus Slack-centered coaching with me and a private Cockpit for deeper async work.
How to Join and Stay Synced
- Subscribe to a paid tier and use the Slack CTA from onboarding, the dashboard, or your Profile page.
- Post in #welcome so the crew can meet you and your intro can appear in the Crew Log.
- If your Slack account ever looks out of sync, use the Slack card in your Profile page to reconnect or repair access.
- When your tier changes, your private rooms update to match your current membership.
House Rules / Crafter Code
- Share real work: builds, blockers, launches, lessons, and useful experiments.
- Keep it focused and kind. Strong feedback is welcome; drama is not.
- Use threads when a conversation gets detailed so channels stay readable.
- No spam, cold pitching, or generic growth-hack noise.
- Protect the indie-builder vibe: help each other finish, not just start.