dsh-workspace-envrc

In DSH, when an Agent runs a Bash command or spawns a local stdio MCP process, the environment is flat. It neither discovers .envrc files in the working directory nor inherits the variable isolation that direnv has already configured. dsh-workspace-envrc fills exactly that gap: it delegates .envrc discovery, evaluation, hash authorisation, and allow/deny decisions entirely to the system-installed direnv binary. The plugin does not parse .envrc, does not maintain an authorisation database, and does not mutate the Harness process.env. Its only job is a reversible method decorator around the existing DSH seams.

Two integration paths carry the logic. First, when the initiating Agent resolves to a canonical workspace through scope ancestry, both foreground and background Bash executions freeze the direnv-determined environment at the moment the child process starts; workdir, timeout, and sandbox policy remain exactly as the caller set them. Second, local stdio MCP lines mapped to the same workspace receive the same wrapping, while global, HTTP, foreign-scope, or malformed lines pass through untouched. Neither path uses shell: true to assemble command strings, and on fiber dispose the descriptors are restored in reverse order; a failed MCP install rolls back the already-attached Bash adapter.

This plugin is built for developers and teams who already lean on direnv across multiple projects or workspaces and simultaneously run DSH Agents. It does not replace direnv or introduce a new environment-configuration layer; it simply lets the Agent-side execution honour the .envrc files you have already written.