Skip to content

Beta: these docs are still being updated. The next full update is on 19 November at 8 PM UTC. Docs in beta. Full update 19 Nov, 8 PM UTC.

Hoody.com

Hoody gives you Linux computers in the cloud. Everything that runs on one has its own HTTPS link: a terminal, a file, a database, a desktop, a website you start on a port.

A free account comes with a free server: 2 cores, 3 GB RAM and 20 GB disk, shared by up to 3 computers. Your first computer is already on it, with the 20 HTTP services of the Hoody Kit. One of them is the Hoody Agent, which runs on Hoody AI’s free tier. The server does not expire, and computers are not charged. Limits can change: Pricing has the current ones.

On this page you sign in, open that computer’s desktop in a browser tab and put a website online. Then you script it: run a command, write a file, query a database and give the Hoody Agent a task. Each step has a tab for the CLI, the TypeScript SDK and plain curl, and most have a link you can open.

Every call is an ordinary HTTPS request. There is nothing to install on the computer, and no deployment step, certificate, port or proxy to configure. An iframe, a webhook or an AI agent calls the same URLs the same way. The CLI and HTTP tabs use jq; the SDK tabs need Node.js 20.19 or later (everything you need).

Pick the fastest way for where you are. Each one creates the same account.

FromDo this
A terminal, nothing installedRun ssh hoody.com. After the terms notice, its welcome menu creates an account or signs you in.
A browserSign up at hoody.com/signup, then open the Hub at hub.hoody.com.
Node.jsRun npx hoody-sdk@1.0.1 signup. It asks for an email and a password, verifies the email and ends signed in.
An AI chatPaste @https://hoody.com Connect to Hoody. Your AI sends you a signup link and, once you approve its sign-in, works on your account for you (Connect Your AI to Hoody).

Verify your email before signing in. A verified new account comes with a free server and a first computer (what an account needs). To follow the next steps, sign in from the interface you want to use:

Terminal window
# Install the CLI (it ships inside the hoody-sdk package)...
npm install -g hoody-sdk@1.0.1
# ...or skip the install entirely: npx hoody-sdk@1.0.1 <command>
# Interactive sign-in (`hoody signup` if you don't have an account yet)
hoody login
# If it offers to open the Hub, press n to stay in your shell

Standalone binaries for Linux, macOS and Windows need no Node.js: Install.

Your account holds servers, a project organizes computers, and a computer is a full Linux computer running Debian 13 with systemd. The free server already holds one computer with the Hoody Kit, in a project named Default. List your computers and keep three values of a running one: its ID, its project ID and its server_name.

Terminal window
# Take a running computer (-o json prints the response data itself, no envelope to unwrap)
COMPUTER=$(hoody computers list -o json \
| jq '[.computers[] | select(.status == "running")][0]')
COMPUTER_ID=$(echo "$COMPUTER" | jq -r '.id')
PROJECT_ID=$(echo "$COMPUTER" | jq -r '.project_id')
SERVER_NAME=$(echo "$COMPUTER" | jq -r '.server_name')
# Make it the CLI's default computer, for commands without -c
hoody config set computer "$COMPUTER_ID"

A computer on a new account can still be setting up: if the list has no running one, run the step again in a moment (Troubleshooting).

Once the computer is running, its Kit services answer at stable HTTPS URLs. A service may still be starting; retry its request if it is temporarily unavailable.

https://{projectId}-{computerId}-{service}[-{instance}].{server}.computers.hoody.com

{server} is the computer’s server_name. The Hoody Kit lists every service on that pattern: two use short URL slugs (notifications → n, proxyLogs → logs), and http-{port} covers anything you start on a port. The next steps use seven of them, counting the curl-1 service that sends each link.

Step 3: Open a desktop and a terminal in the browser

Section titled “Step 3: Open a desktop and a terminal in the browser”

Kit services with a screen open as pages, with no client to install on the device you use. Paste either link into a browser, with your three values in place:

https://{projectId}-{computerId}-desktop-1.{server}.computers.hoody.com
https://{projectId}-{computerId}-terminal-1.{server}.computers.hoody.com

