Client feedback
Send a client a link, and they comment on the site itself: they select a passage, click Comment, and type. You read the notes in the console or the terminal, fix things, and resolve them. Nobody signs in, and nothing changes in your code.
Feedback is switched on per address. Turn it on for the address you send the client, and leave it off on your live domain. Real visitors never see the comment box.
slew feedback on staging.acme.nl
Feedback is on for https://staging.acme.nl — send that link; visitors select text to comment.
Read the comments with 'slew feedback'.
Without an address, slew feedback on uses the project's own <project>.slew.cloud address. That's the natural review link before launch.
Which address to use
| Address | Good for |
|---|---|
<project>.slew.cloud |
Review before launch, while the site has no domain of its own |
A branch domain such as staging.acme.nl |
Review after launch: the client sees the branch you're working on, the live site stays as it is |
| Your live domain | Rarely. Every visitor sees the comment box. The console asks you to confirm, and the CLI reminds you to turn it off again |
Each address keeps its own comments. Notes left on staging.acme.nl don't show up on acme.slew.cloud, because the two can serve different versions of the site.
Reading and resolving
slew feedback
acme.slew.cloud off
acme.nl off
staging.acme.nl feedback on branch staging
2 open comments on 'acme'
1. cmt_7Hk… — Sam · 11/11/2026, 10:02:11 · § Pricing · staging.acme.nl/pricing
> from €49 per month
This should be €59 since September.
2. cmt_9Qz… — Sam · 11/11/2026, 10:04:40 · staging.acme.nl
The logo looks blurry on my phone.
Resolve one with 'slew feedback resolve <comment-id>' (or 'all').
| Command | Effect |
|---|---|
slew feedback |
Addresses with their feedback state, then the open comments (--all includes resolved ones) |
slew feedback on [address] |
Put the comment box on an address (default: the slew address) |
slew feedback off [address] |
Take it off again. Comments are kept |
slew feedback resolve <comment-id|all> |
Mark comments as handled. A resolved note disappears from the page |
slew feedback reopen <comment-id> |
Bring a note back |
slew feedback rm <comment-id> |
Delete a note |
In the console, the project's Feedback tab has the same controls: a Turn on button and a Copy link button per address, and the comments with Resolve and Delete.
Each comment carries the quoted passage, the nearest heading and the page URL. A coding agent can act on it without the page in front of it.
How it behaves
- The widget is added by slew. On an address with feedback on, slew adds one small script to every HTML page it serves. Turning feedback on or off takes effect right away for new visitors; slew clears the CDN copies of that address. A browser that still holds a page it was allowed to cache shows the old version until that copy expires or the visitor reloads.
- Static sites and server apps. On a static site the comment box goes into every HTML file. On a server app (Next.js, Node and the like) slew adds it to every full HTML page the app sends, at the very end, so streamed pages keep streaming. HTML fragments (htmx, Turbo), JSON, assets, downloads and redirects are never touched. The box follows client-side navigation, so comments land on the page the visitor is looking at.
- Content-Security-Policy. The box is one script from your own origin (
/_slew/feedback.js). A policy that allows'self'scripts lets it through; a policy that only allows scripts with a nonce or hash, or uses'strict-dynamic', blocks it on that address. - Changed pages. When a passage someone commented on is no longer on the page, the note stays in the list, marked "passage not found".
- Password-protected sites keep feedback behind the same unlock screen. That's a good way to keep a review link private.
- Limits. A site holds at most 500 open comments; resolving notes makes room. One visitor can post 20 comments per ten minutes.
What is stored: the note, the optional name, the quoted text with a little surrounding context, the heading, the page path and the address. No IP address, no user agent.
HTTP API
| Method | Path | Description |
|---|---|---|
GET |
/projects/:name/feedback |
{ addresses: [{ host, url, feedback, branch }] }, the slew address first |
PUT |
/projects/:name/feedback |
Body { "enabled": true | false, "host"?: "<address>" }. No host = the slew address |
GET |
/projects/:name/comments |
{ addresses, comments: [{ id, host, path, url, body, author, quote, section, created_at, resolved_at }] }, oldest first. ?open=1 hides resolved ones |
PATCH |
/projects/:name/comments/:id |
Body { "resolved": true | false } |
DELETE |
/projects/:name/comments/:id |
Delete one comment |
Visitors post through the address itself (POST /_slew/feedback, JSON). That endpoint only exists on addresses with feedback on.
For a one-off page rather than a site, use a temporary share with --feedback.