dsh-subagent-route-badges

When you juggle multiple subagent sessions, it is common to want a quick answer to which provider, which model, and what reasoning effort is actually routing this chain. dsh-subagent-route-badges keeps things light: it adds a single route badge to the Header area of an already-open subagent session, surfacing provider, model, and reasoning effort at a glance. It neither intercepts nor rewrites model requests—this is a pure display layer.

Implementation follows a strictly additive approach: the plugin registers one list-slot seat under a unique ID without copying or shadowing any official UI components and without competing for single-slot positions, so there is no slot, locale, or priority conflict surface with the official package. Field sourcing is deliberately narrow—data.header.config in the latest request/header is the authoritative source for provider and model; when adapterDefaults.reasoningEffort is true, an unmarked effort is labelled adapter-default, otherwise it shows as unspecified. Assistant rollbacks affect provider and model only and never overwrite a known effort. When the projection is missing, a route-unknown placeholder appears so you can visually confirm the badge component has taken over.

If you routinely run multiple subagent chains in DSH and need to verify routing configuration often, or if you are privacy-conscious and do not want plugins touching message bodies or credentials, this small badge is a practical addition to your workflow. It uploads no data and reads no files; long text is truncated in the badge but the full value is preserved in the title and aria-label attributes, balancing accessibility with information completeness.