AI Agent Hub
Back to plugins
dsh-plugin-better-glob preview

dsh-plugin-better-glob

Workflow Updated 2026.09.04

Run the following command in DeepSeek Harness:

dsh plugin install HuanLinOTO/dsh-plugin-better-glob

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install HuanLinOTO/dsh-plugin-better-glob in DeepSeek Harness to install; source is available at https://github.com/HuanLinOTO/dsh-plugin-better-glob

About this plugin

When you run glob searches through DSH, the built-in tool plunges indiscriminately into node_modules, dist, .venv, .gradle, and other bottomless directories, burning tokens and slowing down every response. The files the model actually needs are rarely hiding in there. dsh-plugin-better-glob shadows the built-in glob at the per-agent scope layer and prunes roughly thirty common artifact and dependency directories during the ripgrep walk phase, not after the fact. Pruned subtrees never reach the result set, while the familiar 100-result cap and spill-recovery behavior stay intact.\n\nThe core mechanism is an include whitelist. If the model genuinely needs to search a pruned directory, it must explicitly pass an include pattern segment in the call parameters, which un-prunes that directory for that invocation only. include governs directory-level pruning alone; pattern remains the sole path matcher, keeping the two responsibilities cleanly separated. VCS metadata directories such as .git, .svn, and .hg are permanently excluded with no override, guarding against accidental exposure of sensitive data. The plugin touches no built-in plugin registration surface and leaves grep completely untouched.\n\nIt is best suited for developers working in large monorepos or polyglot codebases where toolchain artifacts like Python venvs, Gradle caches, Terraform state, and SvelteKit outputs intermingle with business code. The default exclude list can be wholesale replaced via excludeDirs, and tuning knobs such as globMaxResults and timeoutMs mirror built-in semantics, making adoption low-friction and easily reversible.

Screenshots

Use Cases

  • Searching business files in a monorepo without drowning in node_modules or build artifacts
  • Excluding Python venvs, Gradle caches, and Terraform state in polyglot projects
  • Un-pruning a specific excluded directory via the include whitelist when the model requests it

Best For

  • Developers who rely on DSH glob search in large monorepos or polyglot codebases
  • Teams shipping multiple toolchain artifacts like .venv, .gradle, .terraform, and .svelte-kit
  • Agent-workflow users who want tighter search scoping to cut token burn