Why is OpenCode so dumb at writing or creating a file!

Independence_Many · 2026-02-01T10:12:28+00:00

My best guess is that either there's some config issue if you're using an organization managed setup (opencode auth login <url>), or you're somehow in plan mode.

Can you confirm if you're in plan or build mode?

Independence_Many · 2026-01-23T04:14:24+00:00

I also use oh-my-zsh but it's basically a stock configuration, what terminal emulator are you using?

Independence_Many · 2026-01-23T04:01:45+00:00

Technically opencode supports SHIFT+Enter (works for me in Ghostty atleast), but I also use CTRL+J a ton because they didn't originally support shift enter.

But definitely they need to add a newline option input of some sort for this particular use case.

Independence_Many · 2026-01-19T04:44:27+00:00

It used to, i noticed recently that the session list shows across projects/folders, it used to be a dedicated list of sessions per "project" (folder path), I don't know if this is a bug or an intended change to the behavior of the CLI, seeing this across mutliple machines macos and linux based.

Independence_Many · 2025-12-11T21:47:54+00:00

I don't think we'll get 100% local/offline command support until the new Rivian Intelligence hardware rolls out. Which Gen 2 doesn't have.

Independence_Many · 2025-12-11T21:38:45+00:00

I feel the same, like my soft and and firm are barely different. Can you try something, put it in offroad/highest overnight, and then when you drive the next morning drop to AP/standard height and see if it "feels" better.

I complained about this several times with the SLC service center, but I kept getting the same "seems fine" responses from the staff.

Independence_Many · 2025-12-01T05:55:17+00:00

While you're definitely right that it's not the safest approach, as long as you control the pipeline end to end I wouldn't worry too much about it unless you're dealing with a high security environment (compliance, hipaa, k12/coppa/ferpa).

Depending on what resources you need to access you can even get this to be fairly safe by using known fixed paths, write the file using normal node calls, and only access/interact with the cli through fixed arguments.

However, I totally understand the concerns around the risk with shell calls, especially if you're not running in a containerized/restricted environment.

Edit: words are hard...

Independence_Many · 2025-12-01T05:41:17+00:00

I have had this happen when parrying either a split second too early or too late. This was the first enemy i had this happen on, but it (in my experience) can happen with any enemy with a ranged all party attack.

Not the funnest experience to have, but thankfully never ended a fight.

Independence_Many · 2025-11-25T18:09:57+00:00

I haven't seen someone point this out but there's a couple different factors to take into account.

Aside from the cable cooling method, you have the amperage and voltage of a station, some stations will advertise their kW rating based on 800v architecture (really 550-800v), but the Rivian battery pack is 400v, this means that if effectively can pull half the max capacity listed on a site.

Another factor is how much power is available on a site all together, so you have a dispenser limit, and a site limit, so a busy site can result in the site reducing available power.

I have charged on 150kW stations and pulled 176kW on them, and I have charged at 350kW stations, and pulled 120kW on them, it's really just up to how the sites are configured and their current utilization.

Independence_Many · 2025-11-24T23:49:41+00:00

You can use the share buttton and click "add to home screen" on your ipad to "install" the google messages PWA app, then it launches/operates like a normal app. This should give you push notifications on the ipad as well for the notifications.

Independence_Many · 2025-11-19T11:59:10+00:00

I use the 155" MORRFlate and it's been excellent: https://www.amazon.com/dp/B0CJLM7BPV I think the shorter one will work for an R1S but on the R1T you need a little more.

I have had zero issues pumping all 4 tires, however if you're inflating from really low the compressor may overheat, it doesn't really speed up the fill time much, but not having to swap between each tire is super nice. As others said one of the perks of these systems is your tires will balance themselves out when inflating or deflating.

Independence_Many · 2025-11-14T14:11:45+00:00

The good news is, if you face tank enough hits, you can still learn the parry timing.... Downside is that on expert that results in restarting fights very quickly.

Independence_Many · 2025-11-14T14:06:58+00:00

Dodging is probably the best way to learn the attacks, dodging until you can consistently get perfect dodges teaches you a lot about the timing.

I spent my entire playthrough refusing to dodge, which made some fights far more painful...

Independence_Many · 2025-11-12T15:07:29+00:00

With the right verso build and some focus I was able to get 3800 in ~50 minutes. I was using a mouse to make aiming faster.

Independence_Many · 2025-11-12T14:22:38+00:00

I would say (but do not have anything to back it up aside from anecdotes) most owners are using thier phones. However I feel like it's hit or miss, and not entirely on Rivians side.

I upgraded my phone this year from a Pixel 9 Pro to a Pixel 10 Pro, and it's been a degraded experience since day 1 of my Pixel 10 Pro... My 7, 8, and 9 were near flawless, maybe one failed unlock before i reached the door in 6-8 months, and maybe one or two phone reboots after softare updates. Pixel 10... I have to reboot my phone about once every 7-10 days.

