
Building Maelstrom | OSS @maelstrom_co · https://teapawt.net/t.co/Vt8Uq46hJY
Lodz, Poland
Joined June 2014
- Tweets279
- Following289
- Followers278
- Likes852
Chris Trześniewski retweeted
Meet Mar...
This app has a special place in our hearts; not only is it my oldest daughter's name, but it is also the app we created to test what @maelstrom_co could do
Chris Trześniewski retweeted
Replying to @maelstrom_co
@maelstrom_co and @umami_software, what a perfect match
Chris Trześniewski retweeted
In case you were curious, here are some more details about how @maelstrom_co works
The time has come... Maelstrom is now open source.
Let AI arrange your React components and run the actions you expose through conversation.
Our first stable release, 0.1.0, is live on npm.
We Just Open-Sourced Maelstrom. Here's Everything you Need to Know
Maelstrom is an open-source library for AI-orchestrated UI. It lets AI arrange and resize your components, then trigger their actions based on what the user wants to do.
Chris Trześniewski retweeted
The time has come... Maelstrom is now open source.
Let AI arrange your React components and run the actions you expose through conversation.
Our first stable release, 0.1.0, is live on npm.
We Just Open-Sourced Maelstrom. Here's Everything you Need to Know
Maelstrom is an open-source library for AI-orchestrated UI. It lets AI arrange and resize your components, then trigger their actions based on what the user wants to do.
Replying to @maelstrom_co
@maelstrom_co has a functional voice integration, realtime actually. One fact about our voice architecture, our VAD runs on the client side. It needs no infra and uses state of the art silero VAD on top of onnxruntime compiled to Wasm. Thus, seamlessly barge-in under 200ms.
Tested OpenAI's Decisions API beta as the fast path in @maelstrom_co's intent-to-UI planner.
Fast: ~170 vs ~310 ms/call, but 2x more turns silently wrong. It's beta, so numbers may change.
Payoff: rewrote our planner's questions. 70.8% -> 82.8%, beating LLM-only.
@OpenAIDevs fun beta to test. Happy to share the eval setup and failure cases if they're useful.
17
How I wasted millions of tokens by not reading the docs 🤦
I designed an elegant layout planner for @maelstrom_co: 16 questions in one Jev request instead of a layout list. It passed 69% of layout tests. The list: 80%.
Why elegance lost, and why brute force isn't always bad 🧵
Last problem: sizes. I assumed Jev's score between levels was continuous. It's not. It measures uncertainty, not magnitude.
Fix: make the levels the actual quantities ("a quarter", "half"). Jev answered "half" with confidence 1.0.
Layout tests passed: 91% → 99%.
1
2
26
Years of trading ideas with @naxodev. This is the one neither of us could drop.
You design the components. The model decides which ones show up and where, based on what the user is doing.
Private beta's open. If you write React, come build with us while the API is still moving.
You design the components. AI arranges them around what the user wants to do.
Introducing Maelstrom: AI-orchestrated UI.
We’re opening the private beta for React engineers. Build with us and help shape the API.
Join the beta: maelstrom-ai.co/#waitlist
Introducing Maelstrom: AI-Orchestrated UI | Private Beta
Maelstrom lets AI arrange, resize, and interact with the UI components you design, based on what the user wants to do. Request private beta access: https://maelstrom-ai.co/#waitlist
1
4
4,216
Interesting take on enforcing modularity without barrel files using github.com/softarc-consultin…
I love this idea!
Presentation by @rainerhahnekamp ath #ngPolandConf
I didn't expect that! Learning about anti matter at #ngPolandConf with Karol Szymczyk
2
86
#NgRx signalStore provides an amazing extensible API for building your store out of multiple custom extensions! I need to dig deeper into the docs! What are your experiences with this API?
Presentation by @AlexOkrushko at #ngPolandConf
I’m listening very carefully 🧐
By @dzinxed at #ngPolandConf
1
104
What does the #Angular compiler do under the hood? Here is a small sneak peek of the transformation that happens with incremental hydration using the `defer` syntax
By @Jean__Meche at #ngPolandConf
9
541











