dsh-linked-folders

A dsh session is normally pinned to a single workspace root, so tasks that span multiple repositories, document trees, or config folders force the model to stay inside one directory and make cross-folder work clumsy. dsh-linked-folders brings Codex-style linked-folder support into dsh, giving every session a flexible, extensible map of multiple roots. The plugin maintains two layers: a durable global list that acts as your standing workspace, and per-session temporary links that the model can attach or detach on the fly via the link_folder and unlink_folder tools. Both lists are injected into the system prompt as a Linked folders section, so the model knows exactly which extra roots it may cd into. Management lives behind the folder icon on the Composer input bar, where you can add folders by absolute path or browse to them; temporary links appear in the conversation tagged with (this session).

If your daily workflow hops between multiple projects, monorepo sub-trees, or standalone document libraries, this plugin lets you keep one context while working across several workspaces at the same time. It is ideal for developers running multi-repo sessions, teams sharing common config or doc folders, and anyone who finds the single-root model too restrictive. Keep in mind it only advertises folders to the model and provides the management UI; it does not widen the file sandbox. Under the workspace-write policy the model can read linked folders but writes remain confined to the session workspace root, while full read-write access requires the danger-full-access policy. The prompt token cost scales linearly with the number of linked folders and is zero when none are linked.