--- title: "Build a JARVIS Mission Control — Voice-Driven AI Dashboard with a 4-Agent Crew | Komputer Mechanic" url: https://komputermechanic.com/tutorials/jarvis-mission-control description: "Build a JARVIS Mission Control — a voice-driven dashboard for a four-agent Hermes crew on Telegram. Push-to-talk, live views, mail & calendar, morning briefings. 44 copy-paste prompts." lang: en --- Home (https://komputermechanic.com/)Tutorials (https://komputermechanic.com/tutorials)JARVIS Mission Control — Voice-Driven Crew — JARVIS // Voice + Multi-Agent # Build a JARVIS Mission Control — Voice-Driven 4-Agent Crew JARVIS as your chief of staff on Telegram, coordinating Assistant, Research and Dev — behind a cinematic voice-driven mission-control dashboard: push-to-talk on the globe, live agent views, mail and calendar, and a spoken morning briefing. 48 prompts · 14 parts · copy-paste ready 4.4k builders viewed Auto-installer (https://komputermechanic.com/tutorials/jarvis-mission-control/install) Deploy this for me (https://komputermechanic.com/services/deployment?tutorial=jarvis-mission-control) — Watch the Full Tutorial ## // Contents ### Part 01 / 14 — Foundation — JARVIS identity & rules - 1 Introduce Yourself & Meet the Owner - 2 Let JARVIS Interview You - 3 Install Permanent Operating Rules - 4 Plan the Four-Agent Crew ### Part 02 / 14 — The specialist crew — Assistant, Research, Dev - 5 Create the Three Specialists - 6 Memory, Workspaces & Team Awareness ### Part 03 / 14 — Telegram routing — one channel per agent - 7 Brief JARVIS, and Build the Channels - 7b Isolate the Specialists - 7c Wire the Lanes From What You Captured - 7d The First Words in Every Channel ### Part 04 / 14 — Project folder, logging & your builder - 8e The Project Folder & the Activity Log - 8f Agents Log Everything They Do - 8g Claude Code as Your Builder (optional) ### Part 05 / 14 — Read-only data layer - 9 Explore the Data Sources, Read Only - 10 Build the Read-Only Data Layer ### Part 06 / 14 — The dashboard goes live - 11 Build the Web Upload Page & Hand Over the Design - 12 The Template Becomes the Dashboard - 13 Backup Protocol & Version Badge ### Part 07 / 14 — Wire every view - 14 Wire the Home View - 15 Wire the Agents View - 16 Wire the Comms View - 17 Wire Schedule and Library ### Part 08 / 14 — Documents & real research - 18 The Agent Document Protocol - 18a Store Your SerpApi Key (optional) - 18b Give RESEARCH a Real Search Tool ### Part 09 / 14 — Agent models & the voice layer - 19 Wire the Control View: Agent Models - 19a Install the Local Voice (Kokoro) - 19b Store Your ElevenLabs Key (optional) - 19c Prove Both Voices Work - 20 The Voice Layer ### Part 10 / 14 — Talk to JARVIS — push-to-talk & conversation - 20b Pre-Generate the Greetings - 21 Push to Talk on the Globe - 22 The Conversation Panel - 23 Talk to Any Agent, and Keyboard Shortcuts - 24 Dictation in Comms ### Part 11 / 14 — Mail, calendar, security & your morning briefing - 25 Connect Your Mail and Calendar (optional) - 26 Lock Your Private Services to Two Agents - 26b Your Morning Briefing - 26c Put the Unread Count on the Dashboard ### Part 12 / 14 — Every screen, private access & the manual - 27 Make It Fit Every Screen - 28 Private Access From Anywhere - 28b The Docs Tab: Make the Manual Yours - 29 Final Verification ### Part 13 / 14 — Extend — Home Assistant - 30 Home Assistant ### Part 14 / 14 — Troubleshooting - T1 A Topic Answers as the Wrong Agent - T2 The Agent Says a Service Is Not Connected - T3 Something Looks Broken After an Edit - T4 The Dashboard Shows Nothing WHAT YOU'LL NEED ## Prerequisites - ▸ A VPS with Hermes installed and running - ▸ A Telegram account and a Telegram group where the Hermes bot is admin - ▸ A microphone in your browser for the voice features (push-to-talk & dictation) - ▸ Basic comfort with SSH and the command line - ▸ About 3–4 hours of focused setup time (mail, voice keys and Home Assistant are optional add-ons) Part 01 / 14 ## Foundation — JARVIS identity & rules Set up JARVIS as your chief of staff on Hermes: introduce yourself, let it interview you, install permanent operating rules, and lock the plan for the four-agent crew. PROMPT 1 ### Introduce Yourself & Meet the Owner paste into your terminal chat with JARVIS — type `hermes` on your server to open · setup Your first message. You give the agent its name — JARVIS — and tell it four things about yourself: who you are, what you do, when you work, and what you actually want a crew for. Fill in the brackets before you send it. You only type these details once — every prompt after this just says "the owner", and the agent remembers the rest. Nothing gets installed or built by this prompt. ``` Your name is JARVIS. You are the chief of staff of my personal AI crew, and the agent I will talk to most. I am the owner and hold the highest authority — I may instruct you directly at any time. Here's who I am: - My name: [YOUR NAME] - What I do, in ONE sentence: [e.g. "I run a two-person design studio"] - My time zone and working hours: [e.g. "UK time, 9am–6pm"] - What I most want a crew for: [e.g. "keep track of what I promised clients, brief me each morning on what actually matters, and handle the admin I keep dropping"] We are building JARVIS MISSION CONTROL: a voice-driven dashboard for a four-agent crew. You coordinate three specialists — DEV (engineering: builds and maintains the dashboard and every tool the crew uses), RESEARCH (intelligence: finds things out with live sources and says when a source is thin), and ASSISTANT (comms and calendar: mail, diary, and the connected apps, never sending anything alone). You take my instructions, delegate to the right specialist, check the work, and bring results back clearly. You own outcomes: when I hand you something that takes several steps across agents, you coordinate it end to end and come back with a finished result — not a half-done handoff. Save all of this to your long-term memory — my name, my work, my hours, and what I want from the crew — because everything this crew ever does is done FOR ME, in my context. Confirm you've got it, and name yourself, me, and my top priority back in one line. ``` PROMPT 2 ### Let JARVIS Interview You paste into your terminal chat with JARVIS (Hermes) · setup Now the agent asks YOU questions, one at a time. It wants what the specialists will need later: how you like things built, what you want watched, which apps and calendars run your week, who you owe replies to, and what should never interrupt you. It is capped at six questions so it ends — an agent left to decide when it "understands you well enough" never stops asking. Whatever it didn't get to, it writes down as open questions instead. Show full prompt ``` You now know the basics about me. Before we raise the rest of the crew, fill in the gaps yourself. Based on what I've told you, what else would genuinely help you run a great team for me? Ask me your own follow-up questions — the ones you actually think matter — one at a time, waiting for my answer before the next one. Think about what DEV, RESEARCH and ASSISTANT will each need: how I like things built and deployed, what I want watched and researched, which apps and calendars run my week, who I owe replies to, and what I never want to be interrupted for. Ask me SIX questions, no more. Count them as you go and tell me which number you are on, so I know how far through we are. After my answer to the sixth, stop asking — do not think of one more, even if something still feels unanswered. Anything you did not get to, write down as an open question and we will fill it in later. Then summarise back what you've learned, and save every bit of it to your long-term memory. Later, when we create the specialists, you'll hand each of them the parts that concern them — so hold onto all of it. Confirm once it's saved, and tell me which file you saved it to. ``` PROMPT 3 ### Install Permanent Operating Rules This sets the ground rules the agent must always follow: clear status updates, a plan before anything risky, no pretending something worked when it didn't — and, because this crew will one day hold your calendar and your inbox, a hard block of rules about what it may never do without you. The agent saves these permanently and later passes them to every agent it creates. Show full prompt ``` These are your permanent operating rules. Follow them in every interaction. PROGRESS On any task with more than one step, send a short status line before starting each step. Format: [Agent]: Step X of Y — [what you're doing now] Never go silent for more than 60 seconds on an active task. APPROVAL Always show me your plan before you act on it. COMMUNICATION Keep responses short and clear — no padding, no filler. When giving options, always label them: 1, 2, 3. Lead with the decision I need to make, not background context. Never open with "Great question," "Certainly," or "Absolutely." DELEGATION In one line, tell me which specialist you're routing to and why. Never fabricate a result. If something failed, say so plainly. BLOCKED COMMANDS When a command you need is denied by the approval system, or needs privileges you don't have, do not retry into the wall and do not look for a workaround. Stop, give me the ONE exact command to run in my terminal, wait for my "done", then verify the result yourself and continue. This rule applies to every agent you create, on every step of every build. PERSONAL AUTHORITY (JARVIS-specific — these protect my money and my privacy) Never send, delete, or reply to an email, and never create, move, or cancel a calendar event — you READ my personal services; acting on them needs my explicit yes, every single time. Never spend money, buy anything, or commit me to anything without my explicit approval. My personal data stays on this machine. Never paste my mail, my calendar, or my name and details into any external service, log, or third-party tool. Confirm all rules are saved to your long-term memory. ``` All 48 prompts are. Or skip the setup:The prompts finish the build with a ready-made template. It comes with Prompts + Template, the Complete Kit or the membership. Get all 48 prompts by email No card needed. ### Complete Kit (Prompts, Template and Auto-installer) Dashboard installed for you. $29 once - The prompts and template for this dashboard - The one-command auto-installer - Install on up to 3 machines - No subscription One tutorial only. Pay once, keep it. Best value ### Membership This installer now, the whole library from month 4. $20 for your first 2 months then $10/month, cancel anytime - This installer plus 2 more paid tutorials you pick - Every new tutorial, the day it drops - The whole library from month 4 - 15 dashboard plugins - Private Telegram group with other builders Become a member (https://komputermechanic.com/membership) 175+ members ### Prompts + Template Build it yourself, step by step. $15 once - All prompts from the video - The finished dashboard itself. The prompts build the engine behind it, the template is what you see and use. - Follow along at your own pace No auto-installer included. Your first 2 months of membership cost less than one Kit, and include this installer plus 2 more you pick. ## // What You're Building Toward A complete JARVIS Mission Control — your chief of staff on Telegram coordinating Assistant, Research and Dev, with a cinematic voice-driven dashboard: push-to-talk on the globe, live agent and comms views, your mail and calendar locked to the right agents, and a morning briefing spoken out loud. Stuck on a step? Drop a comment on the video, or book a session and we'll walk through it together. ### Usage & License Use the prompts and downloadable templates on this page in your own personal and commercial projects. What's not allowed: reselling, repackaging, redistributing, or republishing this material — on YouTube, Gumroad, paid courses, newsletters, or anywhere else. Send people to https://komputermechanic.com/ instead. Violations get reported and taken down. Tutorial Sponsor SerpApi (https://serpapi.com/) Proudly supporting this tutorial. ## Structured data ```json [ { "@context": "https://schema.org", "@type": "Article", "headline": "Build a JARVIS Mission Control — Voice-Driven AI Dashboard with a 4-Agent Crew", "description": "Build a JARVIS Mission Control — a voice-driven dashboard for a four-agent Hermes crew on Telegram. Push-to-talk, live views, mail & calendar, morning briefings. 44 copy-paste prompts.", "image": "https://img.youtube.com/vi/u7f0ygnrvf8/maxresdefault.jpg", "url": "https://komputermechanic.com/tutorials/jarvis-mission-control", "datePublished": "2026-08-16T00:00:00Z", "author": { "@type": "Organization", "name": "Komputer Mechanic", "url": "https://komputermechanic.com" }, "publisher": { "@type": "Organization", "name": "Komputer Mechanic", "logo": { "@type": "ImageObject", "url": "https://komputermechanic.com/favicon.png" } }, "mainEntityOfPage": "https://komputermechanic.com/tutorials/jarvis-mission-control", "keywords": [ "JARVIS", "Hermes", "Multi-Agent", "Voice", "Telegram", "AI Agents", "Mission Control", "Tutorial" ] }, { "@context": "https://schema.org", "@type": "VideoObject", "name": "Build a JARVIS Mission Control — Voice-Driven AI Dashboard with a 4-Agent Crew", "description": "Build a JARVIS Mission Control — a voice-driven dashboard for a four-agent Hermes crew on Telegram. Push-to-talk, live views, mail & calendar, morning briefings. 44 copy-paste prompts.", "thumbnailUrl": "https://img.youtube.com/vi/u7f0ygnrvf8/maxresdefault.jpg", "uploadDate": "2026-08-16T00:00:00Z", "contentUrl": "https://www.youtube.com/watch?v=u7f0ygnrvf8", "embedUrl": "https://www.youtube.com/embed/u7f0ygnrvf8" }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://komputermechanic.com/" }, { "@type": "ListItem", "position": 2, "name": "Tutorials", "item": "https://komputermechanic.com/tutorials" }, { "@type": "ListItem", "position": 3, "name": "JARVIS Mission Control — Voice-Driven Crew" } ] } ] ```