Skip to main content

How to use dsh-fail-logger

Auto-log failed tool calls across native tools, PTC run_code, and inline invocations: dedup and count root causes into a skill so repeated mistakes fade.

This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.

This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

Auto-log failed tool calls across native tools, PTC run_code, and inline invocations: dedup and count root causes into a skill so repeated mistakes fade.

— source: plugins.ai_summary

Install & verify

dsh plugin --profile web add dsh-fail-logger

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

  • [tool] [bash] EPERM: operation not permitted, open '/Users/me/.dsh/x' — ×3（最近 2026-08-14 10:20）｜命令: rm -rf /x｜💡 检查沙盒权限，或用被允许的操作重试
  • [tool] [read] ENOENT: no such file or directory — ×2（最近 2026-08-14 10:19）｜💡 先确认路径存在再操作
    • id: dsh-fail-logger
  • Trend & TTL: per-day counters render a "last 7 days" trend line; entries with no new occurrence for ttlDays are archived.
  • over-wide searches: whole-drive glob on C:\ / D:\, or grep over huge paths such as node_modules and DSH install directories;

— source: plugin_wiki.readme_en (fallback readme_raw)

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule

How to use dsh-fail-logger