[Bug] Content filter over-blocking legitimate Australian AML/CTF statutory compliance research

Resolved 💬 1 comment Opened Apr 24, 2026 by jacobtruvro Closed May 28, 2026

Bug Description
Content filter is blocking legitimate Australian regulatory compliance research in Claude Code.

Request IDs (pattern — repeated blocks on the same task, selection below):

  • req_011CaMdGGwek5TKTCxY8EgkV
  • req_011CaMdee2mzrrn5tFSxxBjc
  • req_011CaMdpKCj5q1a5FkJ36A9h

Task: Assembling a compliance design document from Australian Commonwealth primary law — verbatim sections of the AML/CTF Act 2006 (compilation C2006A00169) and AML/CTF Rules 2007 (F2007L01000), both freely published at legislation.gov.au, alongside AUSTRAC's public SMR reference guide. Output is statutory text plus neutral structural commentary on SMR/TTR/IFTI form mechanics. No operational detail, no evasion guidance, no tradecraft.

The filter appears to trip when the output aggregates offence-category references from AUSTRAC's public reference guide alongside the statutory triggers in s.41 of the Act. Individually each passage is neutral public law; the filter seems to treat the aggregation as a catalogue of offences.

Paid Claude Code user, Australian fintech, building internal regulatory artefacts. Please review filter behaviour on outputs composed primarily of Commonwealth statutory text for compliance deliverables. Happy to share the full request_id list, the prompt, and the sanitised output on request.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.119
  • Feedback ID: c4ab45cc-9395-404c-80dd-ddc582184815

Errors

[{"error":"Error: rg --files exited 2\n    at <anonymous> (B:/~BUN/root/src/entrypoints/cli.js:705:84)\n    at emit (node:events:98:22)\n    at #maybeClose (node:child_process:778:16)\n    at emit (node:events:92:22)\n    at emitCloseNT (internal:streams/destroy:78:14)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-24T00:20:10.913Z"}]

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