{"version":"2.1.275","anchor":"plugin-api-uilog-gains-a-to-destination-field","canonical_anchor":"plugin-api-uilog-gains-a-to-destination-field","heading":"Plugin API: ui.log gains a to destination field","tier":"use","area":"Plugin API","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/plugin-api-uilog-gains-a-to-destination-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Plugin API: ui.log gains a `to` destination field\n\nPlugin ui.log gains a to field to route output to the transcript or a debug-only log\n\n**What**\n\nThe `ui.log` operation, which plugins use to write log output, now accepts a `to` parameter that chooses where the text goes: either the normal visible UI log (\"transcript\") or a debug-only log line. Previously, `ui.log` always appended to the visible UI log.\n\n**Why**\n\nThis lets plugin authors send diagnostic or debug output to a separate debug log instead of cluttering the visible transcript that users see.\n\n- Area: Plugin API\n- Names: `ui.log`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}