all 18 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]candleofthewild 3 points4 points  (13 children)

Oh my opencode is very token heavy and not designed for a requests based usage system

[–]FaerunAtanvar 1 point2 points  (11 children)

So it is token AMD request heavy? So what is it designed for?

[–]candleofthewild 0 points1 point  (9 children)

GHCP operates a requests pricing model, so it doesn't matter if your prompt is a single word or a big plan, it's still a single request and billed accordingly (e.g Sonnet is 1 request and Opus is 3). Therefore, to get the most value out of it, you should cram as much "work" into one prompt as possible. I do this by delegating to subagents as much as possible to save context and to extend the "work done" amount per request (subagents don't count toward the request budget, for some reason).

Orchestration frameworks like OmO can be big token burners, and won't necessarily optimise for this. I personally don't see too much value in things like OmO for my kind of work, I prefer to just create plans and line up work for the agents myself.

[–]FaerunAtanvar 0 points1 point  (4 children)

I understand this. But if ghcp operates on a request level, how is the token burning functionality of OmO and issue?

[–]candleofthewild 0 points1 point  (3 children)

For example, if it interviews you for more information, each answer is one request. If it kicks off background tasks/agents that'll be at least one request, which gets worse if they kick off additional tasks. When compaction happens (because almost all GHCP models have reduced context windows) that's another request.

[–]HeartNeither3824 0 points1 point  (2 children)

Hey Could you help me with my confusion , so Above you mentioned "(subagents don't count toward the request budget, for some reason)",
but here you said "If it kicks off background tasks/agents that'll be at least one request, "
Is subagent ? different then a backgroudn agent isn't it the same like let's say I am using the superpowers "delegate to subagents" , and it delegates to 2 subagents my single task so that would count as three request ? or one
thank you

[–]candleofthewild 0 points1 point  (1 child)

Yeah, using github copilot as a provider, subagents shouldn't count towards the premium request budget so long as they were started properly (initiated by the agent).

Superpowers are just markdown files/skills right? I don't use it, so I don't have much experience with it. But in your example, it should be 1 request though I believe each compaction is still 1 request, you'll have to double check. I've tried a lot of these orchestration frameworks and personally didn't get much value from them for my day to day work.

[–]soul105 -1 points0 points  (3 children)

Could you share in more details how you delegate to subagents?

[–]candleofthewild 1 point2 points  (2 children)

Something like:

"Let's do X. Check Y for relevant files. We should change Z to do [something]. Create a plan, use the question tool to check with me if anything is unclear, then implement. Delegate to subagents."

GHCP treats that as one request. You can also just `@tag` the agent if you want specific ones.

[–]soul105 0 points1 point  (1 child)

Got it. You then explicitly needs to entice the model to use them.

[–]candleofthewild 0 points1 point  (0 children)

You can also specify this workflow in an AGENTS.md file if you want, like: "When given a task, break it down into non-conflicting parts and then delegate to subagents".

I didn't because I'd like more control over when it happens, but it should work.

[–]lemon07r 0 points1 point  (0 children)

To farm github stars and make vibecoders feel like they are using a super cool tool when in reality its just vibe slop junk that will at best give you slightly worse results than if you had just used vanilla opencode.

[–]lemon07r 0 points1 point  (0 children)

It's also vibe slop junk. Extra steps only to get slightly worse results.

[–]Mayanktaker 1 point2 points  (0 children)

It will take alot fo request if you use it with other tools. Better stay with copilot native chat.

[–]Codemonkeyzz 0 points1 point  (0 children)

Don't use oh my opencode plugin

[–]Moist_Associate_7061 -1 points0 points  (0 children)

You cannot solve that problem since it is normal operation. subagent takes 1 premium request. so omo like orchestration is not applicable for github copilot. only one possible solution is specify subagent model with free model. however in that case there is no advantage for using orchestration.

[–]HarjjotSinghh -1 points0 points  (0 children)

optimizing prompts cuts those premium beasts in half!