The first starts an Xfce desktop if none is running, then shows it once it is ready. The second is a shell in terminal 1, the same terminal that runs the command in Step 4.

In the Hub, open Computers and select your computer. On its Overview tab, under Open on followed by your computer’s name, select the Desktop or Terminal tile. It opens in a new browser tab.

Terminal window
# Open the desktop in your browser (add --url to print the link instead)
hoody desktop open -c "$COMPUTER_ID"
# Open terminal 1 as a web terminal
hoody terminal open 1 -c "$COMPUTER_ID"

files-1 opens a file manager and code-1 opens VS Code the same way. Displays covers GUI programs and driving a desktop over HTTP, and Embed a Kit UI in your own page covers putting these pages in an iframe.

Start any HTTP server on a port inside the computer, and that port has its own HTTPS link: put http-{port} where the service label goes. This command writes a one-line page and serves it on port 3000. You can also type it into the web terminal from Step 3.

Terminal window
# Write a page and start a web server on port 3000 inside your computer
hoody terminal commands run -c "$COMPUTER_ID" --terminal-id 1 \
--command 'mkdir -p /home/user/site && echo "<h1>Hello from Hoody</h1>" > /home/user/site/index.html; nohup python3 -m http.server 3000 --directory /home/user/site >/tmp/site.log 2>&1 & sleep 1'
# It's already on the public internet, with HTTPS
curl "https://$PROJECT_ID-$COMPUTER_ID-http-3000.$SERVER_NAME.computers.hoody.com/"

Open the http-3000 link in a browser to see the page. Have your own servers listen on all addresses (0.0.0.0 or ::) (bind addresses). A proxy alias gives the port a hostname you choose or your own domain, Hoody Daemon starts the server and restarts it by your rules, and a script file becomes a live HTTP endpoint with no server in Your First API.

In the Hub, open Computers, select the computer and open its Run tab. Type the command into Command and press Run.

Terminal window
# Execute a shell command on your computer
hoody terminal commands run -c "$COMPUTER_ID" --ephemeral \
--command "grep PRETTY_NAME /etc/os-release"

The CLI and HTTP answers are the finished result: stdout, exit_code and a command_id that fetches the same result again (what each step returns). The SDK helper returns stdout, stderr, exitCode, timedOut, duration and commandId. It runs the command without a terminal session, so its result cannot be fetched again. For an interactive shell from your own terminal, run hoody shell "$COMPUTER_ID".

Replace the page from Step 4 through the Files service, then read it back. Reload your http-3000 link and the site has changed.

In the Hub, open Files, pick your computer and browse to /home/user/site. On index.html, Open in editor opens the computer’s editor, where you change and save the file, and Preview shows it.

Terminal window
# Write a file: the body comes from stdin
echo '<h1>Changed over HTTP</h1>' \
| hoody files upload /home/user/site/index.html -c "$COMPUTER_ID"
# Read a file from your computer (-o raw prints it verbatim)
hoody files get -c "$COMPUTER_ID" /home/user/site/index.html -o raw

Every Kit computer ships a SQLite service; there is no database server to provision and no connection string to configure.

In the Hub, open Computers, select the computer and open its Connect tab. Open SQLite under Program links, create or open a database, then open Query, type the SQL and press Execute.

Terminal window
# Run a SQL transaction on the built-in SQLite
hoody db transactions run -c "$COMPUTER_ID" --db app --create-db-if-missing \
--transaction '[{"statement":"CREATE TABLE IF NOT EXISTS greetings (message TEXT)"},{"statement":"INSERT INTO greetings VALUES ('"'"'Hello, Hoody!'"'"')"},{"query":"SELECT * FROM greetings"}]' \
-o json

Hoody does not host the agent: your own computer serves it, so every Kit computer carries its own, directly at:

https://{projectId}-{computerId}-agent-1.{server}.computers.hoody.com

Open it in any browser, embed it in an iframe or share it with a teammate: a phone, a laptop, a TV and a tablet all reach the same environment and the same state. The agent that manages your computers itself runs in a computer.

