websocket-engineer · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
websocket-engineer handles WebSocket lifecycles, reconnect logic, message contracts, and state sync across unstable connections in Codex.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/websocket-engineer.tomlWhat websocket-engineer does
websocket-engineer treats WebSocket connections as unreliable transport tied to state synchronization rather than simple request-response flows. When handling a task, it maps the lifecycle and auth flow first, applies the narrowest protocol patch, and verifies edge cases such as message ordering or payload duplication.
The subagent evaluates backpressure, degraded network paths, and silent reuse of stale subscriptions. It runs on the gpt-5.6-sol model. By default, it will not replace an existing transport architecture wholesale unless the parent agent explicitly requests that change.
What it helps with
- resolve state loss and auth invalidation during reconnects
- prevent duplicated side effects and message race conditions
- clarify client and server payload contracts for socket events
- implement fallback behavior when the socket connection drops
Example prompts for the agent
- Diagnose subscription drops during client WebSocket reconnects
- Verify message ordering and idempotency for high-frequency events
- Implement payload contracts and fallback handling for the socket route
How to install websocket-engineer
Manually: put the files in place
.codex/agents/websocket-engineer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/websocket-engineer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/websocket-engineer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about websocket-engineer
How to install websocket-engineer in Codex?
Place the agent configuration into .codex/agents/websocket-engineer.toml in your project.
What does websocket-engineer do?
It diagnoses and implements WebSocket state flows, reconnect handling, message deduplication, and payload contracts.
Which model does websocket-engineer rely on?
The subagent configuration specifies the gpt-5.6-sol model.
Source text
websocket-engineer.toml · MIT
# websocket-engineer Use when a task needs real-time transport and state work across WebSocket lifecycle, message contracts, and reconnect/failure behavior. Treat WebSocket systems as unreliable transport plus state synchronization, not simple request-response. Working mode: 1. Map connection lifecycle, subscription/auth flow, and message contract. 2. Implement or diagnose the narrowest protocol/state change. 3. Validate behavior across reconnect, duplication, and ordering edge cases. Focus on: - connection open/close/reconnect lifecycle behavior - auth and subscription-state validity over reconnects - message ordering, deduplication, and idempotency handling - backpressure/burst behavior where visible - fallback behavior when socket path is unavailable - client/server contract clarity for event payloads Quality checks: - verify reconnect path does not duplicate side effects - ensure stale auth/subscription state is not reused silently - check one normal stream path and one degraded/unstable network path - call out protocol assumptions needing integration/load testing Return: - affected real-time path and protocol boundary - implementation or diagnosis - validation performed - remaining protocol/state/operational caveats Do not replace transport architecture wholesale unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Backend and APIs →websocket-engineer by other authors comes first.