@boundaryML

Learn more about BAML: https://nitter.cf/t.co/ZeXBUN6m0N

Joined January 2023
make a new programming language: 1. sound type system, like Rust 2. compiles as fast as Go 3. looks like TypeScript 4. green threads 5. embeds anywhere 6. ??
2
2
1
18
5,412
Boundary retweeted
I think we’re looking for this github.com/BoundaryML/feelin…
putting an early bet that Jev’s biggest use will be some flavor of context window protection for agents by filtering tool results agents will perceive a cleaner world through the lens of Jev
3
2
39
3,875
No comment.
We really do earnestly believe BAML could kill all programming languages! I personally think it is >10% within the next decade. I believe @boundaryML is trying its best, but we do not yet have a plan to solve alignment and are not clearly on track to.
2
1,003
Boundary retweeted
i know for some folks this is peanuts, but its so cool to see that in the last 48 hours at least 75 people were watching @dexhorthy and I yap on youtube every hour. love you all <3
6
2
45
3,457
Y = λf.(λx.f(x x))(λx.f(x x))
1
5
1,469
Boundary retweeted
new benchmark for tool calling... gpt-oss-20b tops out gpt-5 mini (no fine-tuning) full results coming out soon in a blog post!
2
1
10
1,017
Boundary retweeted
running background tasks that just "do helpful things" is so nice. we now have a package that anyone can use for syntax highlighting BAML that auto updates whenever the grammar changes.
1
1
16
966
Boundary retweeted
AI is writing more code than you will ever read, but if you don’t understand how it works, its not going to end well. To understand the code, trace everything, because you can’t know what is possibly going to be useful in the future, and you’re going to be darn happy you have the log. @dexhorthy and i yappin
3
6
27
2,930
Boundary retweeted
Replying to @davidcrawshaw
Why would untyped be better? Wouldn’t you want compiler errors before runtime errors? And then leave runtime errors for logic state. (Ofc assuming a fast compilation time) Reading local code would be harder for both humans and agents without type information
1
11
506
Boundary retweeted
agents deserve their own programming language. @boundaryML is already doing this incredibly well with BAML. Ive genuinely been loving it so far super excited to be in seattle this week w/ the team~ I’ll share my insights & thoughts on BAML throughout the week! @vaibcode
3
14
1,931
Boundary retweeted
Someone really wants our promptfiddle.com api keys... here let me make your life easier. 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 Meanwhile, promptfiddle is now BYOK :(
2
3
12
1,671
At @boundaryML We're building building a full compiler, VM and async runtime. Kinda like TypeScript + V8 + Node.
i wonder about people who are claudemaxxing/codexmaxxing 18 hours a day, like what are these folks building exactly?
3
3
17
3,597
marginally manageable is the highest form of flattery
5/x: and then use @boundaryML 's BAML for chunking things out and testing / iterating quickly. fuck llms and prompts etc but if you have to work with them BAML is like the only thing that makes it feel marginally manageable.
1
1,757
We are launching a programming language built for agents soon called BAML that has been in the making for 1+ years. You can follow @boundaryML We are a small team of 6 developing it with care, gathering feedback from humans and agents. Fully Open Source. If you are interested DM me for early alpha access.
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.
2
2
13
1,691
I benchmarked a new extraction harness on a private eval dataset for lerim-cli (new version is out now - v0.1.83) and the main lesson was very clear: if you want smaller models to work well, you should stop asking the model to do everything and start doing more engineering work. Before, the agent was closer to a single-pass PydanticAI setup: read a large trace, understand what matters, decide what is durable memory, call tools correctly, stay inside the context window, and output clean structured records. That puts too much burden on the model, especially when you want to use smaller or cheaper models. The new harness is BAML (@boundaryML) + LangGraph (@LangChain). The graph now does more of the deterministic work: - read the trace in windows - ask the model to scan one window at a time - keep compact findings instead of the whole trace - synthesize memory records only at the end - validate/retry typed BAML outputs - persist with normal code, not model improvisation So the model is not the whole agent anymore -> It is one reasoning component inside a more engineered system. On the private benchmark, using the same MiniMax M2.7 model, the new harness completed all cases while the old harness had multiple failures from tool retries and context window issues. - Task completion: BAML+LangGraph completed 100.0% vs PydanticAI at 72.73%, a +27.27 point lead. - Case failures: BAML+LangGraph had 0 failures vs PydanticAI with 6, meaning 6 fewer failures. - Episode count rate: BAML+LangGraph reached 100.0% vs PydanticAI at 81.25%, a +18.75 point lead. - Record budget rate: BAML+LangGraph reached 46.88% vs PydanticAI at 28.12%, a +18.76 point lead. - Concept recall average: BAML+LangGraph scored 0.428 vs PydanticAI at 0.2598, a +0.1682 improvement. - Quality average: BAML+LangGraph scored 0.3352 vs PydanticAI at 0.318, a +0.0172 improvement. - Tool call errors average: BAML+LangGraph had 0.0625 vs PydanticAI at 1.9688, much better. Quality is not solved yet. It is only slightly better overall and still needs better pruning before persistence. But robustness improved a lot. This is the direction I think specialized agents should go: smaller models, more deterministic scaffolding, less magical thinking about one giant prompt doing the whole job. Next step is to make this work well with models people can run locally. A new version of Lerim-cli is now released with the extract agent refactored to use Langgraph+BAML. Next agents will be refactored as well soon in the next releases. github.com/lerim-dev/lerim-c…
1
1
5
382
Boundary retweeted
Refactoring is definitely much easier now. Here's how i used agents to refactor our entire compiler (+65k, -117k, 74 commits). 1. Forked parallel crates (foo --> foo2) 2. Strict dependency firewall (enforced via precommit) 3. Audited core data structures first <-- took time
"Refactoring is so much easier now" Not if you're generating 100x more code to refactor
2
1
26
6,224
My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
1
1
2
14
2,595