{"version":"2.1.224","anchor":"replayed-sessions-no-longer-show-empty-command-output","canonical_anchor":"replayed-sessions-no-longer-show-empty-command-output","heading":"Replayed sessions no longer show empty command output","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/replayed-sessions-no-longer-show-empty-command-output","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Replayed sessions no longer show empty command output\n\nReplaying a stored session no longer shows blank assistant messages for empty command output.\n\n**What**\n\nWhen a stored session is streamed back, a local command whose output is blank once trimmed now produces nothing instead of an empty assistant message. Compact summaries are also now treated as synthetic entries, matching how meta and transcript-only entries are handled.\n\n**Evidence**\n\n`local_command`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}