claude-code - 💡(How to fix) Fix Opus 4.7 does not honor cybersecurity use approval previously granted on 4.6 [1 comments, 2 participants]

Summary

After upgrading to Claude Opus 4.7, the model no longer honors the cybersecurity / authorized-use approval that was previously accepted and persisted under Opus 4.6. Tasks that 4.6 would proceed with (authorized penetration testing, security research workflows using the /pentest skill, Burp/Ghidra MCP tooling, etc.) are now being refused or gated again on 4.7, even though the prior approval should still apply.

Environment

• Model: claude-opus-4-7 (previously claude-opus-4-6)
• Platform: macOS (Darwin 25.4.0)
• Claude Code CLI
• User context: security researcher / authorized pentesting work, with /pentest, Burp MCP, and Ghidra MCP configured

Expected behavior

Cybersecurity-use approvals granted under a prior Opus version should carry over when upgrading to a newer Opus model in the same Claude Code installation. Authorized pentesting / defensive security workflows should continue without re-prompting or refusal.

Actual behavior

Opus 4.7 behaves as if no prior approval exists:

• Refuses or hedges on requests that 4.6 handled directly under the same approval
• Treats authorized-testing context (CLAUDE.md, /pentest working dir, MCP stack) as insufficient
• Does not appear to read or respect the previously approved cyber-use grant

Impact

• Breaks continuity for security-research workflows mid-engagement
• Forces re-approval (or workarounds) on a per-session basis
• Inconsistent behavior between Opus 4.6 and 4.7 for the same user, same machine, same configuration

Request

Please ensure that cybersecurity / authorized-use approvals persist across Opus model upgrades (4.6 → 4.7), or document how to re-grant the approval at the account level so 4.7 picks it up automatically.