Local-first by design
The core workflow runs on your machine. Use the CLI yourself or connect an agent through MCP.
Agents move fast. Your decisions should travel with them. rdy keeps decisions and documentation connected as you design, change, and build.
Local-first · CLI + MCP · Public release in preparation
The rule behind the change stays in reach.
A decision changes. One page is updated. Another still carries the old rule. The next agent starts with an incomplete picture.
rdy gives decisions a durable place, links them to the content they govern, and brings that context into the editing workflow. The accepted design stays separate from work in progress.
Explore a simple example. These panels explain the workflow; they are not product screenshots.
The agent asks rdy for context. The briefing returns the recorded decision and linked material relevant to the change.
The core workflow runs on your machine. Use the CLI yourself or connect an agent through MCP.
Typed blocks, recorded links, and version history make governing decisions and dependent content available to the workflow.
Agents propose changes in separate views. You review what becomes accepted, with the reasoning kept in the record.
rdy computes from recorded relationships. It does not guarantee every dependency has been captured or replace human judgment.
rdyhub is the upcoming service for individuals and teams using agentic workflows. Designs, decisions, and intent live together; integrations carry that context into implementation.
Built to support a real agentic workflow.
Now being prepared for public release.