[Bug] Fable 5 false positive on OSS decompilation analysis in code review context

Status Open
Reported on v2.1.237
Maintainer reply None cached
Activity 0 comments · opened Aug 20, 2026

Bug Description
False positive on Fable 5 safeguards, Details: [reasoning_extraction]
Request ID: req_011CeDZvNGKycsyJu26GNEzc

Context: pasting the output of a code-review skill into a Fable 5 session and
asking it to fix the findings. The content is an ordinary C# code review of a
test harness - one finding about a Verify (unit-test assertion library)
setting that stops orphaned snapshot baselines from self-healing, plus two
missing-unit-test notes. No policy surface anywhere in it.

Fable returned the AUP safeguards error instead of a response. Asking it to
explain why produced the identical error again - because the flagged content
is still in context and it re-trips on every turn, so the conversation is
unrecoverable without editing the prior message.

Best guess at the trigger: the finding cites a decompile of the Verify 27.0.0
assembly with internal file/line references (engine.cs:4860-4868) to justify
the claim, and infers a callback signature from it. Verify is MIT-licensed
OSS and this is routine debugging of a test dependency, but the "decompiled a
third-party binary and quoted its internals" shape appears to be what fired.

Two things worth looking at:

  1. The classifier treating OSS decompilation/source-inspection during

debugging as a violation - this is normal developer work.

  1. The [reasoning_extraction] failure mode being unrecoverable in-session and

giving no actionable signal. The same error repeating on a follow-up
question, with no indication of what to remove, is a bad experience even
when a flag is correct.

Environment Info

  • Platform: darwin
  • Terminal: zed
  • Version: 2.1.237
  • Feedback ID: ffb7b347-0571-4d4a-939a-b62a58d1f32b

Errors

[]

View original on GitHub ↗