Show the user your plan on a local web page instead of writing it out in chat. Call this BEFORE you start making changes, once you have decided on an approach. Send a short summary (max 3 sentences), up to 12 one-line steps, optionally a diagram of the intended flow, and optionally refs pointing at the files you plan to touch. Refs are pointers, not content: give a path and an 'anchor' string that literally appears in that file; the server opens the file itself. Returns a single line with the page URL - reply with that line only.

Show the user what you did on a local web page instead of writing it out in chat. Call this AFTER you have finished the work. The page also shows every file that changed since this session started, with per-line diffs, so do not describe your edits in chat - point at them. Send a short summary (max 3 sentences), the list of things done, optionally a diagram of the resulting flow, optionally refs (path + an 'anchor' string that literally appears in the file) marking spots worth reading, and optionally notes for warnings or leftovers. Returns a single line with the page URL - reply with that line only.

Draw a diagram on a local web page, without a plan or a report attached. Use this when the user asks how something works and the answer is a picture: a flow of steps, or the shape of a system. Hard limit of 9 nodes - if the subject needs more, call this several times: one overview diagram, then one per sub-flow. Never send colors, coordinates or SVG; the server does the layout and the styling. Returns a single line with the page URL - reply with that line only.