Stage Chat and its connectors

Applies to Stage Chat 0.1.1. Sources checked on 9 October 2026.

Stage Chat defines a PHP interface for requesting one final answer. Each request supplies its own conversation context. Stage\Chat\Connector::complete(Request $request, ?Closure $cancelled = null) returns Stage\Chat\Response. The application owns retrieval, conversation state, authentication, and answer validation.

The package installs with composer require skyyware/stage-chat:^0.1.1. Installing the contract does not contact a provider or require a subscription. A provider answer needs a connector implementation and the credentials or other setup required by that service.

Request separates trusted application instructions from untrusted context and messages. Only user and assistant message roles exist. Messages form a nonempty list ending in a user message. Browser-supplied assistant history is also untrusted. Role separation is not an authorization system.

Limit incoming HTTP bytes before decoding JSON. Your application can set smaller limits and choose how much history to include in each request.

Response::$text contains the final answer. The contract does not promise streaming or structured JSON. A connector can request JSON, but the application must still validate its schema, facts, source IDs, and links.

Failure reports Unavailable, Timeout, Cancelled, or InvalidResponse without provider content. Invalid application inputs throw InvalidArgumentException. A cancellation closure returns true to ask the connector to stop waiting.

The package contains no storage, session IDs, tools, network client, retries, background jobs, tenant selection, or retrieval engine. It has no dependency on Stage core or Stage CMS. skyyware/stage-chat-codex is a separate connector. Build the chat interface and application behavior separately.

Sources

• Stage Chat contract and limits
• Connector interface
• Request validation
• Message validation
• Runtime dependencies