Compare/pi-autoresearch vs Plain

AI tool comparison

pi-autoresearch vs Plain

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

P

Developer Tools

pi-autoresearch

Autonomous code optimization loop — edit, benchmark, keep or revert

Mixed

50%

Panel ship

Community

Paid

Entry

pi-autoresearch extends the pi terminal agent with an autonomous optimization loop: the agent writes a change, runs a benchmark, uses Median Absolute Deviation (MAD) to filter out statistical noise, and either commits or reverts — then loops. No human in the loop. The cycle repeats until a time limit or convergence criterion is met. The technique was popularized by Karpathy's autoresearch concept for ML training, but pi-autoresearch generalizes it to any benchmarkable target. Shopify's engineering team ran it against their Liquid template engine and reported 53% faster parse/render with 61% fewer allocations after an overnight run — changes their team had been unable to land manually in months. The MAD-based noise filtering is the key innovation: it prevents the agent from chasing benchmark noise and reverting valid improvements. The project has spawned an ecosystem: pi-autoresearch-studio adds a visual timeline of accepted/rejected edits, openclaw-autoresearch ports the concept to Claw Code, and autoloop generalizes it to any agent that supports a run/test interface. At 3,500 stars, it's one of the most-forked pi extensions.

P

Developer Tools

Plain

A Django fork rebuilt for AI agents — typed, predictable, agent-readable

Ship

75%

Panel ship

Community

Free

Entry

Plain is a full-stack Python web framework that forks Django with one overriding goal: make the codebase maximally readable and understandable by AI coding agents. Built by Dropseed (Adam Engebretson), it started in 2023 and has quietly matured into a production-ready framework — today's Show HN submission (93 points) brought it to wider attention. The design philosophy is radical clarity over magic. Plain eliminates Django's more implicit behaviors, adds strict typing throughout, and includes built-in AI integration hooks: a `.claude/rules/` directory for Claude Code context, a CLI command for on-demand documentation retrieval, and OpenTelemetry instrumentation out of the box. The idea is that when a coding agent touches your codebase, it should be able to understand what's happening without fighting through Django's layers of metaclass magic. This represents a genuine philosophical bet: as AI agents write more of our code, the framework's readability to machines matters as much as its readability to humans. Plain is ahead of the curve on this — most frameworks were designed for human ergonomics first. The Show HN traction suggests senior engineers are taking the concept seriously, even if migration from Django remains a real cost.

Decision
pi-autoresearch
Plain
Panel verdict
Mixed · 2 ship / 2 skip
Ship · 3 ship / 1 skip
Community
No community votes yet
No community votes yet
Pricing
Open Source (Apache 2.0)
Open Source / Free
Best for
Autonomous code optimization loop — edit, benchmark, keep or revert
A Django fork rebuilt for AI agents — typed, predictable, agent-readable
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

I ran this against my GraphQL resolver layer over a weekend and got 31% latency reduction with zero manual intervention. The MAD filtering is the real innovation — previous attempts at autonomous optimization would thrash on noisy benchmarks. This one doesn't.

80/100 · ship

The `.claude/rules/` integration and typed APIs are exactly what you want when you're letting agents modify your codebase. OTel built-in is a legitimate win — no more strapping on tracing as an afterthought. If you're starting a new Python project in 2026, Plain is worth serious consideration.

Skeptic
45/100 · skip

Shopify's results are impressive, but they're also running this on a well-tested, stable codebase with comprehensive benchmarks. On a typical startup codebase with flaky tests and incomplete benchmarks, this will confidently optimize the wrong things. Benchmark quality gates the whole approach.

45/100 · skip

Django's 'magic' is also its ecosystem — 20 years of packages, tutorials, and institutional knowledge. Plain's ecosystem is tiny. For any non-trivial project, you'll hit the ecosystem wall fast. 'Designed for agents' is a compelling narrative but the migration cost from Django is real and steep.

Futurist
80/100 · ship

This is the earliest glimpse of AI that genuinely improves software without a human in the loop. When benchmarks exist, the agent is a better optimizer than humans — it's tireless, statistically rigorous, and immune to sunk-cost reasoning. Performance engineering as a discipline is about to change.

80/100 · ship

The question 'is this codebase understandable to an AI agent?' is going to be central to framework design by 2027. Plain is three years ahead of that conversation. Frameworks that don't add agent-readability features will be retrofitting them later at significant cost.

Creator
45/100 · skip

The framing here is very backend/systems. I tried running it on a React component library to reduce render cycles and got a mess — the agent optimized for the benchmark at the expense of code readability. Fine for systems code, wrong tool for UI work.

80/100 · ship

As someone who ships products, not just writes code, I care about the full stack being coherent. Plain's opinionated structure means less time arbitrating between packages and more time building. The built-in OTel means I can debug AI-assisted changes without adding another tool.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later

pi-autoresearch vs Plain: Which AI Tool Should You Ship? — Ship or Skip