Repository navigation
fix: send no analytics, traces, or crash reports off the machine - #57
Merged
Merged
Conversation
The fork shipped upstream's outside sinks: server usage events to PostHog through ingest.t3.codes, relay traces to Axiom from server, web, and mobile, and mobile crash reports through expo-observe. Each is now disabled at one point in code, so no build config or baked key can turn it back on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fork shipped upstream's outside sinks: server usage events to PostHog through
ingest.t3.codes(on by default, key baked in), T3 Connect relay traces to Axiom from server, web, and mobile, and mobile crash reports and launch timings through expo-observe.Each is disabled at one point, so callers and settings stay as upstream has them and no build config or baked key can turn one back on:
AnalyticsService.layeris a no-op.relayTracing.layernever builds an OTLP exporter.https://observe.invalidand dispatching is configured off; the "Send crash reports" toggle is removed.UI copy and docs now say nothing is sent.
docs/internals/product-analytics.mdlists the 3 choke points for future upstream syncs. User-configured OTLP export to your own receiver is unchanged.Tests: the web runtime and mobile tracing tests now assert no request is made even with trace credentials set.
vp run check:changedpasses.Model: Claude Opus 5.5, harness: Claude Code in PseudoCode.
🤖 Generated with Claude Code