Radix

Radix is a macOS app that gives programming agents a visual workspace beside the usual chat or terminal conversation. Instead of asking an agent for another block of prose, a developer can ask it to build an interactive page for the task at hand. That page stays on disk and can continue evolving as the work changes. The result is closer to a small task specific tool than a disposable answer, which makes Radix useful when code, controls, diagrams, or live output would communicate more clearly than markdown. It is built around the belief that some programming questions are easier to answer by manipulating a working interface than by reading another explanation.

The basic workflow starts with the coding agent a developer already uses. A prompt asks that agent to create a workspace for an experiment, investigation, or implementation task. Radix displays the generated interface and keeps it available in a sidebar with the other tools made for the repository. The developer can interact with the page, inspect what it shows, and leave comments on the interface instead of describing every requested change vaguely in chat. The agent can then adapt the workspace while retaining the visual context that prompted the change. That makes iteration more specific because feedback can refer to the thing on screen rather than reconstructing it in words.

These workspaces are local React apps, so they aren't trapped in a proprietary document format. A developer can open and edit the files directly when that is faster, and the workspace can remain next to the code it helps explain. Radix presents examples that span diagrams, plots, debugging views, test coverage, state machines, schemas, flame graphs, import cycles, and other engineering artifacts. The exact output depends on what the connected agent builds. Radix supplies the durable surface and interaction model, while the agent supplies the implementation for each task. A workspace can therefore be as small as one useful control or as involved as a multi-panel view into a problem.

That distinction is important for understanding what the product does and doesn't do. Radix isn't another coding model, and it doesn't replace the agent that writes the code. Messages continue to run through the developer's own agent. The maker says the current beta captures no telemetry or user data, and that generated workspaces remain local. A free key is still required to use the app, primarily so the maker can understand how many people are trying it. Developers should expect to install a native app and connect it to their existing workflow rather than sign into a complete browser IDE.

Radix fits developers who regularly create temporary scripts, small dashboards, diagrams, or one purpose React pages just to understand a problem. It can turn a color picker into a control that updates code, give an algorithm a more approachable diagram, or keep a debugging view available while an investigation continues. It also suits people who find agent chat histories difficult to navigate once a project contains several parallel lines of thought. A persistent library of task focused interfaces makes the useful result easier to return to than a message buried in a transcript. It may also reduce the urge to build and abandon a separate mini app for every experiment.

The interesting part is its attempt to make the artifact, rather than the stream of agent messages, the primary interface. A developer can act on a control or comment on a specific visual element, which gives the next agent turn more concrete context. Because each workspace is an ordinary local app, it can be inspected and changed without waiting for Radix to add a dedicated template. That flexibility is also a limitation. Artifact quality depends on the connected agent and the prompt, and the public product material doesn't yet define a polished workflow for every example it names.

Radix is currently an early beta for macOS. The present version is free, requires a free access key, and installs through a command provided on the site. The maker has said a Pro version is planned, but the live beta doesn't yet present a paid tier with established limits. That makes it inexpensive to explore, though buyers should approach it as a young developer tool with rough edges, a narrow platform target, and relatively sparse documentation. It is most compelling for an individual developer willing to shape a new agent workflow, not for a team that needs mature administration and support promises today.