profile

Lenny’s AI Builders

i’m Lennox. i sift through AI Twitter and share one thing i tried with ChatGPT. for people making products, content and useful systems. five emails a week, with a weekly option.

feedback becomes software

one of my thumbnails had logos that looked pasted on. i said so. the next batch looked better. i wanted the fix to stick for the next job too.

​

the useful move is small: find the rule that made the mistake, change that rule, then check the next result.

​
13:01 in the full episode - the thumbnail Lennox was correcting.

​

​

why this matters

a chat can say “i’ll remember.” your next job may start in a new chat. the fix needs a home - the one skill, rule or module that owns that part of the work.

that gives you three useful things:

  • less repeating yourself. the next run can read the changed rule.
  • a smaller fix. one thumbnail note does not rewrite every part of your workflow.
  • a check you can see. the next output either has the same problem or it doesn’t.

copy this prompt

​

replace [correction] with the exact thing you saw. “the logos look pasted on” is useful. “make it better” makes the next agent guess.

​Illustration of a mistaken rule being moved from a crossed-out folder to a corrected folder, showing how feedback changes the one instruction that caused the error.
LENNY'S AI BUILDERS / LAB 0004
LAB remember this: [correction]. zoom out first. find the one skill, rule, or module that owns the behavior. show the smallest before/after change, apply it there, and prove it on the next run. keep one-off feedback scoped to this job.

do it in five steps

  1. name one mistake you can point to in the work.
  2. find the instruction that controls it. if the note is only for this job, keep it here.
  3. read the before and after. make sure the new rule fixes your note without adding things you never asked for.
  4. save the change in that instruction, not only in the chat.
  5. run the job again and look for the same mistake.

the test is the next output. a saved rule on its own proves nothing.

the rest of this LAB

seven stories led to the practical. Jev showed a narrow browser task. CUA-S1 split form answers from the clicks. a handoff file helped the next chat pick up a long job.

​

Anthropic reported Claude led 26% of its measured AI research work, with none of that work fully autonomous. OpenAI announced limited access to Astra for Law.

​

i also talked about the Codex reset promise and a proposed way to carry agent skills between apps.

​

these were the source states shown or discussed in the recording on 20 September 2026, not a claim that every promise or demo has since shipped. the legal job forecast is my opinion. the thumbnail fix is an artwork result, not a business result.

sources

more to watch or use

the full notes are free to read. joining the email list is optional.

​LAB 0004 video frame at 13:23 showing two revised illustrated thumbnails after Lennox corrected the earlier logo treatment, with Lennox speaking beneath them.
13:23 in the full episode - the next thumbnail batch after Lennox’s feedback.

​

​

​