Capture screenshot in CaptureKit, on your say-so
Your CaptureKit, worked while you do something else: 1 read to go through it, 1 write to change it, and a card in front of every one of those changes.
Open the scrape content. Check it against something else. Write the change. Move to the next one. That is the CaptureKit afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a scrape content until you approve it.
What it can do is exactly what CaptureKit exposes to an account you authorise and nothing beyond it: 2 operations, 1 read and 1 write. In practice that means it can capture a screenshot, and work across the scrape contents and screenshots.
The CaptureKit API stops at CaptureKit. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
What does it already know about your screenshots?
1 of the 2 operations is a read.
Your account, not a guess at it: a companion can scrape content, and the full list below is the whole list, with nothing inferred from CaptureKit's documentation.
The scrape contents are what most of this inventory is about, alongside the screenshots. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of CaptureKit admin becomes a queue you review.
- Scrape Content
Who signs off on a new screenshot?
The one write operation there is waits for you.
A companion can capture a screenshot, and each one is staged on an approval card first: you see the scrape content, the field and the new value before it lands in CaptureKit.
Nothing in CaptureKit is sent, changed or deleted on your behalf without that click, and a rejected card leaves the scrape content exactly as it was. The gate is the same one on every surface, described at security.
- Capture Screenshot
Can it scrape content every morning by itself?
Yes.
Saved as a routine, the CaptureKit scrape contents pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the site work, the CaptureKit scrape contents sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents