Does my client need an account to leave feedback?

No. The review link is the authorization by itself: whoever opens it can read the review and comment. A guest is asked for a display name and nothing else, and their own comments stay editable because ownership is proven by a token stored in their browser rather than by a login. Accounts exist on your side of the review, for the people who need the dashboard, the projects and the statuses.

Which of the three ways in should I start with?

The shared review link, unless the page needs a login, because it is the only one with nothing to install anywhere. Add the Chrome extension when the round reaches screens behind authentication or a builder's preview. Add the widget when feedback keeps arriving after the round is meant to be closed.

Can Writhink review a page that is behind a login?

Yes, with the Chrome extension rather than the shared link. The extension annotates the page in your tab, so anything you can reach after logging in you can also comment on, including admin screens, staging environments with auth, and localhost. It is Chrome only.

What does the generated prompt actually contain?

Every comment, rewritten clearly and deduplicated, grouped by page and by element, with priorities set. Each item keeps its pin metadata and the URL of its screenshot so the assistant knows which element it refers to. Items that stayed ambiguous are flagged as unclear instead of being guessed at, and the prompt closes by asking the AI to draft replies for those.

Does it integrate with Jira, Slack or Webflow?

No. Writhink has no native integrations with project trackers, chat tools or site builders, and no plugin or app in anyone's marketplace. Feedback leaves two ways: the generated prompt — copied, or downloaded as a .md, and pasted into any AI assistant — or the MCP server if your AI client can connect to one.

Can I use it on a site I did not build?

Yes. Any page with a URL Writhink can load works through a review link with nothing installed anywhere, which is the usual setup when you are auditing somebody else's site. If the page needs a login, the person reviewing uses the Chrome extension instead.

Website feedback

Every comment on your site, in one place, ready for your AI

Writhink collects feedback on a live website the way people actually give it: by pointing at the thing they want changed. You share one link, your client pins a comment on the exact element, and Writhink turns the whole pile into a single prompt you can paste into ChatGPT, Claude, Cursor or whatever else writes your code. This page is the overview: the three ways feedback gets in, the one question that decides which of them a given page needs, and what comes out at the end.

Start for free

No credit card. Your client doesn’t need an account.

From a URL to a prompt your AI can use

Five steps. Nothing in the middle asks your client to learn anything.

Step 1
Point Writhink at the page
Paste the URL of the site you want reviewed: a staging build, a client preview, a page that is already live. Writhink serves it through its own proxy so a comment can be attached to an element on it. If the page sits behind a login, you use the Chrome extension instead and skip the proxy.
Step 2
Send one link
Your client opens it and types a display name. That is the whole onboarding: no account, no password, no email address, nothing to verify. The link itself is what grants access.
Step 3
They pin instead of describing
Each comment lands on the element it is about, and arrives with its page, viewport and screenshot already attached. Your client can add up to five files of 10 MB each, reply in a public thread, and edit or delete their own comments. With live collaboration turned on for the project, you see who else is in the review and where their cursor is.
Step 4
You work the list
Every item moves through four statuses: open, in progress, in review, resolved. Replies are public, so answering inside Writhink answers the client. Email digests tell your team when new comments have come in.
Step 5
Generate the prompt
Writhink reads every comment, rewrites the vague ones without inventing requests, merges duplicates, groups them by page and element, sets priorities, and produces one prompt to paste into your assistant.

Three ways feedback gets in

Pick per project. Most teams end up using two of the three.

Method	Use it when	What it needs
Shared review link	The page has a URL Writhink can load: a public site, a staging build, a client preview	Nothing on your client's side. They open the link and comment.
Chrome extension	The page cannot be loaded by a proxy: anything behind a login, a builder's preview or editor, a staging environment with auth, localhost	Chrome, with the extension installed by whoever is reviewing. Chrome only, no Firefox, Safari or Edge build.
Embedded script widget	Feedback should be available all the time on your site or your client's, with no link to send	One script tag on the page. It carries a Powered by Writhink badge.

All three land in the same project, so a comment left through the widget and a comment left through the extension sit in the same list, with the same statuses and the same export.

The question that decides which way in you need

Can a proxy fetch this page without logging in? That single question sorts almost every project, and it is worth answering before you promise a client a link. A shared review link works by having Writhink fetch the page server-side and serve it from its own domain, so pins can be attached to the elements on it. Whatever that fetch gets back is what your client will see.

If anyone holding the URL can reach the page, the answer is yes: a live marketing site, a public staging build, a deploy preview with a shareable URL, a demo you put up for the client. Send the link and nobody installs anything, on either side.

If reaching the page needs a session, the answer is no, and no amount of configuration changes it. That covers anything behind a login, an app screen that only exists after authentication, a password-protected preview, the editor or preview mode inside a site builder, a storefront hidden behind a store password, and localhost, which is not on the public internet at all. In each of those the proxy's fetch comes back as a login wall. Use the Chrome extension instead: it annotates the page in the tab you already have open, logged in as you, so anything you can reach you can pin on.

