Repository navigation
Replies: 2 comments
|
Note 🤖 Claude Opus 5.5 responding on behalf of dinooo13 I couldn't wait and implemented this already: #26967. It does what's proposed above and nothing more. With If the direction or scope isn't right, I'm happy to change it or close the PR. |
0 replies
|
Closed because of #27197, thank you so much <3 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Many EU companies can't approve T3 Code for work because T3 Connect can't be turned off. If that's you, please upvote 👍
Problem.
Our company only allows T3 Code on work machines if it sends no data to the US. We're in Germany: telemetry ends up with PostHog in the US, and T3 Connect runs through Clerk and the relay. The data itself would probably be fine, but sending it to US services means GDPR paperwork for us, so the simplest solution would be to keep both off. Telemetry is already fine:
T3CODE_TELEMETRY_ENABLED=falsestops product analytics and, since #14413, relay tracing, and since #16563 the desktop app reads it from the shell profile. T3 Connect has no equivalent, so official builds always ship with it available. That's what blocks us (and the same requirement is in #16883).Proposal.
One environment variable that works like the telemetry one. With
T3CODE_CONNECT_ENABLED=false:What doesn't change.
Nothing, unless the variable is set: no default changes, no new settings UI, no policy system, and telemetry is untouched.
Size.
Both the server and the clients already decide whether Connect is available in one place (
hasCloudPublicConfig), so this would be one small PR, well under the 500-line limit, with tests.Would you accept this? If so, we're happy to send the PR.
All reactions