Feature request: Ship `dsp` as a bin entry for `claude --dangerously-skip-permissions`

[DocWach]

Summary

dsp (shorthand for claude --dangerously-skip-permissions) is a common workflow shortcut but is not shipped as a bin entry in the claude-flow package. Users must manually create shell-specific wrapper scripts, which is error-prone across different terminals (CMD, PowerShell, Git Bash).

Current State

package.json only exports one binary:

"bin": {
  "claude-flow": "./v3/@claude-flow/cli/bin/cli.js"
}

No dsp command exists anywhere in the source.

Problem

On Windows, users need three separate scripts to make dsp work across all terminals:

• .cmd for CMD
• .ps1 for PowerShell (VS Code default)
• extensionless bash script for Git Bash

Without these, dsp silently fails or returns "command not found."

Proposed Solution

Add dsp as a cross-platform Node.js bin entry:

"bin": {
  "claude-flow": "./v3/@claude-flow/cli/bin/cli.js",
  "dsp": "./v3/@claude-flow/cli/bin/dsp.js"
}

Where dsp.js:

#!/usr/bin/env node
const { execFileSync } = require('child_process');
try {
  execFileSync('claude', ['--dangerously-skip-permissions', ...process.argv.slice(2)], { stdio: 'inherit' });
} catch (e) {
  process.exit(e.status || 1);
}

npm automatically generates .cmd and .ps1 wrappers for Node.js bin entries on Windows, so this single file works everywhere.

Environment

• claude-flow v3.1.0-alpha.3
• Claude Code v2.1.61
• Windows 11, PowerShell (VS Code terminal)

[DocWach]

Root Cause Probability Assessment

After investigating, we performed a probability assessment of what caused the dsp command to stop working:

#	Hypothesis	Probability	Evidence
1	claude-flow update dropped a previously-shipped bin entry	40%	claude-flow went from 3.0.x → 3.1.0-alpha.3 recently; bin entries can be lost during major refactors. No historical package.json was available to confirm dsp was ever shipped.
2	npm global bin corruption during rapid Claude Code updates	25%	10 Claude Code releases in 4 days (v2.1.50 → v2.1.61) on Windows. v2.1.61 specifically fixed "concurrent writes corrupting config file on Windows." npm global bin directory churn could delete non-npm-managed files.
3	Manual wrapper files lost (disk cleanup, OneDrive sync, Windows update)	20%	npm bin dir is on local disk, but Windows updates and sync tools can interfere.
4	dsp never existed as a shipped command	15%	Codebase search found zero references. Simplest explanation but conflicts with user's recollection.

Conclusion: Whether dsp was previously shipped and dropped, or was always a manual setup that got lost, the fix is the same — claude-flow should ship dsp as a cross-platform Node.js bin entry so it survives updates automatically. The proposed dsp.js wrapper in the original issue description would solve this permanently.

The concurrent-write corruption fix in Claude Code v2.1.61 suggests Windows file corruption was a known issue during this update period, which reinforces hypothesis 2 as a contributing factor.