Introducing Zero The programming language for agents. I wanted a systems language that was faster, smaller, and easier for agents to use and repair. Explicit capabilities. JSON diagnostics. Typed safe fixes. Made for agents on day zero.

May 15, 2026 · 11:44 PM UTC

382
203
2,669
1,710,747
Sort replies: Relevant Recent Liked
Replying to @ctatedev
WEN self-hosting?
2
33
59,642
98.7% there
3
55
56,330
Replying to @ctatedev
so agents can't write any of the currently existing languages? 🤔 why would a brand new language be easier for agents vs languages that have billions and billions of existing, functioning lines of code throughout history that have been extensively used in training sets?
11
4
621
44,716
Replying to @ctatedev
"Claude build me a new language called zero for agents. No Mistakes."
101
2,773
Replying to @ctatedev
Chris
1
63
8,722
Replying to @ctatedev
feels like typescript and rust had a baby looks lovely
30
4,113
Replying to @ctatedev
I don't know what to say other than eyes emoji! Excited to dig in. Fun fact - the @ppressdev started out as a convo with my agent "I want to start a programming language from scratch for agents - here's why." and then it talked me out of doing that and the idea evolved into the Printing Press
1
21
6,396
Replying to @ctatedev
come on folks. you could have been just slightly creative instead of another overload of the term zero.
31
2,830
Replying to @ctatedev
i know what i'm doing this weekend...
20
3,239
Replying to @ctatedev
a brand new language that no llm has ever heard about or knows how to write, brilliant
1
1
27
1,333
Replying to @ctatedev
Interesting. But: 1. How do you know it's better for agents? Any backing research? 2. Better than what? All existing programming languages? 3. How is it for humans? 4. How do agents deal with the relatively tiny code sample size for Zero? 5. What about the ecosystem?
13
638
Replying to @ctatedev
bro
7
1,541
Replying to @ctatedev
wow you love naming things zero
2
218
Replying to @ctatedev
The .0 extension is going to fight you. Log rotators (app.log.0), Unix split, core dumps, and numbered backups all use trailing ".0/.N". Most .gitignore templates and IDE indexers treat *.0 as a rotation artifact and skip it. LLM's training data associates .0 with "log file," not "source." For an agent-first language, that's the ambiguity you'd want to remove. .zero or .zr would have been friendlier.
5
532
Replying to @ctatedev
bro
2
379
Replying to @ctatedev
Haha, @mvanhorn was just pitching this to me! A true visionary 🙏
3
1,656
Replying to @ctatedev
:/
2
169
Replying to @ctatedev
ok the name and file extension is cool af🫡
1
209
Replying to @ctatedev @rauchg
beast! 🔥
2
1,635
Replying to @ctatedev
Python is the programming language for agents.
1
138
Replying to @ctatedev
yo chilllll
1
430
Replying to @ctatedev @rauchg
Agent languages are going to force everyone to care about boring systems constraints again. Smaller/faster/easier suddenly matters a lot.
1,696
Replying to @ctatedev
what the fuck is this bullshit
32
Replying to @ctatedev
we are now designing languages to be debugged by something that cannot feel frustration
290
Replying to @ctatedev
Can write GPU kernel in it? Pls say yes!
520
Replying to @ctatedev
vulnerability-wise?
27
Replying to @ctatedev
This needs explicit error types / checked exceptions I think!
616
Replying to @ctatedev
trying it out on a livestream now @ctatedev
77
Replying to @ctatedev
Imagine a world where print can throw an exception 😂
68
Replying to @ctatedev
interesting work!! tooling is indeed important for unlocking AI power, but wonder if we can do similar for existing languages so we don’t waste the data scale 👀
1,168
Replying to @ctatedev
Take a look at MoonBit - moonbitlang.com/
129