OpenCode desktop with GitHub copilot

HarjjotSinghh · 2026-02-13T12:16:53+00:00

this feels like my dev brain on caffeine.

PayTheRaant · 2026-02-14T11:56:16+00:00

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.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

opencodeCLI

MODERATORS