# Multiplayer by Default **Page:** vision/multiplayer [Download Raw Markdown](./vision/multiplayer.md) --- # Multiplayer by Default **Collaboration as you know it is already obsolete.** Screen sharing is taking turns. Video calls are "can you see my screen?" Pair programming is watching someone else type. Customer support is describing problems instead of solving them. **Hoody changes everything: Every computer, every program, every environment is multiplayer by default.** Not web-based collaboration tools. Not screen sharing. **Actual simultaneous control of the same programs.** --- ## The Core Truth **Everything is a URL. Every URL is collaborative.** When you spawn a container, anyone with the URL can join. Everyone typing in the same terminals. Everyone controlling the same browser. Shared displays with everyone seeing the same screen. Collaborative file editing in real-time. **It's like Google Docs, but for entire computers.** ``` https://abc123-def456-terminal-1.node-us.containers.hoody.icu https://abc123-def456-display-1.node-us.containers.hoody.icu https://abc123-def456-files.node-us.containers.hoody.icu ``` One URL per service. Share the URL = instant collaboration. **That's it.** **Why this works:** Because everything is HTTP with WebSocket support, multiplayer isn't a feature—it's the foundation. Multiple connections to the same URL. Shared state synchronized in real-time. Zero setup required. --- ## The 30-Second Bug Fix **Traditional collaboration:** 1. "Can you help me with a bug?" 2. Schedule screen share call 3. "Can you see my screen?" 4. "Wait, let me share my terminal" 5. "No, the other terminal" 6. Senior dev watches, describes what to type 7. Junior dev types, makes mistakes 8. 20 minutes later, maybe fixed **Hoody collaboration:** 1. Junior dev: "Bug in container abc123-def456" 2. Senior dev opens terminal URL 3. **Both see the exact same terminal** 4. **Both type simultaneously** in the same session 5. Bug fixed in 30 seconds No screen share setup. No "can you see this?". No taking turns. **Just instant collaboration.** --- ## Shared State, Not Screen Sharing **The breakthrough:** You're not sharing your screen. You're sharing the **actual environment**. ### Social Media Team Example Traditional workflow: - 5 marketers managing 20 brand accounts - Each logs into accounts on their own computer - "Whose turn to post?" - "Did you log out of the Instagram?" - Credentials shared in password managers - Someone forgets which account they're on **Hoody workflow:** - ONE computer with 20 browser instances managing 20 accounts - All 5 marketers open the computer's display URL - Everyone sees all 20 browsers, all logged-in sessions - Someone drafts a tweet in browser tab 1 - Another person reviews Instagram stories in browser tab 5 - Third person posts to LinkedIn in browser tab 12 - **All simultaneously working on different tabs. Shared state. Zero credential sharing.** No more "whose session is this?". It's **our** session. --- ## Any Program, Multiplayer, On Any Device Here's the revolution: **Programs that were never designed for collaboration become collaborative. And you can access them from anywhere.** - **VS Code never built for collaboration?** Now it is. - **Custom internal tools?** Multiplayer. - **Legacy desktop applications?** Multiplayer. - **Terminal sessions?** Multiplayer with multiple people typing. - **File editing?** Multiplayer like Google Docs. - **20 browsers with logged-in accounts?** Shared state. **Because it's not about the app—it's about the environment being web-native.** **Your phone can run VS Code.** Not a mobile version. The actual desktop application. Because Hoody displays are URLs: - **Phone** → Open URL → Full VS Code - **Tablet** → Open URL → LibreOffice - **TV** → Open URL → Your entire dev environment - **Smart glasses** → Open URL → Terminals and dashboards - **Any browser anywhere** → Full desktop applications The device doesn't matter. **The URL is the computer.** And because it's multiplayer by default, your team can join from their phones, tablets, laptops—all controlling the same VS Code, the same browser, the same environment. --- ## AI + Humans Together **This is the future of human-AI collaboration.** You're coding in a terminal: - **You type** commands - **AI agent joins the same URL** and types too - **You both work simultaneously** in the same environment You're debugging: - You check logs in terminal 1 - AI reads stack traces in terminal 2 - Both manipulating the same container - Seeing each other's actions in real-time **Not AI suggesting code you copy-paste. AI and human as peers, coding together in shared state.** Multiple AI agents can join too: - Agent 1 writing tests in terminal 1 - Agent 2 refactoring code in terminal 2 - Agent 3 updating docs in terminal 3 - You orchestrating across all terminals **All in the same environment. All visible to each other. This is collaborative intelligence.** --- ## Always Collaborative → Add Permissions When Ready **The radical philosophy:** Containers start collaborative. You **add** restrictions when you need them. ### Default State (Perfect for Development) ``` https://abc123-def456-display-1.node-us.containers.hoody.icu ``` - ✅ Anyone with URL can join - ✅ Shared control, everyone can type - ✅ Perfect for team collaboration - ✅ Instant sharing (just send URL) **Cryptographic URLs** (24-char hex IDs) make them unguessable. Share intentionally, not accidentally. ### Production State (When You Need Control) Add [permissions](/foundation/proxy/permissions/) when ready: - **IP restrictions** - Only your team's office - **Basic authentication** - Username/password via URL - **Bearer tokens** - API-style access control - **2FA** - Two-factor authentication - **Read-only mode** - Viewers can't control **The difference:** You **choose** when to restrict. Default is collaborative. Lock down later. **Best practice:** Keep development environments open for collaboration. Add permissions when moving to staging/production. Use [Realms](/api/realms/) to isolate production from collaborative environments. --- ## From "My Computer" to "Our Computers" **The psychological shift is profound.** You don't think: "Let me share my screen so you can watch" You think: "Here's the URL, we're already there" You don't say: "Wait until I'm done typing" You say: "Just start typing" (we're both here) You don't ask: "Can you see this?" You know: **We're looking at the same thing** **Computing becomes inherently collaborative.** Not through bolted-on features. Through fundamental architecture. --- ## Why This Changes Everything **Traditional computing:** Each person on their own island. Collaboration requires bridges, boats, swimming. **Hoody computing:** Everyone in the same space. URLs are portals. Walk through and you're there. **This enables:** - **Remote work** that actually feels collaborative - **Pair programming** that doesn't require being in the same room - **Teaching** that's genuinely interactive - **Customer support** that solves problems in seconds - **AI + human teams** working as peers - **Desktop applications on any device** (because browsers are universal) - **Shared accounts and sessions** (marketing teams, operations teams) **And it's not coming.** It's here. Default. Built-in. --- > **Collaboration isn't a feature anymore.** > **It's the foundation.** > **Every computer. Every program. Every environment.** > **Multiplayer by default.** **Welcome to collaborative computing.** **Next:** [Security Model →](/vision/security/)