dsh-at-file Compatibility Plugin

When the dsh-at-file Compatibility Plugin Still Helps

Keep the plugin only when an established profile needs its file picker and the current DSH upgrade path is not yet available. Do not install it by default on a new environment simply because the package name appears in an older setup guide.

For a legacy test profile, the repository's current tagged package is added with:

dsh plugin --profile web add https://github.com/omdsh-dev/dsh-at-file/archive/refs/tags/v0.7.0.tar.gz

Restart the selected DSH web profile afterward. The repository's package metadata is not fully synchronized across every file, so pin the intended tag instead of claiming a universal internal version.

Verify the installation in a disposable workspace. Type @, choose a known file, submit a bounded task, and confirm that the agent reports the referenced path. If the picker does not appear, check the web profile, restart it, and confirm that the file-mentions setting is enabled.

Searching the Workspace From the Prompt Box

Typing @ opens a picker for file and directory paths inside the current workspace. The picker searches path and file names, limits the visible candidate list, and keeps references inside the workspace boundary. Unknown @text stays ordinary text.

The plugin is useful when a developer knows the relevant file exists but does not want to paste or retype the path. A valid path can still be referenced even if a large workspace caused it to fall outside the indexed picker list.

How Workspace References Reach the Agent

For plugin version 0.3.0 and later, the plugin does not attach the file's contents to the prompt. It validates the path and injects a small workspace-reference marker. The agent then decides whether to open or inspect that path using the tools available in the session. The repository notes that earlier releases did read file content during submission and enforced file-size limits.

That distinction matters for large files, PDFs, and directories. Referencing a path does not prove that its contents were read, parsed, or added to context. A useful task request should still name the expected output and ask the agent to report files it could not inspect.

For a more visible terminal surface around those tasks, dsh-TUI focuses on status, streaming output, and tool cards.

The Blink alternative is the more relevant next page when the decision is whether to keep source work in a repository or use a managed app builder.

Turning the Plugin Off and Using Built-In @file

The plugin settings include an Enable @ file mentions control. Turning it off hides the picker and reference dock and stops the marker from being injected. This is the safest immediate fallback when the surface conflicts with another plugin.

The repository does not provide a dedicated remove or rollback command. For a maintained workflow, move to the current built-in @file and @session features, check the behavior in a test profile, and only then retire the legacy setup.

How HappySeeds Fits This Workflow

dsh-at-file concerns coding-agent context. HappySeeds concerns the product that the team is trying to build. A useful handoff can begin with a HappySeeds plan that names pages, flows, and acceptance criteria, then point a repository agent to the exact implementation files needed for one bounded change.

Review the HappySeeds first-project workflow before introducing a repository handoff.