Show HN: Plain – The full-stack Python framework designed for humans and agents

Inventing a new thing "for agents" always feels counter-productive. Your new thing isn't in the training data, so you have to teach it how to use your thing. Why not use tech that's already in the training data? Agents know Python and Django. Or, better (because the performance, maintainability, and deployment story are much nicer with no extra work, since agents write the code), agents know Go.

The very nature of LLMs means you can't invent a thing for current agents to use that they'll be better at using than the things they already know how to use from their immense training data. You can give them skills, sure, and that's useful, but it's still not their native tongue.

To make a thing that's really for agents, you need to have made a popular thing for humans ten years ago, so there's a shitload of code and documentation for them to train on.

It looks like it's a fork of Django that just kinda changed a bunch of stuff arbitrarily?

Something like this has been on my mind for a while. When using LLMs for coding I believe it is a significant benefit, if the amount of lines to be reviewed by humans is as small as possible. An app, which is not much more than a configuration in a dense, custom made DSL with minimal coding to specify business logic would be the simplest artifact that a human can review quickly and an LLM can manipulate with ease (provided there's good docs / linting / errors / maybe even a finetuned model at some point).

Everything which just works "by convention" or by "opinionated defaults" (allowing a tightly coupled but very feature rich framework) helps to reduce the noise / lines that needs to be reviewed.

While this approach might not be optimal for every project, I'm certain the opinionated defaults can work for many endeavours. And the reduction of complexity might be one important aspect, which can make an "agentically engineered" project sustainable.

Nice. Love the idea behind this. I have been using Django for most of my vibe coded side projects just for the reasons stated in this thesis.

Django code is pretty easy to review quickly. LLMs are good at writing it.

Django is just old and bloated, so the fork is a good idea. Maybe I will use this for my next side project.

It’s vibe-coded, too. Pass.

TLDR:

- fork of django

- it's opinionated

- typed

- comes with skills / rules / docs baked in

I'm not against this idea in principle, but I'm also not sure why that is better than what's already out there, except maybe you save some tokens by not vibe coding this yourself?

I do think in the future we'll see some novel libraries that are agent-optimized first. I'm not sure if this is it, though.

(edit: formatting)

How does this compare to FastAPI + SQLModel?

So a sloppified Django spit out by Claude? Good luck with that.