dsh-env-profile

Every new session forces the model to rediscover the machine from scratch: which tools are installed, their versions, which paths are reliable, which network link is fast. That repeated probing is slow and burns tokens for no lasting gain. dsh-env-profile solves exactly this. As a DSH global-experience plugin, it runs a one-time host-side probe, distills the results into a cross-session profile, and hands the model a working knowledge of the environment from the very first turn so it stops re-running env, which, and ping round by round.

The closed loop has three stages. Probing fires in parallel across 33 common commands (existence plus version where available), key filesystem paths, a TCP-443 handshake timing, and a 1 MiB disk read/write sample—all deterministic host-side operations that cost zero tokens and are cached for a configurable interval (default 6 hours). Accumulation subscribes to session events, folds per-turn tool calls, errors, and token ledgers into per-session stats, and uses the session's own model every N turns to extract user preferences, project conventions, and useful paths as knowledge entries, deduplicated by normalized text and stored globally. Injection compresses the profile into a byte-deterministic summary (hard-capped at 600 characters by default) at system-prompt slot 500; when the profile is unchanged the summary is identical byte-for-byte every turn, so DeepSeek's prefix cache keeps hitting, and even when the summary does shift only the tail is invalidated while the large stable prefixes above remain cached.

It is aimed at developers who run DSH intensively and care about token efficiency: if you open a dozen sessions a day, keep asking the model to re-verify tool versions, paths, or network latency, or simply want the model to carry forward the machine's quirks across sessions, this plugin gives every new conversation the full environment context up front and redirects the saved probing turns and explanatory tokens back to the actual work. The current skeleton targets Windows; POSIX support is already on the roadmap.