# Hoody Website AI Review

Exported: 2026-06-18T06:57:19.268Z

## Summary

- Reviews: 5
- Findings: 4 high / 12 medium / 7 low

### Highest-risk pages

- (16) https://c25207b1d01f6070c09370dc-69a267f1d6a9761e35df0f49-http-3055.dusk-lion-2a3-sg.containers.hoody.icu/kit/terminal
- (15) https://hoody.com/
- (10) https://hoody.com/kit/terminal
- (2) https://hoody.com/agent

## Pages

### https://c25207b1d01f6070c09370dc-69a267f1d6a9761e35df0f49-http-3055.dusk-lion-2a3-sg.containers.hoody.icu/kit/terminal

#### claude-code / Claude Opus 4.8 — completed
- **[high] claim-mismatch** — Response samples use array brackets [ ] around object fields — invalid JSON, contradicts documented response schema
  - Evidence: > ["success":true,"stdout":"Hello from Hoody!\n","duration_ms":3]  (and) > [> "success": true,> "exit_code": 0,> "stdout": "24 passed, 0 failed",> "duration_ms": 12> ]
  - Docs: HTTP Shell Execution — documented Response is a JSON object: { "success": true, "command_id": ..., "terminal_id": ..., "status": ..., "exit_code": 0, "stdout": ..., "stderr": "", "duration_ms": 5 }
  - Fix: Replace the surrounding [ ] with { } in both response blocks so each is a valid JSON object, matching the documented response shape in HOODY_DOCS_CONTEXT.
- **[high] other** — Four different terminal hostname patterns appear across the page's code samples
  - Evidence: https://your-terminal.hoody.com/token | https://proj-dev-terminal-1.server.containers.hoody.com | terminal.hoody.com/api/v1/terminal/execute | https://proj-dev-terminal-1.hoody.com/api/v1/terminal/execute
  - Docs: on-page self-check; canonical pattern in HOODY_DOCS_CONTEXT is https://$PROJECT-$CONTAINER-terminal-1.$SERVER.containers.hoody.icu (map .icu → .com per domain override)
  - Fix: Use one consistent hostname pattern across all samples. Do NOT standardize on one of the page's own strings — quote the canonical pattern documented in HOODY_DOCS_CONTEXT ({project}-{container}-terminal-1.{server}.containers.hoody.icu), substituting the production .com domain per the known override, rather than the placeholder-laden 'proj-dev'/'server' forms shown on the page.
- **[medium] claim-mismatch** — Page says '14 Kit services' but docs describe '18 HTTP Services'
  - Evidence: Terminal is one of 14 Kit services that ship with every Hoody container.
  - Docs: Docs section titled 'The 18 HTTP Services'
  - Fix: Reconcile the service count with the documented total ('The 18 HTTP Services' in HOODY_DOCS_CONTEXT); if 'Kit services' is a deliberately narrower set than 'HTTP services', clarify the distinction so the number is unambiguous.
- **[medium] claim-mismatch** — Session-management endpoint paths differ from the documented paths
  - Evidence: DELETE /api/v1/terminal/sessions/:id Terminate session ; POST /api/v1/terminal/sessions Create new session ; WS /api/v1/terminal/sessions/:id/ws Real-time stream
  - Docs: API Endpoints Summary: DELETE /api/v1/terminal/{terminal_id}; POST /api/v1/terminal/create; GET /api/v1/terminal/ws (WebSocket)
  - Fix: Align the session-management, create, and WebSocket endpoint paths with the values documented in HOODY_DOCS_CONTEXT (e.g. DELETE /api/v1/terminal/{terminal_id}, POST /api/v1/terminal/create, GET /api/v1/terminal/ws), or confirm with the API source which scheme is authoritative.
- **[medium] launch-content** — curl examples pass an unquoted JSON body to -d
  - Evidence: -d {"command":"echo Hello from Hoody!","wait":true}  (and)  curl -X POST terminal.hoody.com/api/v1/terminal/execute -d {"command":"ls -la /app"}
  - Docs: Docs curl example quotes the body: -d '{"command": "ls -la /app", "wait": true}'
  - Fix: Wrap the JSON body in single quotes, e.g. -d '{"command":"...","wait":true}', matching the quoted form used elsewhere on the page and in the docs.
- **[medium] needs-docs-context-check** — Listed endpoints GET /api/v1/system/env and GET /api/v1/system/info are not present in the supplied docs
  - Evidence: GET /api/v1/system/env Environment variables ; GET /api/v1/system/info System information
  - Docs: Supplied docs list system/resources, system/processes, system/process/signal, system/ports, system/daemon, system/displays — but no system/env or system/info
  - Fix: Verify GET /api/v1/system/env and GET /api/v1/system/info against the full API reference; if they don't exist, correct or remove them (and recheck the '6 endpoints' subtotal), otherwise confirm the docs excerpt is simply incomplete.
