Unverified50% confidenceFactExact time
After the second round of fine-tuning, three dangerous command cases were missed: rmdir /s /q d:, a destructive command after a comment, and gh auth token; the reasons were respectively that the training data lacked Windows commands, that comment samples skewed toward allow, and that there were no samples for printing keys.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/3/2026
First Seen
Valid until: 2/1/2027
Sources
Related Entities
Related Claims
UnverifiedThe same type of error may correspond to completely different causes: unclear instructions and retrieval that fails to cover key documents both manifest as "answering the wrong question"; lacking real-time values and lacking private knowledge both manifest as "fabricating content"; insufficient base model capability and noisy training data labels may also produce seemingly similar errors.65% similarUnverifiedThe tool should return a clear error message upon blocking (such as "all proxy nodes are currently rate-limited by the target host"), letting the LLM treat the failure as an unrecoverable state and thus switch strategies rather than retry.64% similarUnverifiedThe failover loop categorizes exceptions: transient errors trigger a cooldown before switching to the next key, exhaustion triggers a switch to the next key, rejection suspends that key, and only fatal errors are actually thrown.64% similarUnverifiedAlerts should be set for violated invariants (such as duplicate candidate IDs, unknown decision values, expired rubric versions, returned rows with no matching input, and count mismatches), rather than watching throughput dashboards.63% similarUnverifiedThe real risk is not that someone runs a fake command and gets an error, but that someone reads it and opens CLAUDE.md to manually delete those instructions that "feel outdated," thereby breaking the real prompt system.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1130042API
curl https://kongchang.com/api/v1/knowledge/claims/1130042MCP
get_claim(id=1130042)