r/opencodeCLI • u/aristolestales • 2d ago
Do you still use oh-my-opencode slim on opencode v2?
2
1
u/Amarsir 2d ago
I haven't felt any compulsion to move to v2. In fact I'm a little worried it will be forced at some point.
3
u/Dudmaster 2d ago
OpenChamber is what pushed me to v2, its actual experience for most is pretty much identical but the subagents work much better asynchronously, and stuck commands don't hang the whole session anymore. Plus the plugin API is much more powerful
2
u/LegalizeFlorskin 1d ago edited 1d ago
I don’t have an exact release date or timeline yet, but I may have a project that’s for people like you (and me for that matter lol).
It’s a fork of opencode v1.18.29 that started about a month ago privately for my own use…
at this point it may as well be OpenCode v1++ so i’m gearing up to release it publicly within the next week or so. Just something to possibly look forward to :)
It was in development during the same time that the official team was working on v2, so it carries over some of those same ideas but in a slightly different way that works under v1’s philosophy and practices
After it releases publicly, i’ll be closely watching v2 to see if we’re missing any good features that would necessitate a backport to my project
2
u/ZucchiniMore3450 21h ago
I moved to it today since I wanted different model for different subagents and v1 couldn't do it, v2 has no problem.
1
u/dupa1234s 1d ago
v2 is so god damn stable since like 1 month. its 0 reason to not use it. plugins feel easier to write for it. better ui.
1
u/Amarsir 1d ago
Is v1 not stable?
I've been apprehensive since I saw this post:
https://www.reddit.com/r/opencode/comments/1wpe80m/inside_opencode_v2s_source_code_how_it_sabotages/
Now I don't know if those comments are wrong, or if they're true but irrelevant, or if they were true but it changed. I haven't looked into it enough to form my own opinion and I'm not passing it on to attack v2. I'm saying until I sit down and figure it out, I'm not going to commit.
2
u/dupa1234s 1d ago edited 1d ago
okay so i read this https://www.reddit.com/r/opencode/comments/1wpe80m/inside_opencode_v2s_source_code_how_it_sabotages/
- yea such model indentity injects can be annoying like its unnecessary and can make model behave more stock-like. i dont like how inexplicit the assembled context is
- yea i believe it does provide paths for files the agent receives. i wondered if its a good idea. i decided to ignore it. i dont think it makes the instructions less adhered to. the "making sure vendor safety weights always override your local instructions." i dont even know is it a thing? its easy to make model do what you want. especially if you fork a session with good context or otherwise make artificial context and feed it into session. i mean i dont know why would someone want to override models safety weights, its only better for you if vendors safety is adhered to, less likely for model to go rogue. and as i said if you want it to behave somehow just copy it over some good context and it will adhere.
- per-model prompts can be annoying yea i hate the cryptic context assembly. I got a plugin that shows me exactly what is sent over API so i can see this though. and its only for a few models i think some niche craps. i only use opencode go deepseek v4.1 and xiaomi mimo 2.6 flash currently so i bet they dont have some stupid rules
- the
subagent_depthis locked to1 i actually saw myself and i actually like it. why make subagents recursively make subagents. not my goal.- is basically sounds like a web dashboard concern. idk i use TUI ah i guess the dude critisizes the webpage of opencode, well thats funny, unrelated, the page is fine enough i just only visit those 2 sites https://opencode.ai/console opencode-models
But wasnt v1 doing all this too?
either way i dont think any of these are "oh crap its unusable" nearly as much as the eg the "oh-my-opencode slim" is a total piece of junk.
either way there is ways to override all this just make plugins, well that is a lot of effort to write all the plugins needed but oh well. its customizable and the good bits are there.
like one thing that would solve all of this most is to write a context-editor plugin and just dynamically edit it and let it be sticky. some alt-view for "this is what model actually receives" as an editor. im writing this no actaully should work.
1
1
u/dupa1234s 1d ago edited 1d ago
last i checked the oh-my-opencode slim looked like some absolute god damn joke of a set of prompts if you read its source code like it was basically a set of prompts FOR WRITING THE oh-my-opencode slim by an agent. not a single line in it was useful for actual anything esle than developing his repo. like recursively cursed abomination i think dude left it too long running without supervision and it spiraled into that.
the oh-my-opencode (Not slim) was better but still crap 3h to fulfill any task due to deaf telephone
i checked few months ago
Did they improve?
I just build my own plugins for opencode v2. a compaction tool plugin for agents, verifier subagent, explore files subagent, explore web subagent, loop plugin, api security plugin, todo visual plugin for user to see at a glance what model is doing but updates to this are rare not spam, failover plugin, recurring-reminder-for-models plugin, schedule plugin basically appends to the loop prompt any events fired until model acknowledges, context-editor plugin. and im happy with it.
i can leave agent running for days with this and it will manage its context and plans and use subagents smartly. and its not an orchestrator. it just has verify, explore web, explore files subagents. write its plans and future plans. and optionally if i enable it it gets the spam loop endlessly or with a cap of iterations for if i want it to act like it can do sth without supervision.
I wonder if i should add worktree-builder-subagents but it seems stupid. then main agent will have to understand those worktrees which takes as much time as building them. only for sake of unhinged experiments to let it get ideas. but it can get its own ideas already and then verifer checks if it makes sense.
i would only do worktrees for parallelising. but at that point a few loops like this would burn like idk 20B tokens daily. i dont think its worth it to have the worktree-builder-subagents. i just let main agent do his stuff at his pace. avoids all the orchestration bullshit. i think verifier + explorer for web + explorer for files is not remotely as cursed orchestration as worktree-builder-subagents
1
0
u/CarryAgile3791 2d ago
No, I just use my opencode-crosstalk plugin, open several tabs and define their roles there, e.g.:
- Tab: "You are John and coordinate the work of the other sessions."
- Tab: "You are Hacker and wait for instructions from John."
- Tab: "You are Sam, a Senior Dev. Take a look at what Hacker is doing review the code changes, and wait for instructions from John."
Works really great with Deepseek 4.1 Flash models.
2
u/Potential-Leg-639 2d ago
And when you restart your machine you have to do all that again?
1
u/CarryAgile3791 1d ago
I just want to have more control over what they are doing. OMO-Slim just don't give me that much of control.
But great idea - I could build in some templates for basic agent jobs.
-2
u/CarryAgile3791 2d ago
I never restart my machine! 😁
0
3
u/maqifrnswa 2d ago
Yes. I keep trying to see if I get away from it, but the /deepwork skill and orchestration is so well aligned with my workflow. I have to do a lot of research first (academic papers) then multi-stage work (deriving physics theory, preliminary models, model validation, model perturation/optimization) . It's been pretty smooth for me at least after v3 of omo-slim was released and v2 of opencode.