- **[low] terminology** — tmux listed among shells; docs treat tmux as a multiplexer/bridge, not a shell
  - Evidence: bash, zsh, fish, tmux, sh — switch shells via URL parameter.
  - Docs: Parameters: shell = bash, zsh, fish, sh, etc.; tmux appears separately as the 'tmux Bridge' feature
  - Fix: Drop tmux from the shell list (or clarify it as the separate tmux Bridge), and reconcile the '5 Shell Environments' count with the documented `shell` parameter values.
- **[low] needs-docs-context-check** — '50+ URL Parameters' vs docs '39 query parameters' for the web terminal UI
  - Evidence: 50+ URL Parameters
  - Docs: Web Interface: 'GET / — Browser terminal UI — 39 query parameters for customization'
  - Fix: Confirm the '50+' figure against the full parameter inventory; if it refers only to the web UI, align it with the documented count (39), otherwise clarify that it spans all endpoints.

### https://hoody.com/kit/terminal

#### claude-code / default — completed
- **[high] claim-mismatch** — Multiple code samples wrap JSON object fields in array brackets [ ] instead of braces { }
  - Evidence: -d '["command":"echo Hello from Hoody!","wait":true]'  ...  > ["success":true,"stdout":"Hello from Hoody!\n","duration_ms":3]
  - Docs: HTTP Shell Execution / API Endpoints Summary — request body and response are documented as JSON objects: {"command": "ls -la /app", "wait": true} and {"success": true, "exit_code": 0, ...}
  - Fix: Replace [ ] with { } in every request body and response so they are valid JSON objects, matching both the page's own correct sample (-d '{ "command": "ls -la /app", "wait": true }') and the documented schema in HOODY_DOCS_CONTEXT.