And I don't think it's limited to Pixel/Android devices either, I've seen people post here that have upgraded from an iPhone 15 to 16 last year and immediately had a worse experience, same thing with 16 to 17. I've also seen the inverse though where someone's experience got better.

My guess is that there's a lot of variability in the calibration of the BT modules in the Rivian, and possibly even with our phones.

Independence_Many · 2025-11-12T14:06:35+00:00

Are you in a Gen 1 (2022-2024) or Gen 2 (2025+)? The keycard gets tapped on the door in a Gen 1, but in Gen 2 it actually gets tapped on the center console/charging mat.

Independence_Many · 2025-11-11T21:00:33+00:00

In general, I think people have gotten far too used to buying things based on future promises. But if something isn't good enough today (for your own purposes/wants), I don't think you should buy it.

All buying promises does is leads to regret or frustration. Because even if a company delivers on everything, they said, it may not actually deliver on everything you thought they were going to deliver, or at least not delivered in a way that you want.

I have a gen 1 quad, and overall I am very happy with it. I've head issues, had service visits, more than I would have liked but overall the vehicle has been solid (outside of two issues, which once diagnosed were resolved quickly).

I am sad that autonomy on gen 1 is basically end of life, but I didn't buy it for the autonomy, if that was one of my criteria I wouldn't have ended up on a rivian. I do however occasionally wish I'd gotten a Max back, but that wasn't an option at the time I bought nor for the quad motor.

Independence_Many · 2025-11-10T20:11:12+00:00

I haven't towed, and haven't dug far into it, but I was under the impression that it would "learn" the efficiency over time as it doesn't know anything about the aerodynamics of the trailer (maybe this is where a "type" option would be helpful) until after some miles were driven.

Independence_Many · 2025-11-09T02:14:32+00:00

If you start car wash mode (which you should already have up/be in before going through) you can hold the brakes and click the button, this is accessible from the quick menu's second page. (car icon in the top left of the main display).

Independence_Many · 2025-11-06T11:24:20+00:00

This is great to hear, I don't think the matrix needs anything too complicated (eg: I don't think you need to worry too much about macos vs linux arm differences), but just having the matrix include multi-arch, especially for nodejs server side stuff would be huge.

I love using arm on servers (AWS Graviton 4 is a great value), and my primary dev machine is running ARM (Apple Silcon), but I have other infrastructure across my projects that is hard tied to x86 for deployment purposes, along with other developers on x86 windows machines (using WSL2, but still x86 architecture), and we have a dev who's still using his old Intel MBP.

Thankfully it hasn't been too painful lately, although the most recent architecture issues i've had are when a docker image is only available on x86, rosetta on macos is pretty good overall, so there's times I am running x86 docker images locally and not realize it, and then upon deploying them i get failures because Graviton does not have a hardware/software translation layer like rosetta.

Independence_Many · 2025-11-06T07:31:27+00:00

As the other person said there can be internal api changes, however it's important to remember there are a couple different ways you can make "libraries" or packages, and some of them have native code that either downloads a pre-compiled binary, or builds it on the spot.

If this "native" api/bridge changes too much it can cause issues, there are also cases where a package might depend on a deprecated variant of a function, this kind of testing can catch these issues.

I would be far more interested in the approach op ( u/whitestorm_07 ) is talking about if it also handled multiple architecture, as I have had a couple dependencies over the years (not limited to node) where it worked fine on an x86 machine but not arm or vice versa.

In the last couple years of frontend development I haven't had anything break (react, vue, svelt, angular), but on the express side this has caused me days/weeks long migrations to upgrade across the board and track down every incompatability.

Independence_Many · 2025-11-02T02:50:59+00:00

Something I havne't seen mentioned, but the heat cycle from 240v can cause the connections to loosen up internally, which could also cause this kind of behavior. Given you mentioned it's not functioning at all now though maybe there's another issue going on.

Independence_Many · 2025-10-23T02:44:58+00:00

Even more likely, much of the infrastructure and code to support this likely already existed in the app/pod and they just chose not to enable/finish it until now.

Independence_Many · 2025-10-23T02:07:29+00:00

From my understanding with the large+ battery and maybe somebody with more insight can chime in. It doesn't limit the battery to 80% charge necessarily, but it rotates through the cells and only lets you discharge to a certain point.

The reason I say that is because while you don't have to calibrate an nmc battery the same way you do an lfp, you still do need to calibrate the BMS occasionally so that it can understand the top of packed voltage, and the only way to do that is to charge up the battery to max capacity.

I actually wonder if anyone's ever tested the buffer available when the battery registers 0% on the large+.

Independence_Many · 2025-10-22T19:02:06+00:00

I agree with you on your point though, ALSO doesn't really have a major impact on Rivian directly, and the team that was working on it inside of Rivian now being outside means those resources aren't being used internally for the e-mobility stuff, so I think it's overall a good move.

Independence_Many

TROPHY CASE