Two consequences catch people out. The extension is installed by whoever is doing the reviewing, so if your client has to comment on a logged-in screen, they need Chrome and the extension too, not just you. And the embedded widget sidesteps the question entirely, because the script runs inside the page itself rather than through a proxy, which makes it the option when the site is yours or your client's and you can add a tag to it.

What you get out

The output is a prompt, not a report. Writhink reads the whole set of comments, including the ones your client dashed off between meetings, and rewrites them into clear instructions without adding requests nobody made. Duplicates are merged. Items are grouped by page and by element, and each one keeps its pin metadata and the URL of its screenshot, so the assistant reading the prompt knows which element, on which page, at which width.

Every item carries its pin and an anchor to the element it was dropped on, the page URL, the viewport it was left at, the device type, an automatic screenshot and its reply thread. The full list of what a comment stores, and what happens to that anchor when the page changes underneath it, is on /visual-feedback-tool.

Anything still ambiguous after the rewrite is not guessed at. It is marked unclear and left for you to ask about, and the prompt ends by asking the AI to draft replies for those items so you can send them straight back to the client. Generation runs on Claude Haiku in production.

If your AI client speaks MCP, skip the copy and paste

Writhink runs a remote MCP server at mcp.writhink.com. Any MCP-compatible client can connect to it: Claude Code, Claude Desktop, Cursor and others. In Claude Code the command is `claude mcp add --transport http writhink https://mcp.writhink.com/mcp`, and the per-client setup notes live at /mcp.

What changes is not what the agent can do, it is who does the fetching. Instead of you generating a prompt and pasting it, the agent asks for a project's open comments and gets them with their pin context and screenshot URLs attached, works through them, and then closes the loop from the same session: the client gets a reply in their own thread and the item's status moves, without anyone opening the Writhink dashboard to record it.

It signs in as you over OAuth 2.1, so it reads exactly what your account reads, one active organization at a time. The seven tools it has, and what each one is allowed to touch, are set out on /visual-feedback-for-ai-agents.

Whether this is the right tool for you

Writhink fits when

You build websites or web apps for clients who are not developers
An AI assistant writes most of the fixes and you want its input to be precise
Feedback arrives today as voice notes, screenshots and long email threads
The person reviewing must have zero setup: no account, no install, no training
You need the comment tied to an element, not to a paragraph of description

Look elsewhere when

You need a Jira, Linear, Slack, GitHub or site-builder connector. Writhink has no native integrations with anything
Your reviewers are on Firefox or Safari and the page is behind a login. The extension is Chrome only
You want session replay, video recording or live chat with the client
Procurement requires SOC 2, ISO 27001 or SSO
You need a contractual uptime or support response guarantee

Before you count on it

The embeddable widget carries a “Powered by Writhink” badge. The white-label add-on that removes it is announced but not purchasable during the beta, so today the badge stays.

Writhink is in open beta: everything described here is available and free, no credit card. Paid plans are announced but not purchasable yet. The one limit that applies today is five AI prompt generations a month per organization.

FAQ

Questions people actually ask

Does my client need an account to leave feedback?: No. The review link is the authorization by itself: whoever opens it can read the review and comment. A guest is asked for a display name and nothing else, and their own comments stay editable because ownership is proven by a token stored in their browser rather than by a login. Accounts exist on your side of the review, for the people who need the dashboard, the projects and the statuses.
Which of the three ways in should I start with?: The shared review link, unless the page needs a login, because it is the only one with nothing to install anywhere. Add the Chrome extension when the round reaches screens behind authentication or a builder's preview. Add the widget when feedback keeps arriving after the round is meant to be closed.
Can Writhink review a page that is behind a login?: Yes, with the Chrome extension rather than the shared link. The extension annotates the page in your tab, so anything you can reach after logging in you can also comment on, including admin screens, staging environments with auth, and localhost. It is Chrome only.
What does the generated prompt actually contain?: Every comment, rewritten clearly and deduplicated, grouped by page and by element, with priorities set. Each item keeps its pin metadata and the URL of its screenshot so the assistant knows which element it refers to. Items that stayed ambiguous are flagged as unclear instead of being guessed at, and the prompt closes by asking the AI to draft replies for those.
Does it integrate with Jira, Slack or Webflow?: No. Writhink has no native integrations with project trackers, chat tools or site builders, and no plugin or app in anyone's marketplace. Feedback leaves two ways: the generated prompt — copied, or downloaded as a .md, and pasted into any AI assistant — or the MCP server if your AI client can connect to one.
Can I use it on a site I did not build?: Yes. Any page with a URL Writhink can load works through a review link with nothing installed anywhere, which is the usual setup when you are auditing somebody else's site. If the page needs a login, the person reviewing uses the Chrome extension instead.

Start

Send one link. Get feedback you can build from.

Your clients comment right on the page — no account, no screenshots, no voice notes. Writhink sorts the comments and writes the prompt for your AI.