Unverified50% confidenceFactExact time
Paths declared in plugin commands within marketplace entries that point outside the plugin directory are now directly rejected with a path traversal error
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
9/11/2026
First Seen
Valid until: 12/10/2026
Sources
Related Entities
Related Claims
UnverifiedThe "not recognized as an internal or external command" error when executing the claude command is caused by the installation path not being added to the system PATH environment variable.67% similarUnverifiedFixed an issue where file permission rules containing uncompilable patterns (such as an unclosed [) caused all file editing operations to fail due to invalid regular expressions; such deny rules now fall back to guarding only the literal path61% similarUnverifiedRules under the .claude/rules directory without a Path configuration are loaded unconditionally, while rules with a Path configuration are only loaded when operating on matching files.57% similarUnverifiedThe reason text did not display after deployment to the development board was that the font path was written as a relative path, causing resource loading failure due to inconsistency between the UI Builder path and the actual Lubanite path.56% similarUnverifiedThe root cause of a command not found error is that the system PATH environment variable does not include the directory where the tool's executable file is located.50% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/897975API
curl https://kongchang.com/api/v1/knowledge/claims/897975MCP
get_claim(id=897975)