List the LayerDock docks (sites) you have access to, with any codebase hints their owner declared (framework, source root, CMS). Call this to get a dockId — but note that list_feedback no longer requires one, so "what is open across everything?" is a single call.

List feedback pins. Omit dockId to see open work across EVERY dock you can reach — that is the one call that answers "what needs my attention?". Pass dockId to scope to one site. Returns a lean summary; call get_feedback for the full fix brief of the one pin you pick.

Get one feedback pin as a complete fix brief: WHERE it is (page URL, section, CSS selector, the component name when the framework exposed it), a SEARCH STRING that actually matches source (one contiguous run of literal text, not the element's whole innerText), WHAT the reporter wants changed, the SCREENSHOT as an image when one was captured, and the DEBUG state at the moment of capture (console errors and failed/slow requests, each stamped with how long before capture it happened). The brief tells you when a screenshot was NOT captured rather than sending you looking for one. Call this before changing any code.

Move a pin through the workflow: open, in_review, changes_requested, approved, resolved. Call this after you have actually made the fix. Your permission to set a given status depends on your role on the dock; the server rejects what you are not allowed to do.

Post a reply on a pin's thread. It is attributed to the person who owns this token AND labelled as coming via a coding agent, so the reviewer can tell your claim from that person's own — the server stamps both from the authenticated token. Do NOT sign the message text yourself; that is duplicated, and unlike the server-side stamp it is not something the reviewer can trust. Use this to say what you changed before resolving the pin, so a silent status flip does not leave them guessing.