Hoody also has a browser interface: sign in at hub.hoody.com and you land in the Hub. Press AI in its top bar to open the Agent panel, which chats with the Hoody Agent on the computer picked in the top bar. The Hub’s pages manage your computers, files, Bots and billing. In a terminal on Linux x86-64 or arm64, the standalone hoody binary or the npm package with Node 26 or later opens the same Hub with hoody hub (the Hub in your terminal).

The agent starts on Hoody AI’s free tier, with no model key to set up, and works on its own computer without signing in. Give it a task. This one rewrites the page from Step 4, so the result is on your http-3000 link when the turn ends.

In the Hub, pick the computer in the top bar, press AI and type the task into the Agent panel.

Terminal window
# --gate-policy auto_approve approves the agent's ordinary confirmations for this turn
hoody agent prompt "Rewrite /home/user/site/index.html as a landing page for a bakery." \
--gate-policy auto_approve -c "$COMPUTER_ID"

The CLI streams the reply. Over HTTP and in the SDK, a completed turn returns its status without reply text; the page itself is the result. A turn needing human input can instead return pending_gate and turn_id before it ends. To let the agent reach your account and your other computers, sign it in once. Agent covers sessions, models and your own provider accounts.

Computers have no per-unit cost. Once a server exists, you can create as many as its capacity and limits allow, including your project’s computer limit (max_computers). An experiment, an agent task or a customer can each get its own computer. This creates a second one next to your first, in the same project and on the same server.

In the Hub, open Computers and press Get a computer. Keep the suggested Name or type your own, pick the same Server and Project, and press Get computer. Under More options, Hoody kit is on by default.

Terminal window
# The server your first computer runs on
SERVER_ID=$(echo "$COMPUTER" | jq -r '.server_id')
# Spawn a second Kit computer in the same project
hoody computers create --project "$PROJECT_ID" --server-id "$SERVER_ID" \
--name "dev-box" --hoody-kit

The answer carries the new computer’s id and server_name. Wait until its status is running before you call its Kit services. Create a computer and wait for it has the whole script, from picking a server to the wait.

The free server is a shared machine to start on. When you need dedicated hardware, rent flat-rate bare metal from the marketplace: computers stay free; you pay for the machine.

Every way in reaches the same account and the same computers, so switching needs no migration. Ways to connect has the setup and the detail of each one.

FromUseStart with
A browserThe Hubhub.hoody.com
A terminal, nothing installedSSHssh hoody.com
A terminalThe Hoody CLInpm install -g hoody-sdk@1.0.1
TypeScript or JavaScriptThe Hoody SDKnpm install hoody-sdk@1.0.1
A static web pageThe browser buildOne script tag that exposes window.HoodySDK
Any languageHTTPA Bearer token on api.hoody.com, and the computer’s own URLs
ChatGPT, Claude, GeminiThe Hoody SkillPaste @https://hoody.com Connect to Hoody (Connect Your AI to Hoody)
A coding agentThe Hoody Skillnpx skills add (below)
Telegram, Slack or DiscordA BotChat apps for your Bot
Another AI app, or people you trustA Bot URLBot URLs

If you already work in a coding agent, install the Hoody Skill into it once and it knows the whole HTTP surface without being told each time:

Terminal window
# The skill itself; deeper docs are fetched on demand
npx skills add https://hoody.com/SKILLS/SKILL.md
# The same skill plus the whole corpus on disk, for offline use
npx skills add HoodyNetwork/hoody-sdk

Works with

  • Claude Code
  • Codex
  • Cursor
  • Cline
  • Any MCP-less agent

CLI runs on

  • macOS
  • Linux
  • Windows

The Skill teaches the agent the endpoints; it does not grant access. The agent signs you in through a browser link, or uses a token you give it.

Everything you need before you start, every placeholder, every way to connect, what each step returns, limits and troubleshooting: Quick Start reference.

The Getting started pages continue from here: Understanding computers, The Hoody Proxy and Your First API.

Explore the Kit

Every HTTP service built into a Kit computer, including the AI agent: browser, cron, notes, pipes, tunnels and more. The Hoody Kit →