dsh-plugin-dew

Running Claude Code in one window, Codex in another, and maybe Cursor on top of that, yet having no single place to see where each one stands is a daily friction. dsh-plugin-dew solves exactly that. It never writes into any agent data directory, never touches a keychain or credential store, and makes no network calls. It simply parses the session logs those agents already write to disk and normalizes everything into one four-state vocabulary: needs you, running, done, idle, giving you an at-a-glance overview from inside DSH.

The plugin exposes two read-only tools. agent_sessions lists active sessions with their current state and supports filtering by agent type, state, lookback window, and row limit, so you can quickly confirm whether a Claude Code run has finished or which agent is blocked waiting for your input. agent_scheduled_tasks lists recurring jobs from Codex automations and Claude Code scheduled tasks, evaluated locally, and tells you when each one fires next. State determination varies by agent: Codex and DSH expose explicit lifecycle events, Claude Code state is inferred from the transcript tail, and Cursor relies on the last row plus file modification time. The needs-you state is always an inference, with per-tool thresholds so that a quietly running long Bash command is not misreported as a permission prompt.

Who is it for? If you run multiple coding agents in parallel, frequently switch windows to check progress, or want to confirm no other agent is already working in a directory before you start editing, this plugin is built for you. It ships as plain ESM with nothing to compile, installs cleanly into any DSH profile, and does not alter your existing agent workflows in any way.