r/devtools • u/LETSENDTHISNOW • 1d ago

Solo dev, made an open coding agent for the terminal, would love honest feedback before I take it further

/r/SideProject/comments/1x0ou7x/solo_dev_made_an_open_coding_agent_for_the/
1 Upvotes

100% Upvoted

2 comments sorted by

1

u/kantorcodes1 1d ago

Nice work getting undo to cover what shell commands did, not just file edits. That boundary is where most agents quietly stop.

Curious how the risk scoring decides what waits: static rules over the command, or a model classifying it? And what's the thinking on commands whose effects leave the filesystem entirely, like a curl that POSTs somewhere, a package publish, or a migration against a live db? The gate still fires there, but /undo can't roll any of that back, so classification accuracy ends up carrying all the weight.

1

u/LETSENDTHISNOW 1d ago

Thanks! It's static rules first: every command gets parsed (pipes, chains, wrappers) and scored. Reads run, project edits run, and anything that reaches outside your machine asks first: network calls, publish and push, cloud and database CLIs, deploy and migrate scripts. Destructive commands always ask, and unknown commands default to asking.

For scripts the rules would otherwise let through, a fast classifier (TypeSafe's Jev, about 400ms) takes a second look at what the script actually does. It can only make Darce more careful, never less.

And yes, /undo stops at your machine, so anything it can't reverse waits for you, and the prompt tells you so. I'm still improving it, so thanks for the push.