dsh-omniloop

dsh admits exactly one AgentFactory per process, which meant running Claude Code required disabling the built-in loop and dragging every session along with you. dsh-omniloop seizes that single slot and turns it into a router: the in-process loop, Claude Code, Codex, and Pi each hold their own factory, and every createAgent or resume call is dispatched to the engine that session belongs to. No global switch, no restart, no interrupted work.

Choosing an engine feels as natural as choosing a model — a click in the composer when you start a session. The binding is durable: a session's engine is recorded at creation and restored on resume, so replaying Codex history will never accidentally land on the built-in loop. Forked sessions and subagents inherit the parent's engine. Each engine's native output is translated into dsh's unified Message, ContentBlock, and StreamChunk types, so storage, streaming, resumption, and tracing behave identically regardless of origin.

If you routinely work across Claude Code, Codex, Pi, and dsh's built-in loop and would rather pick an engine per task than pay a restart and a context switch every time, this plugin is built for you. Once installed, engine selection is pure runtime state — switching never requires a restart, and the session you are in keeps running on the engine it was born with, undisturbed.