Your client points at the problem. You get what you need to fix it.

A small button on the site you're building. Your client clicks what's wrong and writes a sentence; you get everything you'd otherwise have to ask for.

Free while it's new. Your clients install nothing and never need an account.

What the email leaves out

The page, the browser and the error are what you'd write back to ask for. The report already has them.

How it arrives now

Re: Re: Fwd: website changes

Ana to me, yesterday at 21:04

Hi,

the booking button isn't working?? Also Tomaž says the page looks strange on his computer, can you check.

I put everything in the PowerPoint again, slides 9 to 12 are new.

Sent from my iPhone

lipa website changes v4 FINAL.pptx23 MB

What the report has already answered

Which button?
The button “Book a table”a.btn.book
On which page?
The home page, reached from the menulipa.example/
What were they using?
A 1440 px wide laptop, Chrome 140, macOS
Did the page complain?
TypeError: Cannot read properties of null (reading 'showModal')
Did a request fail?
GET /api/slots 500

What your client has to do

  1. Open the link you sent

    Make a review link and send it however you already talk to them. Only people with the link see the button.

  2. Click what's wrong

    One click on the button, one click on the thing. They can draw on it or hide something private.

  3. Write a sentence

    In their own words, with no account to make. If they close it halfway, what they wrote is still there when they open it again.

Your side of it

Reports land on a board: a list or six columns, with filters, search and keyboard shortcuts. It's built for one person with a handful of clients, so there's nothing to configure.

You work in your words, they read theirs

You move a report to “Ready for check”. Your client gets an email that says “Please check”. Notes you mark as internal stay internal.

Status names on your board, and what your client reads
On your boardYour client reads
NewReceived
AcceptedPlanned
In progressWe're on it
Ready for checkPlease check
DoneFixed
Won't doNot planned

Your coding agent can read it too

Copy as prompt puts the report into one block for any agent. Or connect Claude Code or Cursor over MCP, and it can read open reports, fix one and mark it ready for your client to check.

How to connect an agent

They check it where they found it

“Please check” arrives as an email with one button. It opens their own site with the fixed part outlined, and asks one question.

“Yes, fixed”
The report moves to Done, and you get an email saying so.
“Still broken”
It's back on your board, with what they wrote about it.

One script tag

Paste it before the closing body tag, whatever the site is built with. The install page turns green when it sees the widget load.

footer.php

<script
  src="https://cdn.client-screen.com/v1/widget.js"
  data-key="pk_your_project_key"
  data-api="https://scintillating-civet-800.eu-west-1.convex.site"
  async
></script>

Read the install guide

About 4 KB
That's all that loads until someone clicks the button. The screenshot code comes after the click.
No cookies
And no tracking. It keeps two things in the reviewer's own browser: their review link's token, and a draft of what they were writing.
Its own shadow root
Your CSS can't reach the widget, and the widget's CSS can't reach your site.
Doesn't lose reports
With no connection, the report is kept in the browser and sent on the next visit.

Pricing

Free

Everything on this page is free while Client Screen is new. There are no plans to choose from and no card to enter.

Questions

Are the screenshots exact?

They're rebuilt from the page, not photographed, so now and then one comes out a little off. Embedded players and videos show as a placeholder, and a page that takes more than five seconds to capture goes without one. The element, the browser details and the error log don't depend on the screenshot.

Does it connect to Jira, Linear or Slack?

No. The board inside Client Screen is meant to be enough for one person. If your work lives in Jira, Marker.io and BugHerd do that well.

Is there session replay or screen recording?

Not yet. You get the pages the client visited on the way, the console and the failed requests, but not a video.

Can I add my team?

Not yet. It's one workspace, one person. Studios come later.

Does the widget use cookies?

No cookies and no tracking. It keeps two things in the reviewer's own browser: their review link's token, and a draft of what they were writing.

What if the client has no connection?

The report is kept in the browser and sent on their next visit.

Send your client a review link this week.

Sign in, make a project, paste one script tag.