Fixit

The business and the pain

Anyone who has built a site for a client knows the loop: a WhatsApp screenshot with “move this a bit left”. Which this? Then three rounds of “which page? mobile or desktop?”, and finally ten comments scattered across email, WhatsApp and phone calls. No status, no tracking, no source of truth.

What the system does

The client gets a link, clicks the actual element on the live site, and types a comment. The system captures a screenshot, a precise element anchor, and even the source-file path of the component. From there the feedback flows over MCP straight to the AI coding agent: it pulls the next item, fixes the code, attaches a commit, and the item is marked resolved. When everything closes, the client gets a summary email in Hebrew. Not a single phone call in between.

The details that prove deep specification

• The client’s click is translated into a source-file path through React Fiber. From a pixel on screen to a file in the editor, in one step.
• The element anchor is stored in five layers (selector, XPath, text, relative position, pixel), so it survives even after the page changes.
• 12 MCP tools designed around an agent’s workflow rather than database tables: next_to_fix picks what’s next, attach_commit closes the loop, and session summaries come out in plain Hebrew.