{"version":"2.1.232","anchor":"dedicated-status-text-when-an-agent-is-resumed","canonical_anchor":"dedicated-status-text-when-an-agent-is-resumed","heading":"Dedicated status text when an agent is resumed","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/dedicated-status-text-when-an-agent-is-resumed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Dedicated status text when an agent is resumed\n\nResuming an agent now prints its own \"Resuming agent\" or \"Resumed agent\" message.\n\n**What**\n\nResuming an agent now produces its own message: \"Resuming agent <id>\" when there is no result yet, or \"Resumed agent <id>. Result:\" with the agent's output, falling back to \"(no text output)\" when the agent produced none. Neither phrase existed before.\n\n**Details**\n\n- The helper that builds these strings is new; which resume paths use it is not settled in the code read.\n\n**Evidence**\n\n`(no text output)`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}