Native APIs and CLIs
Use the local endOS command-line tools and HTTP APIs for scripts, automation, and debugging inside the desktop container.
Inside your endOS desktop container, some of the same capabilities used by the agent are available through local command-line interfaces and HTTP APIs. These native surfaces are intended for scripts, custom automation, and debugging.
Available surfaces
| Surface | Intended user | Purpose |
|---|---|---|
| Agent tools | Agent runtime | High-level automation during a run. See Tools. |
endos-* CLIs | Shell sessions inside the container | Stable wrappers around control-plane route families. |
Local /api/* HTTP routes | Integrations and generated code | Direct access to route families. |
For code running inside the container, use the container's local base URL and control-plane credentials. Do not route in-container scripts through external web or mobile proxy URLs.
CLI families
| CLI | Capability |
|---|---|
endos-terminal | Terminal execution and process control |
endos-chrome | Chrome tabs, pages, and elements |
endos-apps | App windows and screenshots |
endos-files | File reading, writing, moving, and deletion |
endos-settings | Settings and presets |
endos-mcp | MCP server status and RPC |
endos-email | Instance email inbox operations |
Local API families
The local API documentation mirrors these route families:
- Terminal
- Chrome
- Apps
- Files
- Settings
- MCP
Use the local route reference shipped in the container for each family's available endpoints and parameters.
Paths and user identity
Each desktop container represents one human user. When writing a script:
- Prefer paths relative to
$HOME, Team Drive, or Shared views unless a route specifically requires an absolute path. - Read MCP configuration from
~/.endos/mcp.json. See MCP. - Find task definitions under
~/.endos/tasks. See Tasks.
Full command and route reference
Flag-level CLI documentation and route-level API documentation ship inside the desktop container at:
~/.endos/docs/README.mdUse that local reference for exhaustive command flags, routes, and parameters.