# The Vibe **Page:** vision/the-vibe [Download Raw Markdown](./vision/the-vibe.md) --- # The Vibe **Your laptop is a viewport. Your server is the computer.** Every process you run — terminals, GUIs, databases, AI agents, cron jobs, file browsers, code editors — gets an HTTPS URL the moment it starts. No certificates. No ports. No reverse proxies. HTTP/2 + HTTP/3, automatically, forever. Share the URL and someone else is looking at it. Embed it in an iframe and it's part of a dashboard. Call it from `curl` and it's an API. That's the whole model. This page is the full picture. What Hoody is, what it enables, and why the architecture makes everything else feel like duct tape. --- ## The Primitive: URLs ``` https://{projectId}-{containerId}-terminal-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-display-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-sqlite-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-workspaces-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-exec-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-code-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-files.{node}.containers.hoody.icu https://{projectId}-{containerId}-browser-1.{node}.containers.hoody.icu https://{projectId}-{containerId}-pipe-1.{node}.containers.hoody.icu ``` 18 services per container. Unlimited instances per service. Unlimited containers per server. Every combination is a URL. Run a process → it gets a URL. Share the URL → instant collaboration. Embed the URL → instant integration. Call the URL → instant automation. One primitive. No special protocols. No SDKs required. HTTP in, HTTP out. --- ## Display: GUIs as URLs Every GUI application running in your container — Firefox, Blender, a desktop environment, an Electron app — streams as a live, interactive URL. Not a screenshot. Not a recording. The real thing, in real time. ``` display-1 → Your React dev server display-2 → Blender rendering on 128GB RAM display-3 → Full Linux desktop ``` Multiple displays per container. Each one isolated. Each one embeddable. Cast it to a TV, embed it in Notion, show it to a client — same URL, works everywhere. Your phone becomes a viewport into a render farm. A Raspberry Pi kiosk becomes a production dashboard by loading one URL. Because displays are isolated, you run conflicting environments side by side. Two app versions. Staging and production. Linux and Windows. Different worlds, same browser tab, zero interference. --- ## Pipe: Data Streams Over HTTP Named pipes, but over the internet. **Share your device screen as an HTTP link.** Your laptop screen. Phone camera. A file transfer. Live audio. Any data, over HTTP. One sender fans out to up to 256 receivers, and progress watchers can spectate the transfer without consuming a receiver slot. ``` You (sender) → https://{project}-{container}-pipe-1.{server}.containers.hoody.icu/{'{path}'} → Anyone (receivers) ``` Debugging at 3am? Pipe your screen. Your teammate opens the URL from their phone. They see what you see in real time, type in a shared terminal (also a URL), and you fix it together. Nobody installed anything. Building a mobile app? Pipe your phone screen to a URL. Your designer watches every tap, every animation, every transition on their monitor. No screen recording. Live HTTP stream. --- ## AI Is a First-Class Citizen Everything is HTTP. AI agents make HTTP requests. The math checks out. `GET /terminal/1/output`. `GET /display/1/screenshot`. `POST /sqlite/1/query`. `GET /files/1/list`. `GET /browser/1/status`. The agent uses the exact same interface you do. No adapters. No "AI toolkit." No special permissions. HTTP in, HTTP out. What this means in practice: - The agent watches your file changes and suggests refactors based on your codebase patterns - It monitors your running app via the display URL for visual regressions - It reads terminal output, queries logs, checks database state — all concurrently - It spawns new containers, assigns tasks to other agents, collects results - It fixes a test failure at 3am, pushes the commit, and sends you the diff URL over breakfast The agent doesn't live in a chatbox. It lives in the same infrastructure you do. Same HTTP, same URLs, same capabilities. The boundary between "AI tool" and "computing environment" doesn't exist because there was never a real boundary — just a protocol. --- ## 75+ AI Providers. Zero Lock-In. Anthropic. OpenAI. Google. Mistral. Groq. Ollama. Any OpenAI-compatible endpoint. Custom inference servers. 75+ providers out of the box. Switch models mid-conversation. A/B test providers across containers. Route secrets through environment variables. Today Claude, tomorrow GPT-6, next week a fine-tuned Llama on your own hardware. Config change, not migration. The AI layer is a pluggable socket. --- ## `@hoody.com` — The SSH of the AI Era `ssh hoody.com` proved universal access for humans. One address. Any terminal. Full environment. `@hoody.com` does the same for AI. Give any AI agent — ChatGPT, Claude, Cline, Codex, Roo Code — the address `@hoody.com`. It fetches a **Skill**: a structured capability definition mapping your entire infrastructure to HTTP endpoints. Terminal commands. File operations. Database queries. Deployments. Sub-agent orchestration. The agent doesn't need an MCP server, a plugin, or an SDK. It visits a URL and learns the skill. HTTP teaching HTTP. Any workflow can be wrapped into a single **hoody-curl** GET URL. A multi-step deployment. A provisioning sequence. A test-and-deploy pipeline. Paste it in a chatbot, embed it in Slack, put it in a QR code. The external AI triggers sub-agents inside your infrastructure, which trigger more sub-agents, which report back — all remotely, all over HTTP. ``` ssh hoody.com → any human, any terminal, full access @hoody.com → any AI, any platform, full access ``` Same principle. Same portability. Different era. --- ## Ctrl+Shift+K — Launch Anything Command palette backed by frecency ranking. Type what you want. "Install Jupyter" → provisioned, running in a display, streaming to a URL. "PostgreSQL database" → endpoint ready. No terminal touched. "Deploy my React app" → built, tested, deployed, proxy alias configured. URL delivered. "Run Blender with my project" → launched in a container display. URL appears. Not a chatbot. A launch mechanism for an entire computing environment where every process becomes a URL the moment it starts. --- ## Notifications: The Connective Tissue Your container sends a notification. It goes everywhere — phone, smartwatch, browser, smart glasses, any device with a push subscription. Your AI agent finishes a 45-minute build. Your watch taps you: "Build complete. 3 warnings. Preview: [URL]." You tap. You see the live app. You reply "deploy to prod." Done. Production alert at 2am. Phone vibrates. You tap the notification → terminal URL opens → you see the error → three commands → back to sleep. No laptop. No SSH. When your environment runs 24/7, notifications are how it reaches you. Events become notifications. Notifications carry URLs. URLs lead back to your infrastructure. One tap from "something happened" to "I'm looking at it." --- ## Hoody OS: The Operating System as a URL A floating-window web OS running on servers you own: - **Hoody Home** — Dashboard, project launcher - **Hoody Console** — Server management, container administration - **Hoody Workspaces** — Draggable windows: terminals, editors, file browsers, AI agents, displays, databases Every window is an iframe to a container service URL. The terminal window loads the terminal URL. The editor loads the code URL. Hoody OS is pure composition — URLs arranged in floating windows. We built the entire OS in under 5 days because of this. When everything is embeddable, an operating system is just a window manager. **Hoody OS itself runs on a Hoody container.** The OS managing your containers is a container. Embeddable. Shareable. Multiplayer. You can iframe the OS inside another OS. ```bash ssh hoody.com ``` Full Hoody OS in your terminal. A complete terminal-based browser rendering the same floating-window interface as a TUI. No username. No password. Login screen, then your full environment. From a Raspberry Pi. From a phone terminal app. If it holds an SSH connection, it runs Hoody OS. --- ## Device Independence Is a Solved Problem Your computing environment is already online. Not synced. Not mirrored. The real thing, running on your server 24/7. Open a browser anywhere → full environment. `ssh hoody.com` from any terminal → full environment. Your laptop dies → buy any device, log in, everything is there. Not "I can access my files from my phone." Your entire computing life — every process, every AI conversation, every database, every deployment — already exists at URLs, already running. The question "did you bring your laptop?" is meaningless. You left your computing environment running at a URL. You just need anything with a browser to look at it. --- ## Bare Metal. Your Server. Your Privacy. Not a shared VM. Not multi-tenant infrastructure. **Physical bare metal servers from the Hoody marketplace.** Your hardware. Nobody else's containers, workloads, or data on it. The hypervisor isn't shared. The host OS isn't shared. In the AI era — when agents write and execute code you haven't fully reviewed — isolation isn't optional. Each project, each experiment, each AI task runs in its own container on hardware you control. One compromised environment doesn't touch the others. Your data sits on a physical disk in a specific rack. Not "somewhere in us-east-1." You still get every convenience — automatic HTTPS, HTTP/2, HTTP/3, instant access from any device — but the hardware is yours and the isolation is real. --- ## Economics: Infinite Containers, One Server The VPS model charges per isolated server. Dev, staging, production? $120/month for three boxes sitting idle 90% of the time. Hoody: one bare metal server, infinite containers. Dev, staging, production, experiments, AI playgrounds, demo environments — all from one machine. The cost of experimentation drops to zero. The cost of spinning up a new project drops to zero. --- ## The Vibe No installation. No configuration. No sync. No "works on my machine." No lost work. No device lock-in. No protocol mismatches. No certificate headaches. No deployment rituals. URLs. To everything. From anywhere. On anything. Your server runs. Your containers run. Your AI agents run. 24/7. When you want to look, from any device, you open a URL and you're there. You describe what you want. It's running before you finish describing it. You share a link. Someone else is looking at it. You close your device. It keeps running. > **Everything you need. Nothing installed.** > **From anywhere. On anything.** > **Your server. Your privacy. Your URLs.** **Next:** [Understanding Hoody →](/vision/obsolescence/) | [The HTTP Revolution →](/vision/http-revolution/) | [The Embeddability Revolution →](/vision/embeddability/)