{"version":"2.1.280","anchor":"modelfork-now-returns-structured-outcome-instead-of-a-bar","canonical_anchor":"modelfork-now-returns-structured-outcome-instead-of-a-bar","heading":"$.model.fork now returns structured outcome instead of a bare string","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/modelfork-now-returns-structured-outcome-instead-of-a-bar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### $.model.fork now returns structured outcome instead of a bare string\n\nInternal model-fork helper now returns a structured result instead of plain text or null\n\n**What**\n\nAn internal helper used for one-off background or utility calls to the model (\"forking\" a copy of an ongoing conversation to ask it something separately) now returns a structured result that distinguishes several outcomes: aborted, an API error (with status and error details), an empty reply, or a successful answer, plus token usage. Previously it just returned joined text or `null`.\n\nWhen there is no warm main-thread conversation available to fork from, it now returns a structured object with `isAnswered: false` and `reason: 'nothing-to-fork'` instead of `null`, with an updated log message.\n\n**Why**\n\nThis lets code calling into this helper tell apart different failure modes (aborted vs. an API error vs. an empty reply) instead of only seeing a missing result, which should make related bugs easier to diagnose.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}