{"version":"2.1.277","anchor":"taskoutput-removed-from-an-internal-tool-set","canonical_anchor":"task-output-max-length-now-derived-per-output-host","heading":"TaskOutput tool removed; task output is now read via the Read tool","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/taskoutput-removed-from-an-internal-tool-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### TaskOutput tool removed; task output is now read via the Read tool\n\nThe TaskOutput tool was removed; background task output is now read through the Read tool, and its max-length setting was retired\n\n**Unclear.** The finding does not say what effect losing access to TaskOutput from this specific tool set has for a user in practice.\n\n**What**\n\n- The TaskOutput tool has been removed. Its config field's description now says background task output should be read via the Read tool instead.\n\n- `TaskOutput` was dropped from the internal tool set used alongside Read, Glob, Grep, NotebookRead, Skill, AskUserQuestion, TaskCreate, TaskGet, TaskList, TaskUpdate, TaskStop, Agent, and TodoWrite.\n\n- The `TASK_MAX_OUTPUT_LENGTH` environment variable was dropped from the list of recognized\/passthrough settings.\n\n- The function that computes the maximum characters allowed for task output no longer reads a `taskOutputMaxChars` setting; it now derives the limit from the current output host\/target instead.\n\n**Why**\n\nThis consolidates reading background task output onto the Read tool instead of a separate TaskOutput tool, and moves the output-length limit from a fixed global setting to something derived from where the output is being read.\n\n- Area: Background Tasks\n- Names: `TaskOutput`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}