{"version":"2.1.310","anchor":"repository-trust-session-elevation-tool-errors-recognised","canonical_anchor":"repository-trust-session-elevation-tool-errors-recognised","heading":"Claude Code now recognises errors about repository trust and session elevation","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/repository-trust-session-elevation-tool-errors-recognised","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Claude Code now recognises errors about repository trust and session elevation\n\nClaude Code can now recognise tool errors saying a repository must be trusted or that a session has not been granted extra permissions\n\n**Unclear.** What Claude Code does when it recognises one of these errors, and when they can occur, is not shown.\n\n**What**\n\nClaude Code now recognises tool errors that begin with these tags:\n\n- `[repository_trust_required]`\n\n- `[repository_trust_declined]`\n\n- `[repository_trust_unavailable]`\n\n- `[session_not_elevated]`\n\nThe first three concern whether a repository has been marked as trusted. The last concerns a session, meaning one run of Claude Code, that has not been given raised permissions.\n\n**Why**\n\nThis suggests a flow in which some sessions must trust a repository or be granted raised permissions before certain tools work.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}