Integrations
Rho ships host and shell integrations in the binary. You do not install a plugin store or run init hooks for the pieces below.
| Integration | Role | Page |
|---|---|---|
| Herdr | Agent state, session restore, host image paste under a Herdr workspace | Herdr |
| RTK | Rewrites agent shell commands when the rtk binary is on PATH | RTK |
| MCP | Native stdio and Streamable HTTP tools | Model Context Protocol |
| OpenAPI | Read-only REST tools generated from an OpenAPI spec | OpenAPI |
| ACP | Run Rho in Zed, T3 Code, and other editor hosts | Agent Client Protocol |
| Agent Plugins | Local packages installed by the user; Rho has no plugin store or remote registry | Agent Plugins |
| Grok Bot | Drive Rho sessions on your machines from a Grok Bot, with webhook updates | Grok Bot |
All stay optional. Outside Herdr, Rho skips host reporting. Without RTK, shell tools run commands unchanged. MCP stays inert until you add an enabled server under [mcp.servers] or a plugin package provides one. OpenAPI stays inert until you add a source under [openapi] or a trusted project declares one in .rho/openapi.toml. Agent Plugins load only from the explicit plugin roots. Disabled packages stay visible in rho plugins list but do not contribute components.
Check setup with /doctor. Inspect MCP with /mcp or rho mcp list. Manage packages with rho plugins.
Community
Products that ship their own Rho adapters are listed on community integrations. Rho does not maintain those adapters.