When OpenCode tries to build Go packages using a Chinese proxy
3 points
5 hours ago
| 1 comment
| mastodon.social
| HN
rcarmo
5 hours ago
[-]
This happened to me an hour ago, and I thought it would be an interesting thing for the HN crowd to see - I had a transient DNS failure and OpenCode (which is running inside Toad, a TUI ACP front-end I prefer) decided to go get via a Chinese proxy. Fortunately I was using it inside a container (https://github.com/rcarmo/toadbox).

Now, this is interesting for several reasons--the first is that even with tool whitelisting this kind of thing might happen, and the second is the _why_. I happen to know about how popular Go is in China and that the proxy approach is... well... kinda official, but it's also a great demonstration of how LLMs leverage "knowledge" in a completely non-linear way.

I'm also _very_ curious as to what model OpenCode is invoking by default for this (I know they have several--I was just using it out of the box, and deleted the container, so we'll probably never know...).

reply
vorticalbox
4 hours ago
[-]
What model were you using? This isn’t an opencode or any other agent issue. the model chose to do this.
reply
rcarmo
4 hours ago
[-]
I was using the OpenCode free model defaults. This was a test setup, so I didn't configure anything - toadbox just installs toad, which then lets me install and run OpenCode without any configuration.

Edit: digging around in a fresh container the default model I'm getting is `big-pickle`, and I have to assume that this is the one that decided to use that proxy.

reply