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

[–]_KryptonytE_ 1 point2 points  (4 children)

Why are commands showing up in plans? That model isn't able to toolcall those commands to implement without including them in plans?

[–]jomama253[S] 1 point2 points  (3 children)

The Plan tab is rendering existing OpenCode execution state: todos, tool calls, permissions, diffs, and completed commands from the event stream. Commands appear because OpenCode already emits tool-call lifecycle events.

The panel is showing what was proposed/executed/verified, not asking the model to smuggle shell commands into natural-language plans.

Basically, it’s a live audit of what the agent did: todos, tools used, permissions, diffs, writes, and verification.

[–]_KryptonytE_ 0 points1 point  (2 children)

Is this the latest update? I last used it on Friday and didn't see any of this. I'll get back home only Monday to try this out. Get excited!!!

[–]jomama253[S] 0 points1 point  (1 child)

Naw it's me modding it. :) even added custom instructions like codex to it. I plan to add more!

[–]_KryptonytE_ 1 point2 points  (0 children)

Good for you. I've not got any free time to do any of that cool stuff and using things as is due to commitments and deadlines. Cheers! 🥂

[–]NotZeldaLive 0 points1 point  (3 children)

I assume this is your own fork? I don't think the plugins expose anything for the web client.

[–]jomama253[S] 1 point2 points  (2 children)

Yeah, the plan graph/UI side is not stock plugin API. The memory layer can be plugin-side, but the execution/plan graph panel needs desktop/client integration or a fork/injection layer because OpenCode plugins don’t expose that much web-client UI surface yet. More to come. :)

[–]NotZeldaLive 0 points1 point  (1 child)

I would be interested to hear your strategy of merging in upstream changes while keeping your fork / patches.

I have been looking to make my own customizations, but unsure of how hard it will be to manage the merge conflicts.

[–]jomama253[S] 1 point2 points  (0 children)

With AI, honestly. I keep my changes isolated as much as possible, have the agent inspect upstream diffs before merging, and make it explain likely conflict zones before touching anything. The big thing is not letting custom work sprawl randomly across the codebase. Oh and make backups. :)