{"version":"2.1.242","anchor":"terminal-output-is-routed-through-a-rendering-hook-that-noth","canonical_anchor":"terminal-output-is-routed-through-a-rendering-hook-that-noth","heading":"Terminal output is routed through a rendering hook that nothing currently answers","tier":"soon","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/terminal-output-is-routed-through-a-rendering-hook-that-noth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Terminal output is routed through a rendering hook that nothing currently answers\n\nNine parts of the terminal ask a hook before drawing, but nothing can answer yet.\n\n**What**\n\nNine parts of the terminal interface now ask a hook whether it wants to draw them before drawing them the normal way: user and assistant messages, tool calls and results, turn duration, notices, the spinner, the session mode line and the question prompt. Only a plugin hooks module can answer, and those are disabled in this build, so everything renders exactly as before.\n\n**Details**\n\n- A hook may return a small tree of boxes, text and basic formatting with hex colours; it is rebuilt into real terminal elements, and if the returned tree fails validation Claude Code falls back to its own drawing.\n- The whole path short-circuits when no loaded hook module handles the render event, which is always the case while `tengu_plugin_hooks_modules` is off.\n\n**Evidence**\n\n`useRenderInput`\n\n- Area: Terminal UI\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}