Repository navigation
OMO Standalone was a bad decision (Opinion) #9100
delasource
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
OMO felt like a natural extension when I was using it within OpenCode. I appreciated the flexibility and transparency—I could see exactly what was happening and control the granularity of each task.
As a standalone product, it's a different story. It burns through tokens without visibility into what's actually running or which models are being used. That opacity is the real problem.
I would like that you keep the thing as a plugin and add support for opencode 2.
All reactions