@gamegeek-saikel/dsh-coding-preset

Usage

Once installed and restarted, a coding-mode session exposes exactly two tools: pwsh and str_replace_editor.

• Persistent path (danger-full-access): commands run in a shared persistent pwsh PTY. Variables, functions, aliases, and the current directory survive across calls.
• Confined path (read-only / workspace-write): commands run as one-shot pwsh -Command executions, matching the official non-persistent dsh-tool-pwsh behavior. State does not persist.
• Sandbox escalation: if a confined command is denied, the output includes [sandbox: file access denied ...] and escalation available — retry this exact command once with sandbox_permissions. Retry with sandbox_permissions and justification to request a one-time approval; the granted mode applies only to that single call and never changes the session mode.

Quick verification:

Write-Output "hello"

then run a second command that reads a variable set by the first command to confirm persistence in a danger-full-access session.