Codex Stello Transport Design for Non-Streaming REST Fallback
Choose Stello request transport based on available client channels and whether the response is streamed.
中文Install in Codex
Open Stello in Codex with the available transport, response type and current server interface.
- Review `.agents/skills/server-design/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/server-design/` in your project and save the reviewed file as `.agents/skills/server-design/SKILL.md`.
- Start Codex from that project's root, then type `$server-design` and select the matching skill.
Example task
Choose the existing project interface for this local client.
{"client":"label review demo","webSocketAvailable":false,"streaming":false,"space":"test-space"}What to check
Choose the non-streaming REST endpoint `/turn` and keep `streaming=false`.
Original SKILL.md on GitHub · Updated
Frequently asked question
How are streaming and regular messages distinguished?
The project lets the client explicitly choose the stream or message type.