{"version":"2.1.235","anchor":"permission-prompts-withhold-approval-when-the-preview-cannot","canonical_anchor":"permission-prompts-withhold-approval-when-the-preview-cannot","heading":"Permission prompts withhold approval when the preview cannot be rendered in full","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/permission-prompts-withhold-approval-when-the-preview-cannot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Permission prompts withhold approval when the preview cannot be rendered in full\n\nPermission prompts now withhold approval entirely when a tool input can't be shown in full, rather than half-rendering it\n\nConsent dialogs no longer render tool input on a best-effort basis. A shared preview builder now returns either a full render or a withheld result, withholding when the value exceeds the grapheme\/unit budget, exceeds the element budget, or would otherwise come back containing an elision marker. When withheld, the dialog shows a marker in place of the command or URL, and the \"always allow\" and suggestion options are suppressed, leaving only one-time approval.\n\nThe unknown-tool and stub preview renderers now throw rather than half-render, with errors like \"stub preview cannot render an over-bound parameter\" and \"unknown-tool stub cannot render parameters\". The old best-effort renderer that caught errors and logged \"Error rendering tool use line\" has been removed. This applies to everyone.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}