Comments and threads

Pins, widths, who a comment is for, and how a fix is confirmed.

A comment is pinned to one element of one page, at the screen width it was written at. Replies make it a thread; the thread is the unit of work — for the agent, for the team, and for the client who checks the result.

What a comment keeps

• The element and the text around it, so the pin finds it again after the page changes — even among cards that look alike.
• The width — desktop, tablet or a phone band — and the device and browser it was written on. A note about the phone layout stays on the phone layout.
• The copy of the site it was written on — live, staging or localhost. A thread belongs to the page's path, so the same page shows it on every copy of the site in the project; the bar marks one that began elsewhere, and the cabinet can filter threads by site.
• A type: General, Text, Bug or Motion.
• Who it is for: the AI agent, anyone, or one person in the project. The agent only picks up comments for the agent or for nobody in particular.
• Screenshots pasted into the comment or any reply, and pictures the agent files before and after a fix.
• What the page logged: errors in the console, uncaught errors and requests that failed in the ten minutes before, up to 20 lines — so the agent sees the 500 behind “the form does nothing”. Tokens, keys and passwords in them are masked before they leave the browser, and again on our side.

Clicking an element that already has an open thread says Already open here, with a link to it, so the same note is not left twice. Your draft waits while you read it.

How a thread moves

While an agent works on an open thread, its pin breathes and the thread says Codex is on it (or Claude, Cursor…). The agent takes a thread with notemend start and the mark goes when it resolves it — or after two hours, if the agent stopped. A second agent asking for the same thread is turned away.

Reopen sends a thread back to Open from either of the later states. A comment a person resolves themselves is confirmed at once.

Checking fixes

When fixes are waiting, the comments panel on the site offers Check. It opens each fixed thread in turn — on its own page, at its own width — with three choices across the top: Looks right, Reopen and Skip.

Into your tracker

An open thread in the cabinet goes to a tracker from its composer: Send to agent opens a GitHub issue for the agent installed in the project's repository, Open as a Linear issue fills in a new Linear issue, and Copy as an issue puts the same text on the clipboard for Jira or anywhere else — the words, the page and width, what the page logged, screenshots as week-long links, and the link back to the thread.

Into your channel

A project can post to a Slack or Discord channel — or any https address, as JSON — when a comment is pinned, when an agent fixes one, and when a person confirms a fix. Paste the channel's webhook in the project's Settings → Channel and press Send a test. Only the project's team sees the address.

Mentions and live replies

Type @ and a few letters in a reply to mention someone in the project; the thread lands in their Inbox. Replies written anywhere — in the cabinet, on the site, by the agent — appear on an open page within seconds.