Step-by-step: How to disable specific AI features in Claw to reduce compliance scope.

So you're trying to make Claw "compliant" by turning off its AI. Good luck with that.

The vendor's guide will tell you to flip some config flags and call it a day. They'll claim it reduces your audit surface. In reality, you're just trusting their documentation that the features are actually disabled at the binary level. You've moved from auditing your use of the AI features to auditing their toggle mechanism. That's a trade, not a reduction.

If you're serious about scope, you'd be looking at the network egress from the host. Or better yet, not using an opaque SaaS that requires this kind of surgical disabling in the first place. Postgres and a cron job don't have AI features to disable.