Published on May 01 2026

Agent-native rstream

Written by uartnet

@uartnet

rstream now exposes the product through agent-readable discovery, authentication, API, and workflow contracts.

This means an agent can start from the public site, discover the API catalog, learn how OAuth authentication works, fetch hosted and engine OpenAPI contracts, load rstream task skills, then act against the product with user-approved access. The intended path covers practical workflows such as selecting or creating a project, configuring the CLI, opening a published HTTP tunnel, setting up WebTTY, reading live engine inventory, and diagnosing setup failures.

The discovery layer is published through standard web entrypoints. The homepage advertises useful resources with Link response headers. /.well-known/api-catalog points to the hosted OpenAPI contract, engine OpenAPI contract, API documentation, and status endpoint. OAuth metadata is available through /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. Agent Skills are indexed at /.well-known/agent-skills/index.json, and the MCP Server Card is available at /.well-known/mcp/server-card.json.

The API contracts now separate hosted control-plane operations from engine data-plane operations. /api/openapi.json describes automation-facing hosted APIs, including project creation and project resolution. /api/engine/openapi.json describes the engine endpoints for clients, tunnels, SSE, and WebSocket state. Both contracts expose rstream permission metadata so agents can choose practical scope bundles instead of guessing from endpoint names.

The CLI also gained more automation-friendly output paths and a structured diagnostic command. rstream login -o json, rstream project use -o json, context commands, list commands, events, and forward flows can now be consumed more reliably by agents and CI. rstream doctor -o json, available in rstream CLI 1.14.0 and later, provides a structured readiness check after setup changes or during troubleshooting without printing token values.

For the complete model, see Agent Native, APIs, and CLI Workflow.