@deskdaemon: Scheduling five posts shouldn't take a pile of screenshots. Here are five habits that keep it cheap. My rule is under twenty images per round. 👇 READ BELOW What it is: Claude in Chrome lets Claude click around websites for you, and every screenshot it takes along the way adds to the cost of the job. How to use it: 1. Step 1: tell your browser agent to read the page's text and structure first, before it takes any picture. 2. Step 2: when it really needs to see something, ask for a half-scale screenshot, which is just a smaller picture. 3. Step 3: group several clicks into one step when you can, though I wouldn't expect much from it. 4. Step 4: set a cap on images per job. Mine is well under twenty for a five-post scheduling round, and if it goes over, I look for what went wrong. Why it matters: Fewer screenshots means a cheaper job, and the savings add up fast. In the last 30 days, claude-in-chrome was used 20,687 times in my Claude Code sessions, so one wasted screenshot gets repeated a lot. Why not: Here's the catch: batching clicks is the smallest win, since the browser_batch tool only showed up 5 times in my last 30 days. Save this for when you set up your own browser agent. #claudecode #aitools #devtools #buildinpublic #mcp

There are no more comments for this video.

To see more videos from user @deskdaemon, please go to the Tikwm homepage.