{"version":"2.1.277","anchor":"remotecloud-session-repository-trust-permission-answers-ca","canonical_anchor":"remotecloud-session-repository-trust-permission-answers-ca","heading":"Remote\/cloud session: repository-trust permission answers can now be named and flagged","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/remotecloud-session-repository-trust-permission-answers-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Remote\/cloud session: repository-trust permission answers can now be named and flagged\n\nRemote\/cloud repository-trust permission answers can now be named and flagged as user rejections\n\n**What**\n\nWhen a remote or cloud session responds to a permission request for the `confirm_repository_trust` tool, and the `config.nameRepositoryTrustAnswers` setting is turned on, the response is now annotated with the tool's name, the same way allowed responses were already annotated elsewhere via `nameToolOnPermissionAllow`. A denial of this request can now also carry a `decisionClassification` of `user_reject`.\n\n**Why**\n\nThis gives remote and cloud sessions more detailed information about repository-trust permission decisions, including explicitly marking a denial as a deliberate user rejection.\n\n- Area: Cloud Sessions\n- Names: `config.nameRepositoryTrustAnswers`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}