- 276comments
- 77comments
- 85comments
- 166comments
- 14comments
- 32comments
- 291comments
- 431comments
- 14comments
- 107comments
- 3comments
- 250comments
- 380comments
- 483comments
- 30comments
- 26comments
- 38comments
- 1comments
- 14comments
- 13comments
- 98comments
- 8comments
- 14comments
- 9comments
- —discuss
- 37comments
- 19comments
- 156comments
- 118comments
- 1comments
Radix is a UI tool for programming agents. You prompt your agent to generate a workspace for a task you're working on and get an interactive widget that persists locally on disk.
I built Radix because I always needed tools while I was writing code: tools to test little experiments, to play around with UI, to visualise results etc. Sometimes these would end up as python tools that read and plotted data, or separate React apps spun up just to test a single feature. Lately obviously I've been using Claude artifacts but these are quite limited.
I wanted a system where it was easy to leave comments or adapt an artifact without having to give vague descriptions back to the agent, and where ideally I could actually shift away from a chat window as the main interface.
I've got a pro version of Radix which I will launch soon. This current version is entirely free and is definitely a beta -- there will be rough edges!
Note: There's no telemetry or data captured. Your messages run entirely through your own agent. I require a key but that's just to get an idea of how many people are using it. Everything is stored locally (the workspaces are actually just React apps which you can edit "artisanally" if you want).
If you have any questions please reply here or email me hello@radix-os.com
Thank you!
What does the term agentic programming means over here?
Using agents to write code
Is this affiliated with WorkOS and the long going Radix UI component primitives maintained by them?
Nope, this is an entirely separate product and I have no affiliation with the people who worked on Radix UI, or with WorkOS.
You'll want to strongly consider rebranding with a different name. Way too easily confused.
[flagged]
It's an example of an algorithm that can be complex to read in code, but is more approachable when viewed as a diagram -- a perfect case for a tool like this.
Also thank you for your feedback and taking the time to view the landing page at least!
Can you please make your points thoughtfully and not respond to people's work by ranting at them?
https://news.ycombinator.com/newsguidelines.html
https://news.ycombinator.com/showhn.html
The landing page looks lovely, but the examples shown have no foundation in my head for what they're doing / showing / helping with.
It's confusing enough that I don't know if this is just way above my knowledge level or whether I just don't understand what it even is.
It feels like you've developed something really useful but it's so internally obvious in your own head that it's missing some steps in the explanation for everyone else on how to come along with you and see the power of it.
Yes ha this is very accurate unfortunately.
I'm actually using Radix right now to brainstorm and update the example on the landing page to be more descriptive.
If it helps: the basic idea is that instead of an agent returning text or markdown we get it to return HTML. We then provide an app which makes working with that HTML actually useful (i.e. a sidebar to list the tools you've built, a way of commenting on the pages it generates).
The most trivial example I can think of is creating a simple colour picker. With Radix you can get an agent to add a colour picker that updates the code directly when you change its value (as explained further in [1]).
[1] https://radix-os.com/notes/hello
Yeah, I don’t really see the point of it just glancing at the website. In fact, that little stack of activity notifications at the bottom seem quite obstructive and unintuitive, not sure if it’s part of the product but as a UI element it looks… off.
(It's not part of the free version since that works with your existing agent and you interact with it however you normally would).
The message stack in the bottom are the agent replies as it works. The idea is to move away from an array of messages as the primary interface with an agent and instead make the tools the primary interface. Whether that's actually helpful is an open question but it's certainly how I prefer to work now that I've been building with it.
I see, that makes sense. Though I personally think the UI could use a little bit of a touch up.
Is there a https://en.wikipedia.org/wiki/Radix_tree somewhere in there?
Haha no sadly not, the name was chosen purely because I like the sound of it.
I thought it was a new product from the Radix UI team focused on agents. The name is actually pretty confusing.
Yes sorry I may need to change that.