You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@thdxr I have noticed that the titles of sessions is computed outside of my network and my own locally hosted LLMs. I noticed this because I have nftables rules that block access to outbound IPs, and this feature of naming the session only works when I disable nftables. What is going on with that, and why is opencode not operating private by default?
Yes, the Github bot does point to relevant issues, this is concerning and is absolutely a privacy concern. This sucks, especially when you read #459 (comment), it comes across as misleading, if not an outright lie. Why would you claim that it's only communicating with your own LLM, when it clearly is sending data to another internet connected model on the side?
Reacted by Vrishabh Lakhani, Victor, Jeremy Akers, strawberrymelonpanda, Cody Ebberson, Madeleine North, Sureal Cereal, Paul, thisago, blockfeed and 8 more
Reacted by Ted Robertson, Cody Ebberson, Madeleine North, Sureal Cereal and Miguel P
You can get around this by adding: "disabled_providers": ["opencode"],
OR "small_model": "ollama/gpt-oss:120b"
What is happening:
you have no whitelisted cheap model available
we are falling back to running title gen using gpt-5-nano on zen provider (NO telemetry collected)
Removing this behavior makes people upset (why am I being billed for model X, why is it using model Y, etc etc)
Luckily this is entirely configurable on your side to resolve.
And note that referenced comment is accurate, there is no telemetry
Reacted by Santiago M. Mola, Michał Matyas, ypashkov, seaweeduk, Matthew Groff, UpInAir, Rafał Krzyważnia, Mirrowel, KrisDev and Walter
Reacted by Victor, strawberrymelonpanda, Madeleine North, JeongJuhyeon, Fernando Canteruccio, trompx, M4rtineski, daniel-capital, matt-nt, Miguel P and 7 more
Luckily this is entirely configurable on your side to resolve.
The issue title is that there OpenCode is not private by default, which is still an issue regardless of the configurability you described. There is also the issue of the the lack of care taken with communicating how OpenCode works with your data.
If it's not private by default, why try to reassure people that it is like in #459 (comment)? Do you know how your own codebase is operating, or do you not take the care needed to assure that data is not sent abroad?
Removing this behavior makes people upset (why am I being billed for model X, why is it using model Y, etc etc)
The use case where you send data to third parties and providers is entirely separate from the use case where the model is running locally. It is not acceptable to somehow blend them together into a mush where some things are running locally and some things aren't, it's a violation of trust.
Reacted by Ted Robertson, Victor, Areiser, Martin Dougiamas, strawberrymelonpanda, Madeleine North, Michael Hood, JeongJuhyeon, Sureal Cereal, Michael Liu and 24 more
This behavior, as well as "disabled_providers": ["opencode"] should probably be documented at https://opencode.ai/docs/enterprise/#data-handling
This page suggests data is not being sent to LLM providers other than the ones setup by the user, but as this issue shows, it's not always the case. So "disabled_providers": ["opencode"] is likely to be a prerequisite for most enterprise users.
Reacted by Martin Emrich, benjamin liu, chrislawso, Paul, David Koňařík, sloopgoop, Navin Francis Shajan and Aleksandr Mikhailov
My complaint is about defaults and who this tool is designed for. If it is not private by default, then it is not designed for people running models locally, and this tool should be added to a list of tools to avoid if you value your personal data privacy. The words "enterprise", "billing" and "provider" are business and corporate terms that are completely alien to anyone trying to run this stuff locally, i.e regular people.
Reacted by A Podlesny, Max, Marijan Petričević, toastal, Roni, Victor, pp, szetakyu, Genmutant, Alberto Garcia Illera and 26 more
Reacted by Ted Robertson, Aymen, Roni, szetakyu, Wolfgang Fahl, Alberto Garcia Illera, blockfeed and luyu
@thdxr - Is there any guide / documentation to know settings to use ensuring opencode remains private when using in enterprise environment without risking data leakage.
Reacted by Daniel Vélez, lmeyer, Sureal Cereal, Teddy Jardine, cp-mromaszkin, Chris Kuethe, thisago, jo-nathan-cw, lawm, Imran Meerza and 6 more
@shantur I tried to use the below lines in my ~/.config/opencode/opencode.json config, while hoping that OpenCode won't be "calling home" unless I allow it:
There's a nice piece of software I love deeply with all my heart - OpenSnitch application firewall (https://github.com/evilsocket/opensnitch). It warns you and allows to block whatever network calls your apps are making. But the frontend is a gui thing, so if you're running opencode remotely on some headless server, it's not an option. Need to find something similar for TUI.
And yeah, even though the opencode is a good product with a solid dev team behind it, I have to say that privacy-wise unfortunately it's a nightmare :-( If I don't find a way to shut it, I'll go find an alternative. Heard some good feedback on pi
Reacted by mejobloggs, Birdthatcantfly, ⚫Robert⚫, Théo Gieruc and Aaron Fabbri
There's a nice piece of software I love deeply with all my heart - OpenSnitch application firewall (https://github.com/evilsocket/opensnitch). It warns you and allows to block whatever network calls your apps are making. But the frontend is a gui thing, so if you're running opencode remotely on some headless server, it's not an option.
@kha84 You can install the OpenSnitch traffic monitoring daemon on a the headless server, and the GUI on your local machine:
In the end, the issue for pointing out there's no privacy (at all) in a privacy-boasting agentic harness, after all the back-and-forth virtue signaling and hand-waving of "we're actually doing stuff, we just might have overlooked it, see? [shows irrelevant one-line change]" is being closed as "not planned". So much for "Open"Code.
Reacted by Sureal Cereal, Birdthatcantfly, Tsung-Han Yu, Ziv-Ink, luyu, bharloe, Tv, mschfh, Mark Steward, Purple Platinum Virgate and 7 more
Activity
MatthewCroughan commentedon Jan 24, 2026
Related to #459
rekram1-node commentedon Jan 24, 2026
@MatthewCroughan can u share
opencode debug configMatthewCroughan commentedon Jan 24, 2026
@rekram1-node
MatthewCroughan commentedon Jan 24, 2026
I had simply followed https://docs.ollama.com/integrations/opencode and wrote the following
~/.opencode/opencode.jsongithub-actions commentedon Jan 24, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
MatthewCroughan commentedon Jan 24, 2026
Yes, the Github bot does point to relevant issues, this is concerning and is absolutely a privacy concern. This sucks, especially when you read #459 (comment), it comes across as misleading, if not an outright lie. Why would you claim that it's only communicating with your own LLM, when it clearly is sending data to another internet connected model on the side?
rekram1-node commentedon Jan 24, 2026
Here is the exact logic:
opencode/packages/opencode/src/provider/provider.ts
Line 1128 in 32e6bca
You can get around this by adding:
"disabled_providers": ["opencode"],OR
"small_model": "ollama/gpt-oss:120b"What is happening:
Removing this behavior makes people upset (why am I being billed for model X, why is it using model Y, etc etc)
Luckily this is entirely configurable on your side to resolve.
And note that referenced comment is accurate, there is no telemetry
MatthewCroughan commentedon Jan 24, 2026
The issue title is that there OpenCode is not private by default, which is still an issue regardless of the configurability you described. There is also the issue of the the lack of care taken with communicating how OpenCode works with your data.
If it's not private by default, why try to reassure people that it is like in #459 (comment)? Do you know how your own codebase is operating, or do you not take the care needed to assure that data is not sent abroad?
The use case where you send data to third parties and providers is entirely separate from the use case where the model is running locally. It is not acceptable to somehow blend them together into a mush where some things are running locally and some things aren't, it's a violation of trust.
smola commentedon Jan 24, 2026
This behavior, as well as
"disabled_providers": ["opencode"]should probably be documented at https://opencode.ai/docs/enterprise/#data-handlingThis page suggests data is not being sent to LLM providers other than the ones setup by the user, but as this issue shows, it's not always the case. So
"disabled_providers": ["opencode"]is likely to be a prerequisite for most enterprise users.MatthewCroughan commentedon Jan 24, 2026
My complaint is about defaults and who this tool is designed for. If it is not private by default, then it is not designed for people running models locally, and this tool should be added to a list of tools to avoid if you value your personal data privacy. The words "enterprise", "billing" and "provider" are business and corporate terms that are completely alien to anyone trying to run this stuff locally, i.e regular people.
MatthewCroughan commentedon Jan 24, 2026
FWIW, I don't want to come across as entitled, it's just not designed for me (and others like me) if the defaults are not privacy first.
MatthewCroughan commentedon Jan 24, 2026
Does the "Optional"
/sharefeature mean that opencode is just hoovering up all data by default?If so, it's another example of why it should be added to a list of things to avoid.
Who wants to go around disabling features all day just to get some basic privacy?
MatthewCroughan commentedon Jan 27, 2026
When a version update is done, and we open
opencode, we see the followingBut then, the TUI is permanently black. This resolves itself if network access is granted to the program.
Any ideas what nasty stuff is happening?
@smola
MatthewCroughan commentedon Jan 27, 2026
Even after removing all the state that opencode creates, I am unable to open the opencode program.
rm -rf /home/virus/.opencode/node_modules/ /home/virus/.opencode/.gitignore /home/virus/.opencode/config.json /home/virus/.opencode/bun.lock ~/.local/share/opencode/ ~/.cache/opencode/ ~/.local/state/opencode ~/.config/opencode/ ~/.opencode/It appears that for opencode to open for the first time, it must be connected to the internet.
37 remaining items
thdxr commentedon Mar 26, 2026
1.3.3 also embeds the webui in the binary now
not sure if there are any other concerns remaining
shantur commentedon Apr 13, 2026
@thdxr - Is there any guide / documentation to know settings to use ensuring opencode remains private when using in enterprise environment without risking data leakage.
kha84 commentedon May 1, 2026
@shantur I tried to use the below lines in my
~/.config/opencode/opencode.jsonconfig, while hoping that OpenCode won't be "calling home" unless I allow it:... but quick-n-dirty inspection shows me it still keep calling some external IPs, even though no providers are configured (fresh install):
There's a nice piece of software I love deeply with all my heart - OpenSnitch application firewall (https://github.com/evilsocket/opensnitch). It warns you and allows to block whatever network calls your apps are making. But the frontend is a gui thing, so if you're running opencode remotely on some headless server, it's not an option. Need to find something similar for TUI.
And yeah, even though the opencode is a good product with a solid dev team behind it, I have to say that privacy-wise unfortunately it's a nightmare :-( If I don't find a way to shut it, I'll go find an alternative. Heard some good feedback on pi
rekram1-node commentedon Jun 23, 2026
Automated: closing question issues.
GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.
If this is a bug or feature request, please open a new issue with the appropriate template.
tredondo commentedon Jun 24, 2026
@kha84 You can install the OpenSnitch traffic monitoring daemon on a the headless server, and the GUI on your local machine:
https://github.com/evilsocket/opensnitch/wiki/Nodes
SynapseScribe commentedon Jun 24, 2026
why does opencode connect so often to models.dev, even in background? i am using a local model running in lm studio (server).
rekram1-node commentedon Jun 24, 2026
You can disable if u want to, but we have a model api that we use to track what providers have which models, how much they cost etc.
It checks the list often so that u can use new models without having to upgrade everytime.
SynapseScribe commentedon Jun 24, 2026
How to disable or reduce the no. of checks to models.dev? I also see periodic checks towards github, even if auto update is disabled
daniel-capital commentedon Jul 8, 2026
In the end, the issue for pointing out there's no privacy (at all) in a privacy-boasting agentic harness, after all the back-and-forth virtue signaling and hand-waving of "we're actually doing stuff, we just might have overlooked it, see? [shows irrelevant one-line change]" is being closed as "not planned". So much for "Open"Code.
privacy: GRAY_OFFLINE master switch + scope session header to zen
insanowsky commentedon Oct 17, 2026
well well well...
0.2.2 polish: privacy gate, plugin dispatch fixes, image-preview remo…
SeungHuLee commentedon Oct 17, 2026
it's so over
thdxr commentedon Oct 17, 2026
This issue was resolved back in March as we stopped offering free title gen models by default