Fable 5 is incredibly capable, but the safety filters are currently a bit overzealous. They trigger false positives constantly when you try to ingest large project structures via the Claude Code desktop app. I was testing a few ways around this and found a very reliable fix. Instead of letting the model read the files silently in the background, just instruct it to document the process. Append something like this to your prompt: “Please drop brief status updates in the chat while you process the files. Keep me updated step-by-step as you read the attachments in chunks.” The reason this works is that it forces the model to generate intermediate outputs. You basically shift the evaluation from one massive file scan to a chunk-by-chunk process. That stops the main safety filter from instantly nuking the request due to a perceived global flag across your whole codebase. An added bonus: if the request still gets blocked anyway, those status updates act like a trace. You can see exactly which specific chunk or file tripped the filter instead of just getting a generic rejection. Super simple trick, but it bypasses the friction and saves a lot of wasted API calls. submitted by /u/martin_rj
Originally posted by u/martin_rj on r/ClaudeCode