This is small and early, but I wanted to put it out there.
I got tired of AI that's all bark and no bite — confident, fluent, and it
tells you "Done!" whether or not anything actually happened. So I built the
opposite, in the narrowest way I could.
ORZN is a local task-runner. It does a handful of things on your own machine:
finds, reads, summarizes, moves and renames your files, launches apps, opens
sites. Nothing fancy.
The one idea I actually cared about: it records every action, and it won't
mark a task "done" unless there's evidence it happened. If it can't prove it,
it says "blocked" instead. And it stops for your approval before it changes
any file.
It's not a general "do anything" agent and it doesn't do much yet. Free, MIT,
local, no account — nothing leaves your machine unless you point it at a URL.
Repo: https://github.com/snit292012/orzn
Genuinely want blunt feedback, including "this is too small to matter."
Top comments (2)
"It tells you Done whether or not anything actually happened" is the exact frustration that made me rebuild one of my own tools — so this instinct is right. One push on it, from having been burned a level deeper:
gating "done" on evidence is the move, but watch what counts as the evidence. If the proof is the tool's own action log ("I moved the file"), that's still the tool grading its own homework — it recorded that it acted, not that the world changed. I had a health check that reported "database: ok" by reading a status its own endpoint had written about itself; it passed happily until I made the watcher run the query directly instead of trusting the report. For a file mover, the honest version is re-statting the destination after the move — confirm the file is actually there, from outside the code that claims to have put it there.
Narrow scope and an explicit "blocked" instead of a fake "done" is already more honest than most things that ship. The upgrade is just making the proof something the tool didn't write itself.
Thank you so much! Will take that into consideration.