- **[medium] other** — Terminal hostname format is inconsistent across code examples
  - Evidence: https://your-terminal.hoody.com/token ... https://proj-dev-terminal-1.server.containers.hoody.com ... terminal.hoody.com/api/v1/terminal/execute ... https://proj-dev-terminal-1.hoody.com/api/v1/terminal/execute
  - Docs: on-page self-check (canonical pattern documented in HOODY_DOCS_CONTEXT: https://{project}-{container}-terminal-1.{server}.containers.hoody.icu)
  - Fix: Standardize every example on one host pattern. Use the canonical pattern documented in HOODY_DOCS_CONTEXT — {project}-{container}-terminal-1.{server}.containers.hoody.[domain] (mapping the documented .icu to the customer-facing .com) — rather than reusing the page's own ad-hoc strings ('your-terminal', 'proj-dev', bare 'terminal.hoody.com') as the example.
- **[medium] claim-mismatch** — Session-management endpoint paths differ from the documented API
  - Evidence: POST /api/v1/terminal/sessions Create new session ... DELETE /api/v1/terminal/sessions/:id Terminate session ... POST /api/v1/terminal/sessions/:id/write Write to session ... WS /api/v1/terminal/sessions/:id/ws Real-time stream
  - Docs: API Endpoints Summary — POST /api/v1/terminal/create (create), DELETE /api/v1/terminal/{terminal_id} (terminate), POST /api/v1/terminal/write (write), GET /api/v1/terminal/ws (WebSocket)
  - Fix: Reconcile the endpoint paths with HOODY_DOCS_CONTEXT (create=POST /api/v1/terminal/create, terminate=DELETE /api/v1/terminal/{terminal_id}, write=POST /api/v1/terminal/write, WebSocket=GET /api/v1/terminal/ws), or confirm the /sessions namespace is the current API and update the docs accordingly.
- **[medium] claim-mismatch** — '14 Kit services' contradicts the documented service count
  - Evidence: Terminal is one of 14 Kit services that ship with every Hoody container.
  - Docs: Docs section header 'The 18 HTTP Services' (the HTTP/kit services bundled in every container)
  - Fix: Reconcile the count with the documented set; use the number documented in HOODY_DOCS_CONTEXT ('The 18 HTTP Services') unless the kit lineup has officially changed.
- **[low] terminology** — tmux is listed as one of the five shell environments
  - Evidence: bash, zsh, fish, tmux, sh — switch shells via URL parameter.
  - Docs: Parameters — shell query param lists `bash`, `zsh`, `fish`, `sh`, etc.; tmux is documented separately as a multiplexer ('tmux Bridge')
  - Fix: Either drop tmux from the shell list (and re-derive the '5 Shell Environments' count) or verify against the documented `shell` parameter values before presenting tmux as a selectable shell.

### https://hoody.com/

#### claude-code / Claude Opus 4.8 — completed
- **[high] claim-mismatch** — Built-in service count is internally inconsistent (14 vs 19) and conflicts with docs (14)
  - Evidence: 14 services, auto-detected, auto-secured. ... [stat block] 19 Built-in services
  - Docs: Containers (concept) and 'Understanding Containers' both state '14 built-in HTTP services' / '14 HTTP services built in' (terminal, display, files, exec, sqlite, browser, agent, code, curl, notifications, daemons, cron, pipe, workspaces).
  - Fix: Reconcile to a single number. If only 14 services are documented, change '19 Built-in services' to 14 and align the Abstraction service list; if 19 is now correct, update the docs and the '14 services' hero line accordingly.
- **[medium] needs-docs-context-check** — Several listed services are not present in the supplied 14-service docs list
  - Evidence: Terminal ... Files ... Display ... SQLite ... Exec ... AI Proxy ... Agent ... Browser ... Code ... Daemon ... cURL ... Notifications ... Pipe ... Cron ... Watch ... Notes ... Run ... Workspaces ... Platform API
  - Docs: Docs enumerate exactly 14 services; 'AI Proxy', 'Watch', 'Notes', 'Run', and 'Platform API' do not appear in that list.
  - Fix: Confirm these services (AI Proxy, Watch, Notes, Run, Platform API) exist and update the docs to cover them, or remove them from the homepage if not yet shipped.
- **[medium] claim-mismatch** — Container URL domain on page (.containers.yourserver.hoody.com) differs from docs (.containers.hoody.run)
  - Evidence: https://proj-frontend-http-3000.containers.yourserver.hoody.com
  - Docs: Quick Start and Workspaces docs consistently use 'https://{projectId}-{containerId}-...{node}.containers.hoody.run' (e.g. terminal-1.containers.hoody.run).
  - Fix: Align the example URLs with the documented '.containers.hoody.run' scheme, or update the docs if the production domain has actually changed.
- **[medium] missing-docs-support** — Open-source / 'no telemetry' claims for Workspaces are not supported by the docs
  - Evidence: Hoody Workspaces is open source and runs on YOUR bare-metal machine. ... No telemetry. No trust required -- verify the code yourself.
  - Docs: Workspaces and 'Understanding Hoody' docs describe Workspaces' capabilities and ownership model but make no statement that it is open source or telemetry-free.
  - Fix: Add documented support (e.g. a repository link and license) for the open-source and no-telemetry claims, or soften/remove them if not substantiated.
- **[medium] missing-docs-support** — '300+ AI Models' is not supported by docs, which cite '75+ providers'
  - Evidence: 300+ AI ModelsClaude, GPT, Gemini, Groq, Mistral... Container-based auth.
  - Docs: 'The Vibe' doc states '75+ AI Providers. Zero Lock-In.' with no model count.
  - Fix: Either document the 300+ model figure or align the homepage with the documented '75+ providers' framing to avoid an unsupported number.
- **[medium] needs-docs-context-check** — Pricing tiers cannot be verified against supplied docs
  - Evidence: DEDICATED BARE METALFrom $29.90/mo ... FREE MACHINE$0 ... HOODY AIPay-as-you-go
  - Docs: No pricing information is present in the supplied HOODY_DOCS_CONTEXT.
  - Fix: Verify these prices against the current pricing source before launch; supply pricing docs for audit.
- **[low] needs-docs-context-check** — '$3.2M raised' funding claim has no docs support
  - Evidence: Since 2021 · From privacy to agentic infrastructure · $3.2M raised · Read our story
  - Docs: No funding or company-financial information appears in the supplied docs.
  - Fix: Confirm the $3.2M figure against an authoritative internal source and ensure it is current.
- **[low] missing-docs-support** — Telegram workspace-agent integration is not covered by supplied docs
  - Evidence: TelegramNEWChat with your workspace agent from Telegram. Manage sessions from your phone.
  - Docs: Supplied docs describe MCP, multiplayer, and mobile/SSH access but do not mention a Telegram integration.
  - Fix: Add Telegram integration to the docs, or confirm it is live before presenting it as a shipped feature.

### https://hoody.com/aup

#### claude-code / Claude Opus 4.8 — completed
- No findings.

### https://hoody.com/agent

#### claude-code / Claude Opus 4.8 — completed
- **[low] missing-docs-support** — Unsupported 'first infrastructure' superlative claim
  - Evidence: The first infrastructure where containers, terminals, displays, and AI agents share the same HTTP protocol.
  - Docs: Docs ('The 100x Foundation' / 'Deploying Autonomous AI Agents') describe Hoody as 'a new kind of cloud platform' and 'HTTP-native infrastructure' but make no first/only-in-market claim.
  - Fix: Drop 'The first' or qualify the claim (e.g. 'infrastructure where containers, terminals, displays, and AI agents share the same HTTP protocol') unless a defensible primacy claim can be documented.
- **[low] terminology** — 'Agent mode' label may be confused with the documented 'Hoody Agent' / 'hoody-agent' service
  - Evidence: Agent mode swaps the human-facing site for a surface designed for autonomous models — same content, machine-shaped.
  - Docs: Docs consistently use 'Hoody Agent' and the built-in 'hoody-agent' service for the autonomous agent capability, and 'mode' as an API task parameter (e.g. "mode": "code").
  - Fix: Consider a distinct name for the machine-readable site surface (e.g. 'Machine view' / 'Agent view') to avoid overlap with the 'Hoody Agent' service and the task 'mode' parameter.