ChatPRD Product Intelligence, 131 photos, and Monday’s podcast
Spent today on Product Intelligence in ChatPRD: connecting sources and making it easier to get useful insights out of them. Also worked through a bug in prototype chats. In between, I had Codex edit 131 event photos in Lightroom, clear space on my very full laptop, and get Monday’s How I AI posts scheduled in Sanity. A mix of product work and all the other stuff that still needs to get done.
Bulk edit crops, lighting, and red-eye in Lightroom with Codex computer use
I had 131 event photos to clean up. I opened them in Lightroom and asked Codex to straighten the shots, improve the crops, and fix red-eye. It used computer use, looking at the screen and clicking through the desktop app.
- Adjust the lighting across the batch so the photos have a consistent starting point.
- Review each photo individually for crooked horizons, awkward crops, and red-eye. Those decisions need to be made photo by photo.
- Check the whole set after the edits, keeping the changes reversible in Lightroom.
It reviewed all 131. I could hand off the repetitive editing while keeping the photos in the app where I’d normally review them.
# Photo polish
Use computer use to work in the Lightroom desktop app I have open. Review the selected event photos, keeping edits reversible.
## Establish the lighting
Inspect a few representative photos first. Adjust exposure, highlights, shadows, and white balance to suit the batch. Check automatic corrections before accepting them—direct-flash portraits can become too bright.
If the photos share similar lighting, copy only the appropriate light/color adjustments across them. Do not copy crop settings or localized eye corrections. Revisit photos whose lighting differs from the rest.
## Check each photo
Move through the selection one photo at a time. Straighten against visible reference lines and inspect the result. Crop awkward edges or excess headroom without cutting people out. Zoom in enough to check red-eye, apply corrections where needed, and inspect the eyes afterward.
Keep track of which photos have been reviewed so none are skipped. Do not claim every photo was individually adjusted if only shared settings were applied.
## Finish
Review the edits and check Lightroom's save/sync status. Report what changed, the number reviewed, and anything still unfinished. Do not export or share unless I ask.
Free up disk space by clearing Git worktree caches with Codex
My laptop was almost out of space. Git worktrees let me work on several branches at once, but each checkout can accumulate its own dependencies and build files. One Next.js cache alone was taking up 18.9 GiB.
- I asked Codex to use the terminal to find the biggest folders and explain what they contained.
- It checked Git status and running processes to separate my code and active work from files the tools could recreate.
- I picked what to remove, and Codex cleared those cache and dependency folders.
That recovered 24.7 GiB. The worktrees and uncommitted changes stayed; dependencies in the cleaned folders would need reinstalling. Having an agent investigate the folders first saved me from guessing what was safe to delete.
# Make room, keep the work
Help me recover disk space in the repositories and worktrees I select.
## 01. Look before touching
Measure disk usage. Identify large generated caches and reinstallable dependencies. Check Git status, ignored files, and active processes. Keep source files, local work, credentials, and databases out of the cleanup list.
## 02. Make the plan concrete
Show the exact paths, their sizes, what each contains, and whether a running process uses them. Separate cache cleanup from deleting whole worktrees. Explain what will need reinstalling or rebuilding.
Ask me to approve the exact cleanup targets and any processes you need to stop.
## 03. Clean only the approved targets
Use the narrowest appropriate operation. Never expand a target to its parent directory or delete worktrees just because their caches are large.
## 04. Verify the result
Measure the space recovered. Confirm source files and uncommitted changes are unchanged. Report any stopped processes and what I need to reinstall before running a project again.
Schedule podcast and blog posts in Sanity with Codex browser use
A How I AI release includes the episode post and companion posts explaining the workflows from the conversation. Getting them all ready means finding the related drafts, checking their URLs, and scheduling each one. It’s a lot of clicking through the same CMS screens.
I gave Codex the episode and publish date, with Sanity already open in Chrome. Using computer use in that browser session, it found the three companion posts, cleaned up the URLs, and scheduled all four. I could delegate the release as one task instead of walking through each post myself.
# Schedule a podcast release
Use browser or computer use in the CMS session I already have open. Help me prepare and schedule the episode and related posts I select.
I will provide the episode, publish date, time, and time zone. Find its companion posts and handle the repetitive editing and scheduling work across the set.
## 01. Identify the release
Confirm the exact documents, publication date, time, and time zone. Check the current draft and schedule status of every document. Do not guess which similarly named post belongs in the release.
## 02. Review the content
Check titles, slugs, internal links, summaries, images, and required fields. Flag anything missing or inconsistent. Distinguish a saved draft from a scheduled snapshot.
## 03. Check the version that will publish
Make sure the scheduled version contains the intended draft changes. If the CMS keeps an earlier snapshot, show me what must be replaced and preserve the latest draft.
Ask for approval of the exact content and schedule before creating or replacing publication schedules, unless I have already approved them in this session.
## 04. Read it back
After the authorized scheduling action, verify each document's saved slug, scheduled version, publication date, and time zone. Report scheduled and published states separately. Note any links that will only work after publication.