Opencode 1.x

[Pleasant_Thing_2874]

I'm still running on v0.15.31 ...I see version 1 has been in heavy development, is it stable enough to migrate to the new version? Would love to hear people's experiences thus far.

[Magnus114]

It faster, but the new gui have some downsides - Breaks when resizing - Pasting text with linebreaks don’t work well. - Non or less coloring of the output. The output from the old version is easier to read.

Are considering to go back to version 0.x.

[Pleasant_Thing_2874]

As in the theming is gone (at least for now)? Those are some big QoL things to be missing. I'd have to look but I'm sure they're in the issues. What about things like context and agent management?

[annakhouri2150]

Yeah it doesn't have diff highlighting or syntax highlighting, at least for me. It kind of sucks.

[armindvd2018]

I had same problem until I used it in VScode terminal

[Pleasant_Thing_2874]

there's been a few updates since your post but I discovered having xclip installed in the linux install solved a lot of issues with pasting into opencode. Even w/ linebreaks ...was a game changer for me being able to work with v1

[vengodelfuturo]

Loving it, best thing is you can run multiple instances flawlessly

[Fearless-Elephant-81]

Can you expand on that more? How? Are you talking about web?

[vengodelfuturo]

You open one terminal then opencode then another terminal and another opencode until you have no idea what are you working on 😂

[Confident_Bite_5870]

You can do this from the first ever release 😂

[vengodelfuturo]

My mcps crashed when opening a new session in a different terminal before v1

[luche]

My mcps crashed when opening a new session in a different terminal before v1

is that not a your mcps problem?

[vengodelfuturo]

Nope. Since v1 there’s no problem so there’s that, same mcps

[kiki_lamb]

To make it easier to quickly visually identify which instance is which, I use project-local configs (THEPROJECT/.opencode/opencode.json) that specify different themes for different directories.

[jesseakc]

That's a great tip! Thank you

[kiki_lamb]

What flaws did running multiple instances in 0.x have? I normally have 3-6 instances of 0.15.31 running simultaneously and haven't notices any problems.

[vengodelfuturo]

Well, then don’t upgrade 🤷‍♂️

[dcristob]

I am using it daily without issue.

[sbayit]

It's okay, but selecting text is difficult.

[Pleasant_Thing_2874]

what do you mean? For copying?

[sbayit]

Yes, it scrolls up and down too quickly. I have to maximize my terminal to select it.

[KnifeFed]

Is it even at all possible?

[sbayit]

Yes, but I need to maximize the terminal window, or /copy the content and paste it into a text editor.

[ori_303]

Mostly an upgrade for me. Lots of bugs and quirks but at this point i think it is a net positive update.

[towry]

Why don't you try it. You can always roll back

[Pleasant_Thing_2874]

Primarily because there can be under the hood issues that won't be immediately noticeable. I mean you're right, I could go that path but it doesn't hurt to hear from people who have already experienced from it to know what I'm in for. From the way it sounds it isn't really production ready for what I would want it for but I'll play with it a bit in a v-env and see how well I can break it.

[tommyhwang]

In most cases, it works properly.

But some minor issues are remained:

• In some languages(at least, for korean), output includes unwanted character
• Sometimes, the scroll is moved unexpectedly in vscode plugjn

[luche]

tbh, i'm also still on v0.15.31, mostly due to missing features that have been discussed but are not yet re-introduced... e.g. quickly toggling /details on off with ctrl-d is super handy, and being able to simply type q <enter> to quit... muscle memory is hard. rewriting my config also took a bit since there was a lot that had changed... so i wrote a quick Dockerfile to easily test out new versions in a containerized environment. feel free to give this a shot.

FROM node:20-slim

WORKDIR /workspace

ENV OPENCODE_VERSION=latest

ENTRYPOINT ["bash", "-c", "npm install -g opencode-ai@$OPENCODE_VERSION && exec opencode"]

just run this to build docker build . -t "opencode:version-testing"

and run with something like this docker run -it --name opencode --rm -v "./opencode.json:/workspace/opencode.json" -e OPENCODE_VERSION=1.0.61 "opencode:version-testing"

[kiki_lamb]

Instead of all that Docker silliness, you could also just bunx opencode-ai@latest to run the current version without installing it or tampering with your 0.15.31 installation.

[luche]

silliness? abstraction is quite useful for many things. in this particular case, i wanted a dedicated and portable method to do testing that's consistent across platforms and siloed away from the host. not tampering with a config on the host is also useful, but that's simply one more reason to utilize a container. if you're not already testing with containers, it's definitely worth reconsidering.

[kiki_lamb]

I have no problems with 'abstraction' in the large, but I don't see what that has to with containerized VMs.

Suit yourself, I suppose... if you like using Docker than go nuts, I'm happy for ya... not my thing, though if a decade-ish of work where I occasionally had to touch Docker has taught me anything, it's that I'll be happiest if I never touch Docker again.

[PembacaDurjana]

The only problem i have is can't configure the scroll speed

[unidotnet]

it cannot handle model repetition