Claude Code settings.local.json: find and fix saved secrets
Saved Claude Code approvals can contain inline credentials. Check local settings, prevent accidental commits, and rotate secrets that were exposed.
Saved Claude Code approvals can contain inline credentials. Check local settings, prevent accidental commits, and rotate secrets that were exposed.
Cursor can receive your workspace path before any tool runs. How directory names enter context, and what to check before storing or sharing sessions.
Map Cursor hook coverage, failure behavior and cloud-agent limits before relying on hooks for security controls and session evidence.
Reconstruct an AI coding session from tool calls, policy decisions and results. Know what the evidence proves, and where the record stops.
What Canadian CTOs should check before engineers send code and logs to Cursor, Claude Code or Copilot: PIPEDA, Law 25 and the records to keep.
What EU engineering leaders should record when Cursor, Claude Code or Copilot touch personal data: GDPR duties, AI Act scope and an evidence list.
A scoped engagement MSPs, MSSPs and vCISOs can deliver to software clients using Cursor, Claude Code or Copilot: inventory, policy, evidence and review.
Cursor's notice on tampered Anthropic.claude-code 2.1.312 and 2.1.313: who was exposed, how to check a machine, and extension controls to add.
How Google Antigravity and OpenAI Codex agents read, print, and send secrets; what hooks and sandboxes cover; and where vendor docs leave failure modes undocumented.