Codex Stello Orchestration for Per-Session Queue Ordering
Check per-session ordering and independent concurrent sessions using Stello's orchestration API.
中文Install in Codex
Open Stello in Codex with session IDs, pending requests and the application's orchestration settings.
- Review `.agents/skills/orchestrator-usage/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/orchestrator-usage/` in your project and save the reviewed file as `.agents/skills/orchestrator-usage/SKILL.md`.
- Start Codex from that project's root, then type `$orchestrator-usage` and select the matching skill.
Example task
Identify ordering constraints for these three illustrative requests.
{"sessionA":["task-a1","task-a2"],"sessionB":["task-b1"],"transport":"none"}What to check
Keep `task-a1 → task-a2` in session A. Session B's `task-b1` can proceed independently without waiting for A's queue to drain.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does the orchestration queue require WebSocket transport?
The orchestration layer manages per-session order, while applications can choose the transport boundary independently.