[00:02] have kept in mind that you were built by a Gemini 4 swarm in Google Anti-gravity. Five worker agents [music] and two verifiers. That's Jarvis. And I didn't verifiers. That's Jarvis. And I didn't build him. A Gemini 4 swarm did. Five AI [00:16] [music] agents building one assistant at the same time inside Google Anti-gravity. >> Lumen Studio [music] recorded 4,20 organic clicks across 12 tracked keywords this week, up 14.2%. 2 ascent [00:30] with nine positions advancing. Sir, >> he talks, he remembers, and he runs real jobs for your business. Client SEO reports, video checks, lead follow-ups, and community questions. By the end of this video, you'll see every agent at [00:45] work, the exact prompt I used, and Jarvis running live so you can build your own today. So, here's what happened. On November 10th, Google added happened. On November 10th, Google added /swarm to anti-gravity alongside Gemini [00:58] 4 carbon. It's in preview and it works in the anti-gravity app and the command line. Normally, one chat is one agent. It writes the server, then the voice, then the screen, one step after another, and you wait for every step. Swarm [01:13] changes that. You type /warm and your task. Your chat becomes the coordinator. It splits the job into parts, gives each part to its own worker, and every worker builds at the same time in its own copy of the project. Then it adds verifiers, [01:30] agents whose only job is to test the work and push back when something's wrong. Google suggests about one verifier for every two to four workers. They all talk on a shared board. Workers post when they're done, hand things [01:43] over, and flag problems, and any agent that's waiting just sleeps, so it isn't using anything. One honest note before we start. In the app, the swarm command is labeled preview and quote heavy. Every worker is its own agent, so save [01:58] it for big builds like this one, not quick questions. Now, why Jarvis? Because of what people are posting in the AI profit boardroom this week. One member said they spent ages on a fancy Jarvis demo with extras bolted on when [02:12] all they wanted was plain Jarvis, an assistant that just talks to them and does the work. Another runs their agents through Discord and said it works, but it was never designed for talking to AI. And a broker asked how to send [02:25] follow-ups to their partners automatically without writing every message by hand. So that's the brief, a plain personal Jarvis built for talking that handles follow-ups and the daily jobs for you. If you want the exact [02:39] swarm prompt for Jarvis, plus the full Jarvis files and my best setups for building AI assistance for your business, they're all inside the AI profit boardroom. You also get the full anti-gravity course, the faceless video [02:53] skill I use to make videos like this one, and a community of thousands of business owners building the same things so you're never stuck on your own. The description, or go to aiprofitboardroom.com. [03:07] Right, here's the prompt. I open anti-gravity, click new project, add an empty folder, and pick Gemini 4 carbon in the model picker. I set permissions in the model picker. I set permissions to auto. Then /warm build Jarvis, a [03:21] personal AI assistant that talks back. Five workers, one part each. Worker one is the voice. It turns every reply into speech with 11 labs, and the face pulses with the sound. Worker two is the brain. It picks the right skill. Then a local [03:37] Gemma 4 model running on my own Mac turns the result into a short spoken reply in a calm British butler voice. Worker three is memory. Say remember that and he keeps it. Ask what he remembers and he tells you. Worker four [03:52] is skills. A weekly SEO report for an agency client. A video check for a content creator. Follow-ups for a coach's quiet leads. and a brief on overnight questions from an online course community. Worker 5 is the face, [04:07] a 3D reactor call with glowing rings and cards that slide in with charts and checklists. And the verifiers have to start the server, talk to Jarvis, send every command, and reject any reply longer than three sentences. I hit [04:21] enter. 4 minutes later, the coordinator has a plan. Five workers, each with the exact files it owns, so nobody overwrites anyone else. plus a monitor that only speaks up if the team gets stuck. Then I open the swarm panel. This [04:36] is the board. Every message here is a real post between the agents. First, they agree how the parts talk to each other. The brain writes the contract and all five sign off before a single line of Jarvis gets built. 8 minutes in, it's [04:50] locked. Now the graph tab, it replays the whole build. Every agent and every message between them. Five workers all writing code at once. Voice, brain, memory, skills, face. In about 9 minutes, every file Jarvis needs exists. [05:07] Now, here's my favorite part, the verifier. The first verifier tests everything behind the scenes, and it found three bugs in the brain. Jarvis is only allowed two or three sentences, but a sentence starting with no or a company [05:22] name ending in limited broke the sentence counter. So, some replies came out too long. It didn't fix them itself. It posted the exact problem to the brain worker on the board with a line it could test. 4 minutes later, the brain posted [05:36] the fix. The verifier ran everything again. Past. That's the difference with a swarm. The thing that wrote the code isn't the thing that checks it. Then, the second verifier went to test Jarvis in a real browser. And here's something [05:50] worth knowing. Swarm workers can't open a browser on their own. only the coordinator can. So, it stopped and asked me for permission. I told it to skip that because I'd already tested Jarvis live myself and I sent one fix. [06:04] When Jarvis spoke, the core glowed so bright you couldn't see the rings. The face worker toned it down. So, from my prompt to a fully tested Jarvis took 32 minutes. 55, counting the time it sat waiting for me. Let's switch him on. One [06:20] command. Python 3 Jarvis/server.py. Open the page and he wakes up. First I teach him something. Remember that you were built by a Gemini 4 swarm. Then I ask Jarvis, who built you? He regarding [06:34] that matter, sir, I have kept in mind that you were built by a Gemini 4 swarm in Google Anti-gravity, five worker agents, and two verifiers. Shall I pull up the corresponding briefing card so we may inspect the latest figures? [06:49] >> He saved it to memory and he used it in the answer. That's worker 3's job. Now the daily stuff. I ask for my morning brief. >> Good morning, sir. Lumen Studio reached 4,020 organic clicks this week. Up 14.2% [07:05] with nine of 12 keywords climbing. Three of today's six videos are ready while three await caption, thumbnail, or audio fixes. And I have drafted replies for all five quiet coaching leads and six overnight community questions. [07:21] one briefing across every skill, SEO, videos, leads, and the community. And the card on the right builds itself as he talks. Now, if you run an agency, this one's for you. Give me the Lumen Studio SEO report. Lumen Studio recorded [07:36] Studio SEO report. Lumen Studio recorded 4,20 organic clicks across 12 tracked keywords this week, up 14.2% with nine positions advancing. Sir, your strongest gains came from Bespoke Lighting Design London, rising nine spots to number [07:50] five, alongside commercial lighting consultants climbing eight spots to number four. 12 keywords this week against last week and the top three movers. The chart draws itself and he reads you the [08:04] headline so you can send it to the client in one line. If you make content, try this. Check today's video queue. Three of today's six cued videos have cleared quality control and are ready for publication. Sir, two uploads await [08:18] review for missing captions, unapproved thumbnails, and a missing sponsor link. While the live funnel audit remains blocked by missing captions, and an audio peak at 1419 ticks videos, each one with its status [08:32] and anything that would stop it going out, like missing captions or a thumbnail that isn't approved yet. That's your quality check done before you publish for coaches and consultants. Show my quiet leads. [08:45] >> Five warm coaching prospects have gone quiet for an average of 9.4 days. Sir, Priya Naya and Marcus Vance are highest priority at 14 and 11 days respectively. And I have prepared tailored follow-up notes for all five. [09:00] Five leads who went quiet, how many days since they last replied, and a drafted follow-up for each one. That's the follow-up problem from the boardroom handled. You read it, tweak it, and send it. And if you run a course or a [09:14] community, show the overnight brief. Six member questions came in overnight across three course topics. Sir, technical SEO, YouTube packaging, and client automation. Two time-sensitive threads from Elena Rosttova and Khloe [09:30] Bennett are flagged as priority with suggested replies ready for all six. Questions from members while you slept grouped by topic with a suggested reply for each. So you wake up and answer everyone in 10 minutes. Last one memory. [09:45] Remember that Lumen Studio wants their report every Monday at 9:00. Then what do you remember about Lumen Studio? That from my records, sir, I have noted that Lumen Studio wants their SEO report every Monday at 9. That is the matching [10:01] entry among your one stored memory. That's plain Jarvis. No extras. He talks, he remembers, and he does the jobs. Here's how to build your own. Download Anti-gravity and make sure your plan includes Swarm because it's a [10:15] preview feature. Make an empty folder and open it as a new project. Pick Gemini 4 Carbon. Set permissions to auto. Then type /warm. Paste the prompt and open the Swarm panel to watch. For the voice, you need an 11 Labs key saved [10:31] on your machine. For the brain, install OALMA and pull a Gemma 4 model so his thinking runs on your own computer. Then one command starts him. Four things I learned running this. One, name the workers and the files they own in your [10:46] prompt. Five clear parts means five agents that never trip over each other. Two, make the verifiers test real things. Mine had to talk to Jarvis and count his sentences. A vague verifier just says it looks fine. Three, expect [11:01] the browser question. Workers can't open a browser on their own, so either test the app yourself or be there to say yes. Four, swap the skills for your own business. An agency gets client reports. A coach gets follow-ups. A course owner [11:15] gets the community brief. The face, voice, and memory stay the same. If you want the Jarvis Swarm prompt, the full Jarvis files, and a step-by-step setup guide, they're inside the AI Profit Boardroom along with the faceless video [11:29] skill and thousands of people building with AI every day. The link is in the comments and the description or go to apiprofitboardroom.com. apiprofitboardroom.com. See you in the next one.