Let your AI capture for you (Automations)
Ask your AI tool to save things from websites into your folders: a section with its real code, a whole page, a screenshot, a site’s colors or its fonts. Nothing happens until you approve. Then your PocketUI extension opens each page in Chrome and saves it the way you would.
Steps
- 1
Connect your AI tool to PocketUI and turn on Add to your library.
Setup: Use your library with AI. Automations use the same switch as every other save your AI makes.
- 2
Ask in your own words, for example: "Save the pricing sections of stripe.com and linear.app into @Pricing refs."
- 3
Open Automations (your AI gives you the link) and check the request: the folder, and what it captures on each page.
Change the folder, edit a page, or click Reject on what you don’t want, before approving.
- 4
Click Approve. With Chrome open and the PocketUI extension on, it starts at once.
The first time, a small window asks to let PocketUI open the pages your AI chose. Click Allow.
- 5
Watch each page being captured on the canvas, then find the saves in your folder.
What you get
- Saves exactly like the ones you make yourself: code you can export, screenshots, colors and fonts.
- A record of every request under Past runs, with a picture of what it saved.
What your AI can ask for
Everything is measured on the real page in your Chrome, so it is what the site actually shows, not what your AI guesses from its code.
| Ask for | What gets saved | For example |
|---|---|---|
| A section | Its real HTML and CSS and a screenshot, ready to export to code, Figma and page builders | "Save the hero of framer.com into @Heroes" |
| A whole page | The whole page as code, with a screenshot | "Save the whole homepage of cal.com" |
| A screenshot | An image of the whole page, or of one section | "Take a screenshot of raycast.com for my @Moodboard" |
| Colors | The site’s palette: up to 6 colors, saved together | "Save the colors of linear.app into @Dark UI" |
| Fonts | The fonts the site uses (up to 4), with their weights and sizes | "Save the fonts of stripe.com into @Type" |
How it finds the right section
Your AI names a section in words: "hero", "pricing section", "FAQ", "footer", or the heading the section starts with. PocketUI finds it from how the page is built, what is in it (prices, questions, quotes, logos) and its heading, so it works on sites that don’t name their sections.
Screenshots leave out the site’s menu bar, cookie banners and chat bubbles, and a section taller than the window is captured whole.
When it asks you: Needs you
If PocketUI isn’t sure which part of a page your AI meant, it saves nothing and that branch turns amber: Needs you. Click Pick it and the page opens in a new tab. Move the mouse until the right section is highlighted (↑ and ↓ make the highlight bigger or smaller), then click it. It saves into the right folder and the tab closes. Press Esc to stop: it waits for you again.
Your AI can answer it too, with the exact CSS selector of the section. It is then captured again with it.
Past runs
Finished requests move to Past runs: how each one went (approved, captured, where it saved) and a picture of everything it saved. Click Show workflow to see the whole run. A capture that failed has Retry, and for a section, Pick it.
Things to ask
- "Save the pricing sections of stripe.com, linear.app and vercel.com into @Pricing refs, then build our pricing page from them."
- "Save the colors and fonts of linear.app into @Dark UI."
- "Take screenshots of the homepages of framer.com and raycast.com for @Moodboard."
- "Save the FAQ of notion.com/pricing and the footer of supabase.com."
Limits
- Every item saved counts as one save on your plan, like a save from the extension: a section, a page or a screenshot is one, a palette one per color (up to 6), fonts one per font (up to 4).
- Up to 20 captures in one request, and 50 waiting at once. Requests nobody approves within 14 days expire.
- Public pages only, never anything behind a login.
- Captures run in your own Chrome, so your computer has to be on with the extension signed in. Approved captures wait until then.
If it does not work
- "PocketUI extension not found on this page": open Automations in Chrome with the extension on, signed in to the same account, and refresh.
- Nothing happens after Approve: look for the small window that asks to let PocketUI open pages, and click Allow.
- "The page took too long to load": click Retry.
- "This page only uses system fonts": the site uses fonts like Arial or Helvetica, so there is nothing to save.
Tips
- Keep the Automations tab open while it runs to watch each page being captured, live.
- Ask for the colors and fonts of the sites you saved sections from: your AI then has the whole style to build with.