dsh-omniloop

dsh's architecture allows only one AgentFactory per process, so running Claude Code meant disabling the built-in loop and forcing every session in the profile to follow along. dsh-omniloop takes that single factory slot and turns it into a per-session router. The in-process loop, Claude Code, Codex, and Pi each register their own factory, and every createAgent or resume call is dispatched to the engine that owns the session. No global switch, no restart, no interrupted work.

Picking an engine is as simple as picking a model: a selection in the composer at session start. The affinity is durable — a session's engine is recorded when it is created and restored on resume, so replaying a Codex-driven transcript will never accidentally fall through to the built-in loop. Forked sessions and subagents inherit the parent's engine automatically. Above the router, everything remains dsh's: each engine's native output is translated into dsh's Message, ContentBlock, and StreamChunk types, so sessions from different engines are stored, streamed, resumed, and traced identically.

This plugin is for developers who switch between Claude Code, Codex, Pi, and dsh's built-in loop on a per-task basis and are tired of paying a restart and a context switch every time. After a one-time install and restart, engine selection becomes pure runtime state: the current session keeps its engine undisturbed, the next session can run on a different one, and nothing in between is lost.