Models and agents, organized around you.
Use different providers, local models, specialized agents, and tools through one consistent workspace.
Rodon / Home
Rodon.
A place for systems, experiments, and work in progress.
What Rodon is
A place for systems and experiments. And a record of the decisions that shaped them.
Featured project
Rodon Workspace.
A personal workspace for conversations, knowledge, tools, durable work, and an optional connected Mail feature for people who choose to link an account.
A library that remains understandable.
Search files, sources, memories, and skills while retaining provenance and permissions.
Documents built from real context.
Draft, revise, compare, restore, export, and connect sources without leaving the workspace.
Tasks with a reason for existing.
Every action can retain its source conversation, message, document, mail item, or research result.
Analysis in an isolated workspace.
Let models use files, code, and controlled execution without exposing trusted infrastructure.
Turn recordings into usable knowledge.
Transcribe media, preserve timestamps, create summaries, and send the result into your library.
Background work that never becomes invisible.
Monitor research, transcription, computation, and agent actions with progress, cancellation, retry, and diagnostics.
Working method
Build, learn, leave a trail.
Every Rodon project begins with a real need, becomes concrete through making, and leaves behind enough context for others—and my future self—to understand the path.
?A question or recurring frustrationStart with something real enough to care about↓
◇Exploration and prototypeMake the uncertain parts concrete enough to test↓
□A working systemRefine the idea until it becomes genuinely useful↓
✎A journal entryRecord the decisions, failures, and lessons✓
Principles
What remains constant.
Build for a real need.
The strongest projects begin with a problem worth living with long enough to understand properly.
Show the process.
Decisions, dead ends, revisions, and mistakes are part of the work—not material to hide after launch.
Make systems understandable.
Technical depth should create capability without making the result mysterious to the people using it.
Leave room to evolve.
A project can be useful now without pretending it has reached its final form.
The Rodon Journal
Notes from the process.
Rodon Principles
Why AI needs durable work, not longer conversations
A conversation can begin the work. It should not be the only place where the work is allowed to exist.
EngineeringDesigning execution without trusting the model
The architectural distinction between trusted coding tools and isolated agent compute.
ProductMemory should be a window, not a mystery
Making extracted context observable, correctable, and worthy of trust.
Anything on your mind?
If something here feels relevant to what you’re working on, get in touch.