Hey! I work on OpenCode, so thank you for this measured reply ;)

Just wanted to add a few things:

- We actually don't do tool-call pruning any more. But compaction is a necessary evil for the time being. There's only so much context window, and if you wish to keep working on the same task for a long time, the model needs to summarize its current progress so it can continue without hitting its token ceiling.

- With V2 (in beta atm), we have a new system for handling changing system instructions (AGENTS.md files, available skills, etc.) that avoids cache misses at all costs, while still giving the robot the newest information. I recorded a little video about it here:

https://x.com/kitlangton/status/2075749116760457346/video/1

▲

sgallant 21 hours ago | parent | next [-]

Just checked out the video...you, my friend, could be a professional voice actor (assuming that job still exists in the future).

▲

vitamark a day ago | parent | prev | next [-]

Can you shed some light on what's the deal with the new interface (web/desktop)?

I updated one of my opencode containers today and had to downgrade it back because:

1. Worktree/workspace support is gone altogether. No way for agent to work in parallel on different things safely except prompting it directly to create a worktree.

2. Seeing multiple sessions properly now requires opening tabs for those?

3. In general, switching between several projects/sessions/whatever stopped working, and command palette is hotkey-only.

Issues about the new design just sit in an endless unsolved pile on GitHub which seems hopeless. And an agressive stale bot is not helping with that.

I came to OpenCode because it seemed hackable and simple, and at this point it seems like a "move fast break a lot" project that you got to live with.

(rant over, sorry if this is addressed to the wrong person, just needed to vent a bit)

▲

jayair a day ago | parent [-]

Yeah it's a big change.

Workspace support is being worked on, it was half-implemented before, so we are taking a proper pass at it now.

For switching between sessions, can you tell me about your workflow from before? Because a tab can hold a session from any project. Are you saying that opening up a tab is too heavy of an action?

GitHub issues though has been a problem from us, we deal with a ton of noise/spam.

	▲	vitamark an hour ago \| parent [-]
		As for switching between sessions — it's the hierarchy that's lost on tabs. in 1.17 I get basically a three-level hierarchy: project -> workspace -> session I could say I rarely use more than one session per workspace (not including subagents), but switching between projects as totally separate contexts works good. Tabs on the other hand are less organized, I can see them being fine for sessions in one project (although sidebar is more ergonomical on both desktop and mobile) Keep in mind that this is coming from someone who has a live browser tab counter website: https://tabs.evtn.me/

▲

steve_adams_86 21 hours ago | parent | prev [-]

Does V2 finally imminentize the eschaton? V1 has completely failed at this so far

	▲	k-langton 19 hours ago \| parent [-]
		I see what you did there ;P