{"version":"2.1.221","anchor":"sandbox-reports-whether-the-tls-inspection-ca-is-trusted","canonical_anchor":"sandbox-reports-whether-the-tls-inspection-ca-is-trusted","heading":"\/sandbox reports whether the TLS inspection CA is trusted","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/sandbox-reports-whether-the-tls-inspection-ca-is-trusted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### \/sandbox reports whether the TLS inspection CA is trusted\n\nThe \/sandbox status now shows whether the HTTPS inspection certificate is trusted and how to fix it.\n\n**What**\n\nThe sandbox status view now tells you if HTTPS interception is actually set up, and what to do when it isn't.\n\n**Details**\n\n- Adds a \"TLS inspection CA:\" row rendering either \"trusted\" or \"not trusted\".\n- When the untrusted CA is the managed one, the row suggests \"\u00b7 run \/sandbox install\".\n- Otherwise it advises \"\u00b7 ask your administrator to trust the configured sandbox CA \u2014 see https:\/\/code.claude.com\/docs\/en\/sandboxing\".\n- Only computed when the sandbox TLS-terminate configuration is present; on Windows this means the CA source is not \"unavailable\". Otherwise the trust field is null and the row is hidden entirely.\n\n**Evidence**\n\n`TLS inspection CA:`\n\n- Area: Sandbox\n- Names: `\/sandbox`, `\/sandbox install`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}