Summary and audience
What the task is and who it's for.
Polysh for agents is in early access. Your coding agent records the demo, and Polysh finishes it. Join the waitlist →
Polysh writes numbered steps from your recording, each with a checked screenshot of the screen you acted on, and blurs private details.
Make a guide, a video, or both in one export.
A demo is for watching. A guide is for following along with the product open.
What the task is and who it's for.
Anything to have ready first, such as access to Reports.
What to do, what you should see next, and an optional tip.
Side remarks become notes, and compared options sit side by side.
A missing screenshot is better than a wrong one.
Polysh splits the walkthrough into steps and links each to the click that performs it.
It takes candidate frames around each click, never from parts you trimmed.
A vision model keeps a frame only if it clearly shows that step.
If none passes, pick a candidate yourself or keep the step as text.
The check looks for names, email addresses, and account details in every screenshot.
Until someone on your team reveals it.
People outside your workspace never see it on a shared page or in its PDF.
Polysh asks whether to include flagged screenshots.
Edit the title, summary, and any step. Drag to reorder or delete.
Pick another candidate frame, or remove it.
Every edit is saved as a new version. If someone else changed the guide first, Polysh loads theirs before you overwrite it.
If the script changes, the guide flags it and offers to remake it.
Each language's guide is written from that language's reviewed script, so the guide and the video say the same thing.
Tick the languages you want and choose guides, videos, or both.
Hindi, Tamil, Japanese, and the rest render in their own script, on the page and in the PDF.
Send a web page with its own link, or save a PDF with selectable text. The link stays the same when you remake the guide.
Invited people confirm with an emailed code, or open it to anyone with the link.
Set an end date, turn off PDF downloads, and see who viewed or downloaded.
Most teams make both from one recording.
| A guide is better when… | A video is better when… |
|---|---|
| People follow along with the product open | People want to see the whole flow first |
| They need to scan back to one step | The order and pace matter, such as a launch demo |
| It lives in a help article or SOP | It plays in onboarding, release notes, or a course |
| Some readers can't play audio | Seeing the motion explains it faster than words |
No. Tick "Step-by-step guides" when you export.
Yes. Untick videos at export and you use no video credits.
They're replaced for that language, so Polysh asks you to confirm first.
Yes, as editors on the share link. They can edit text, reorder steps, and swap screenshots, but not remake or delete the guide.
Not directly yet. Share it as a page or save a PDF, and tell us which help center you use.
Drop numbered step badges that match the order of your written instructions.
Open toolMark up a screenshot with every kind of annotation in a single editor.
Open toolCover secrets in a screenshot with solid boxes that leave nothing to read.
Open toolGet indented HTML source from your Markdown, ready to paste into a CMS or save.
Open toolMake both from your next recording. Founding teams keep their rate.