Command Execution
Execute one-off commands, retrieve stdout/stderr, and stream output as it is produced. See Command Execution.
Hoody Terminal
Section titled “Hoody Terminal”The Hoody Terminal service provides programmatic access to command execution, interactive sessions, system monitoring, and terminal automation inside containerized environments. Use these endpoints when you need to run shell commands, drive TUI applications, inspect resource usage, or stream session I/O over WebSockets from your own tooling.
The service is exposed through client.terminal.* in the Hoody SDK and over HTTPS at the container-scoped subdomain. Each container runs an isolated Terminal instance, and all operations are scoped to that container’s session boundary.
Available Endpoints
Section titled “Available Endpoints”Session Management
List, inspect, connect to, and manage interactive sessions. Stream session I/O over WebSockets. See Session Management.
Web UI & API Access
Access the web-based terminal interface and the in-browser API documentation surface. See Web UI & API Access.
System Monitoring
Query CPU, memory, disk, and process information, and inspect listening network ports. See System Monitoring.
Terminal Automation
Drive TUI applications: capture the screen, search the buffer, send keys, paste text, and wait for conditions. See Terminal Automation.
File Drag-and-Drop
Stage files into a session and inject them as a drag-and-drop frame. See File Drag-and-Drop.
Choosing the Right Endpoint
Section titled “Choosing the Right Endpoint”Authentication
Section titled “Authentication”All Terminal endpoints require a valid Hoody API token in the Authorization header using the Bearer scheme:
Authorization: Bearer <token>When using the SDK, authentication is handled automatically by the client instance.