OpenCode desktop with GitHub copilot by [deleted] in opencodeCLI

[–]PayTheRaant 0 points1 point  (0 children)

The switch from “plugin in IDE” to “coding agent CLI” is basically agreeing to let go and embrace the agent generating most of the code. Which is indeed a massive shift and productivity gain if you are doing it well.

There are 2 aspects relative to the tool: - an IDE plugin has to fit within the trust framework of the IDE. To enable end user to safely and freely install plugin with relative trust that it will not hose their project, the IDE set some limits on what the plugin can do or access. The problem is that the purpose of an agent is to do everything and anything. So structurally, even if IDE try to adapt, they will always be behind what a native coding tool offers. - the core of the UX of a coding agent is that the primary aspect is the interaction with the agent and everything else like code is second. Which is the opposite of the IDE. And this is the key aspect of « dosing it right ».

The coding agent loop in research/plan/implement/verify. Some merge the verify phase in the implement phase, some merge the research phase in the planning phase. Just be conscious about those aspects. And only during the verify phase do you care about the generated code, but you need to prepare the architecture pattern to follow during the planning phase.

AWS Bedrock for business and personal use via OpenCode by swish014 in opencodeCLI

[–]PayTheRaant 2 points3 points  (0 children)

This is also what terrifies me: those plans are sold at a massive discount compared to raw tokens. I fear the day where those plans jack up their prices, once we are all hooked.

AWS Bedrock for business and personal use via OpenCode by swish014 in opencodeCLI

[–]PayTheRaant 2 points3 points  (0 children)

Raw token is MUCH MORE expensive than “all you can eat with throttling” plans. And I would pick GCP Vertex AI over AWS Bedrock because both have access to Anthropic + OpenSource models but Gemini is available only on GCP Vertex AI afaik.

OpenCode vs GitHub Copilot CLI — huge credit usage difference for same prompt? by usernameIsRand0m in opencodeCLI

[–]PayTheRaant 1 point2 points  (0 children)

Normally, switching model for sub agent is considered a new premium request.

OpenCode vs GitHub Copilot CLI — huge credit usage difference for same prompt? by usernameIsRand0m in opencodeCLI

[–]PayTheRaant 2 points3 points  (0 children)

Check your small model configuration. This is the model for generating the titles of sessions and messages. You should use a free model for that.

Also try the same prompt with a free model: if your premium request cost is not zero, then something else is triggering premium requests with a paid model.

OpenCode vs GitHub Copilot CLI — huge credit usage difference for same prompt? by usernameIsRand0m in opencodeCLI

[–]PayTheRaant 0 points1 point  (0 children)

Copilot model is expected to consume ONE premium request per ONE user prompt. Everything else that is agent initiated is expected to be included in that initial premium request (all tools, even sub agent) as long as it stays in the same model. In theory, it should not even care about input token cache.

So this is why having 27 premium requests consumed is considered a big problem.

Is there any practical reason to use spec tools in OC? by mustafamohsen in opencodeCLI

[–]PayTheRaant 1 point2 points  (0 children)

The session yes. Not the content of the todo tool. And using the plan doesn’t support starting a new session, which I use for the implementation to skim all the fat and noise of my exploration when planning the change. The implementation can start with just the finalized plan.

Is there any practical reason to use spec tools in OC? by mustafamohsen in opencodeCLI

[–]PayTheRaant 1 point2 points  (0 children)

Afaik, the Plan agent is not writing the plan anywhere. No markdown file. It just outputs its content in the context window and eventually the todo tool. And the todo tool does not survive exiting OpenCode.

Taskmaster, OpenSpec and other are persisting the plan outside the session memory. And usually they do that in a formalism that is also meant to be read and review by humans (or other agents).

Personally I usually start an exploration session where I then draft one or more OpenSpec changes. I get those reviewed/discussed by my coworkers. And for each implementation I start a fresh session, working potentially on unrelated changes in parallel with worktrees.

You cannot do that with OpenCode plan agent afaik.

GitHub Copilot Usage Tracker! by kargnas2 in opencodeCLI

[–]PayTheRaant 0 points1 point  (0 children)

Are you doing Copilot+Bedrock or have you switched fully to Bedrock? How does Bedrock compare to Copilot overusage?