The working notes behind Uoink.
Hooks, corpus workflows, agent memory, local-first tradeoffs, and the product decisions underneath the launch.
- loop engineering / agent-dev
Loop engineering: what Boris Cherny and Claire Vo agree on
Loop engineering is designing loops that let an AI agent run a job on its own and check its work. Where Boris Cherny and Claire Vo agree, with receipts.
- creator / hooks
The 9 Hook Types Every Creator Should Recognize
Uoink's taxonomy for reading the first seconds of a YouTube video like a system instead of a vibe.
- creator / research
How to Find Your Channel's Overperformer Pattern
Use your local Uoink corpus to see why specific uploads beat the channel baseline.
- agent-dev / mcp
Why Your AI Agent Should Have a Corpus
Generic agents guess. Corpus-grounded agents search your actual sources before they write.
- privacy / architecture
Local-First, No Uoink Cloud: What It Costs Us
A plain accounting of the privacy choice: Own the disk. Skip the subscription.
- writer / corpus
How to Write a Script Grounded in Your Corpus
Turn saved videos, pages, comments, and style anchors into a script draft with source gravity.
- writer / twitter
Tweet What You Learned from a YouTube Video
A workflow for turning a useful video into a credited, specific thread without link-share mush.
- capture / agent-dev
Uoink Any Page: Our Crawl4AI Fork
How universal page capture works inside the local helper, and why allowlists matter.
- writer / voice
Voice DNA: How Uoink Writes
The house rules behind Uoink's writing surfaces: short paragraphs, concrete claims, zero AI slop.