Answer: Compare the absolute path in the error message with what's on disk, then fix the path or create the directory, and run `/reload-plugins`. Status: Confirmed Entry: tool/claude-code/troubleshooting/fix-commands-path-not-found Revision: 2 Digest: sha256:07fc35afb2cba366 (changes whenever the content changes) Timeline: Created: 2026-11-15T12:24:33Z Last changed: 2026-11-18T12:19:28Z (fix: — → Fix the path or create the directory, then run `/reload-plugins`.) Last verified: 2026-11-20T12:24:16Z Next check: 2026-11-21T12:24:16Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of error message | commands path not found: | [1] | 2026-11-20 guidance shown | Check that the path in your manifest or marketplace config is correct | [1] | 2026-11-20 fix | Fix the path or create the directory, then run `/reload-plugins`. | [1] | 2026-11-20 path format | Paths in the manifest are relative to the plugin root and start with `./`. | [1] | 2026-11-20 version note | v2.1.299 | [1] | 2026-11-20 Sources: [1] Anthropic. "Troubleshoot plugins". https://code.claude.com/docs/en/plugins/troubleshooting.md Role: primary. Accessed: 2026-11-20T12:24:16Z Quote: "The **Errors** tab shows `commands path not found: `" (Supports: error message) Quote: "with the guidance `Check that the path in your manifest or marketplace config is correct`" (Supports: guidance shown) Quote: "Fix the path or create the directory, then run `/reload-plugins`." (Supports: fix) Quote: "Paths in the manifest are relative to the plugin root and start with `./`." (Supports: path format) Quote: "Before v2.1.299, this message could appear at startup on a row labeled with a tag such as `synced[0]`." (Supports: version note) Published: 2026-11-20T03:36:45Z Snapshot SHA-256: 5155c5edab68e7a1e31e9426e733fc8281a548f7dce24fd9c2a365188c9275f7 (captured 2026-11-20T12:24:14Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:24:16Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:24:16Z Last attempt: 2026-11-20T12:24:16Z Notes and limitations: Extracted automatically from a single official source (section "Build a plugin"). Related: https://latestn.com/tool/claude-code/troubleshooting/fix-garbled-text-integrated-terminal How do I fix garbled or corrupted text in an editor's integrated terminal when using Claude Code? https://latestn.com/tool/claude-code/troubleshooting/fix-high-cpu-memory-usage How do I fix high CPU or memory usage in Claude Code? https://latestn.com/tool/claude-code/troubleshooting/fix-invalid-api-key How do I fix the Claude Code "Invalid API key" error? https://latestn.com/tool/claude-code/troubleshooting/fix-cliconnectionerror-failed-to-start What causes a CLIConnectionError: Failed to start Claude Code and how do I resolve it? https://latestn.com/tool/claude-code/troubleshooting/fix-clinotfounderror How do I fix the CLINotFoundError when using the Claude Code Agent SDK? https://latestn.com/tool/claude-code/troubleshooting/fix-command-not-found How do I fix 'command not found: claude' after installing Claude Code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:19:28Z | changed | fix: — → Fix the path or create the directory, then run `/reload-plugins`. | [1] 2026-11-18T12:19:28Z | changed | guidance shown: — → Check that the path in your manifest or marketplace config is correct | [1] 2026-11-18T12:19:28Z | changed | fix action: Fix the path or create the directory, then run `/reload-plugins`. → — | [1] 2026-11-15T12:24:33Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/troubleshooting/fix-commands-path-not-found/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/troubleshooting/fix-commands-path-not-found POST: https://latestn.com/dispute/tool/claude-code/troubleshooting/fix-commands-path-not-found with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/troubleshooting/fix-commands-path-not-found?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix the "commands path not found" error when building a Claude Code plugin? Revision 2, last verified 2026-11-20T12:24:16Z. https://latestn.com/tool/claude-code/troubleshooting/fix-commands-path-not-found (accessed 2026-11-21T09:57:19Z). @misc{LatestN_tool_claude_code_troubleshooting_fix_commands_path_not_found_r2, title = {How do I fix the "commands path not found" error when building a Claude Code plugin?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/troubleshooting/fix-commands-path-not-found}}, note = {Revision 2; digest sha256:07fc35afb2cba366; last verified 2026-11-20T12:24:16Z; accessed 2026-11-21T09:57:19Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/troubleshooting/fix-commands-path-not-found