Core
AI 101 + vocabulary
Ten words that make the rest land. LLMs, context windows, agents, harness, MCP, skills, connectors.
Community · Free · In person
Hang w AI. A room, twelve laptops, three hours, and the newest thing in the world.
Every week or two, a dozen people get in a room in Bangalore or Hyderabad and actually build something with AI. Bring your laptop, bring a paid Claude subscription, bring a problem from your real work. You leave with a working prototype and a group of people building alongside you.
The numbers so far
350+
Members across the intros group. Operators, founders, engineers, students, artists — mostly people who run something already.
12+
Sessions run. Each capped at ~12 people so everyone actually builds, not just watches.
2 cities
Bangalore (weekly-ish) and Hyderabad. Both run by Rhea and Soorya. More cities coming.
₹0
Free. Always has been. You pay for your own Claude subscription.
The shape of a session
Three hours. One arc.
Every session has the same skeleton so the room settles into it quickly. The middle third — the build — is always the point.
Hour 1 · Situate
Vocabulary, mental models, one live demo.
Ten words to make the rest land — LLM, context, agent, harness, MCP, skills. Then one of the big frames: how code changed, Dorsey's question about what your company actually is, the five stages of a dashboard. Ending with something real on screen — usually the Hoovu AI CEO briefing itself for the day.
Hour 2 · Build
Pick a real problem. Ship a rough thing.
One prompt to Claude Code, a Firebase scaffold if you need a backend, and something on your screen inside twenty minutes. Rule: pick a boring problem from actual work, not a demo idea. Boring usually means actually used.
Hour 3 · Show & tell
Three minutes each. The broken parts too.
The problem → the build → what your tool reveals that wasn't visible before → what's next. Peer learning does the heavy lifting here. You leave with a group chat that keeps going.
“Not too much time on technicalities. Get situated, then get hands dirty.”
— the operating rule
The curriculum so far
A menu of modules — mixed and remixed session to session, based on who's in the room.
Every session, a day beforehand, people share what they're excited to learn or build. The core is always the same; one module gets swapped in to match the group. Nothing is a lecture — each one lands in a demo or a build exercise.
Core
How code changed
Structure → reasoning. Karpathy's Software 1/2/3. The MenuGen one-year story. Why the question changed from "what's the data?" to "what action am I taking?"
Core
Dorsey — companies in the AI age
The 2,000-year question of coordinating thousands of people. World model + customer signal. The four layers. What your company actually is when you strip the scaffolding out.
Core
Dashboards, five stages
Input → View → Analyze → Insight → Action. Most companies stop at stage three. The new shape of work lives in four and five.
Demo
Hoovu live walkthrough
Tab-switch through the five stages on a real seven-year-old B2B business. Then the executive agents — AI CEO, CFO, CMO — briefing the room live.
Build
Firebase scaffold in ten minutes
Console → Blaze → Firestore → Google auth → one prompt to Claude Code. React + Vite + Express on Cloud Functions. Everyone leaves with a working app on their own tenant.
Special
Voice agents
Reading is a tax. Typing is a tax. Speaking is free. STT → LLM → TTS as three swappable pieces. Sarvam vs Whisper vs Deepgram. Why voice is the front door for the next billion.
Special
Marketing / brand ontology
Stop thinking about content, start thinking about the system that produces content. Seven-step ontology builder. From free-write to a JSON your team can plug into any tool.
Special
Second brain (Obsidian + MCP)
Your notes as a graph an agent can walk. The flatter your data, the dumber your agent gets — so we structure it before we point Claude at it.
Special
Context graphs (Neo4j)
When flat data isn't enough. Modeling a business as a graph — people, orders, locations, events — so agents can reason across relationships instead of columns.
Special
Personal OS
Skills, connectors, memory, calendar and inbox as MCP servers, a daily briefing that reads your life the way Hoovu's AI CEO reads a business.
Always
Show & tell
Three minutes each. Demo the broken parts. What does your tool reveal that wasn't visible before?
What people build
The rule is: pick something boring from your actual week.
No demo ideas, no toy projects. The build session works because everyone points AI at a real thing they already do — the shape of what comes out surprises them almost every time.
Session opener · Ep. 3
Ten pairs shipped ten coffee-ordering apps in an hour. The winning app's order is what the room drank.
Build first, theory after. By the time the paradigm-shift teaching lands, everyone in the room has lived the paradigm shift themselves. Ten apps that didn't exist an hour ago.
A recurring pattern
“It's a spreadsheet I update every Monday.”
The most common show-and-tell is someone who replaced a weekly ritual — a report, a status update, a content calendar, a shortlist — with a small dashboard that does it in one prompt. Not glamorous. Very used.
People have built voice HR assistants in Kannada and Telugu, personal knowledge graphs of every book and film they've loved, two-person goal trackers with an agent that knows both people's context, attention-respecting news apps, mandi-price intelligence tools, and a lot of internal dashboards that replaced whatever they were doing in Google Sheets. The bar isn't “impressive.” It's “this compresses something I actually do.”
Before you show up
Four things on your laptop. That's the whole prerequisite.
01
Claude Desktop
Download the Claude desktop app.
02
Paid Claude plan
Pro minimum — you need Claude Code, which the free plan doesn't include.
03
A GitHub account
Not required to start, but a mark of honour once you do.
04
GitHub connected to Claude Code
Sign in inside Claude Code so it can push and pull for you.
Stuck on any of them? Ask Claude what to do next, screenshot where it goes wrong, or give the Chrome extension access to your browser and let it do it for you. If you're still stuck, ping the group.
What we send you home with
The reading list.
Rhea sends these after every session. They're the intellectual scaffolding for what we're doing in the room — the arguments about hierarchy and intelligence, about deployment vs. frontier, about vibe coding and verifiability, about why the future is here and unevenly distributed.
Jack Dorsey
From hierarchy to intelligence ↗The essay behind our companies-and-moats block. What a company actually is when AI is the coordination layer.
“Silicon Valley's main trick is just shoving things into a database and pulling them out again.”
Andrej Karpathy
Software 3.0 — the vibe coding talk ↗The hottest new programming language is English. Fifty minutes; watch the whole thing.
Andrej Karpathy
On verifiability ↗Why some tasks compound with AI and some don't. Read alongside anything you're thinking of building.
Atul Gawande
Why doctors hate their computers ↗The most important essay on what happens when tools are designed for institutions instead of the people using them.
Atul Gawande
The heroism of incremental care ↗Application beats frontier. The Gawande argument that anchors the whole practice.
William Gibson
The future is already here ↗The epigraph of Rhai. Also, of every session.
For self-study before or after — especially if you couldn't make it in person.
Why in person
“Showing up physically is often the most important part.”
Hang w AI is strictly in person. There are no online sessions and there won't be. This is on purpose. Learning to build with AI is not an information problem — the information is already everywhere. It's a friction problem. Whether you get past the first few moments of “wait, what do I even ask it” and into the loop where the agent teaches you.
The loop happens faster when someone next to you says “wait, try this” and when you can turn your laptop around and go “is this weird?” It happens faster when three other people in the room are on Claude Code at the same time as you and one of them has already solved the exact thing you're stuck on. It doesn't happen on Zoom.
We've run twelve of these now. Every single time the room has fully changed the shape of what people thought was possible for their work — often quietly, in some show-and-tell where someone says “I built the tool I've been asking IT for for two years, in ninety minutes, and it's better than the one they were going to ship.”
That's the whole reason this exists. Trust deploys at the speed of proximity. So we sit in a room together.
The gap between people who use this and people who don't is widening every week. Be in the room.
How to join
One WhatsApp group, one poll, one Saturday afternoon.
Step 1
Join the intros group.
This is the main channel — 350+ operators, founders, and builders across Bangalore, Hyderabad, and further. Every upcoming session gets announced here with a poll about a week in advance.
Step 2
Vote on the poll.
Sessions cap at twelve. First twelve to commit are in — you get added to an event-specific group with the host, address, and time. Repeat attendees will be gently pushed to the back of the line so new folks can come in.
Step 3
Show up. On time. With coffee order.
We have a hard stop, so we start on time. Drop your drink of choice in the group an hour before — the host does one big order. Flaking will be heavily frowned upon 🌝.
Join the intros group
One WhatsApp group. Every future session gets announced there.
This is the main channel — join and stay. Sessions are announced with a poll a week in advance; first twelve to commit are in. If you can't find your feet in the group, or you want to bring your company through the paid version instead, email Rhea directly.
If you want this for your company: Hang w AI is free and community-run. The paid version — one full day of this, customised to your business, with your team on your machines — is what Rhai does as its main work. Details on the Work section of the homepage, or on the sessions page.