Radix is a macOS app that gives coding agents like Claude Code a persistent workspace. Your agent builds interactive pages, tools and diagrams that live in your repo and stay wired to your code.
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 [email protected]
Thank you!
18 comments
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.
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]).
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.
Read the full thread on Hacker News →
Related stories
- Launch HN: Vespper (YC F24) – SOTA Docx MCPvespper.comHacker News · 31 points · 2 days ago
- Hacker News · 3 points · 3 days ago
- Hacker News · 15 points · 13 days ago
- Show HN: Vespper (YC F24) – Docx MCPvespper.comHacker News · 5 points · 2 days ago
- Hacker News · 1 points · 9 days ago
- Hacker News · 1 points · about 1 hour ago