Tag
Developer Tools
4 posts
Stop Letting Browser Agents Improvise Every Click. Use AI to Heal Playwright Instead.
The best browser agent architecture is usually not an agent driving every step. It is a deterministic Playwright workflow that uses AI only when the page changes or the script fails. That keeps normal runs cheap and debuggable while still giving you a way through the web’s inevitable mess.
The AI Pull Request Manifest: The One Page That Makes Agent Code Reviewable
The worst AI pull request is not a bad diff. It is a diff nobody can explain six weeks later. A short manifest, written before the agent starts, turns review from archaeology into a check against a concrete promise. Here is the format and policy I would put in every repository.
Coding Agent Permissions: The Access Ladder I Use Before I Press Approve
Giving a coding agent access to your repository is not one permission. It is a stack of file, shell, browser, network, credential, Git, and production permissions that compound into something much bigger. Here is the access ladder I use to keep agents useful without handing them my whole life.
llms.txt Does Not Get You Cited. Here Is What It Is Actually For.
The most honest answer to "does llms.txt work?" is yes for developer documentation, no for AI-search rankings. I read the crawl data, checked what the answer engines support, and made a list of the work that is worth doing before you ship another text file.