Coding agents are now the default way to start any project
REA launched with an install line you paste into your coding agent, and the top skeptic comment asks how that beats telling Claude to set up Ghidra yourself. The Antiquity toolkit open-sourced a workflow for pointing a coding agent at archives, which found a forgotten meteorite and lost rhinos. A Lean paper claims autoformalization is practical in 2026, and a commenter translating papers says the results are shakier than that. An older thread has a 60-year-old developer saying Claude Code re-ignited his passion, with a 51-year-old engineer calling it the courage to go solo-founder.
The key bit: the product is increasingly a prompt, a workflow or a toolkit that sits on top of someone else's agent. That is cheap to ship and cheap to copy. The REA comment hits this directly. If a one-line instruction to Claude gets you the same environment, what are you selling?
The counterweight is trust in the output. Lean skeptics, and the commenters who refuse to run a vibe-coded Proton Drive client with their data, show the limit: verification is the scarce thing, not generation.
So what?
A thin wrapper around a frontier model is easy to clone and easy to dismiss. The defensible parts are verification, curated data, and a workflow that is hard to reproduce with a single prompt. Build those, and show your checks.
Read these
REA Reverse – Engineer Anything
Pointing AI at archives found a forgotten meteorite, lost rhinos, and more
What mathematicians should know about the Lean Theorem Prover: reliability & AI
Tell HN: I'm 60 years old. Claude Code has re-ignited a passion
Show HN: Proton Drive for Linux