Constructor for Chrome

Pin notes to what's wrong on your project's Stage and Prod sites: each lands in its Intake with a screenshot and what the page said.

Test your project's sites with Constructor. Turn on its Stage and Prod sites, start a session, and pin notes to what's wrong — on an element, or on an area you drag over. Each note lands in the project's Intake in Constructor with a screenshot and what the page said: the page and its build, your last steps, console errors and failed requests. Fields, emails and card numbers are masked in screenshots: always on Prod, on Stage unless you turn it off. Ask Foreman, Constructor's planning agent, about what you see, right on the page: he answers from the session — the failed request and its answer, the console's error, the build. When you are done, Build plan turns your notes into issues, each with its notes attached, ready for an agent to start on. Constructor for Chrome works only on the sites you turn on, each allowed in Chrome's own prompt, and sends nothing of a page until you act on it: Start session sends the page's address and the build it runs, and a note or a message what its chips show. It needs a Constructor account: constructor.works, or a tracker your organization runs.