Repository navigation
Forward session-bearing site feedback to the Kernel API - #259
Closed
ulziibay-kernel wants to merge 1 commit into
Closed
ulziibay-kernel wants to merge 1 commit into
ulziibay-kernel wants to merge 1 commit into
Conversation
submit_feedback site_compatibility and config_registry reports that
name a browser session are now also posted to
POST /browsers/{id}/site-reports, so the outcome lands next to the
session's telemetry instead of only in analytics. Forwarding is
fail-open and never changes the tool's result.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
submit_feedbackalready capturessite_compatibilityandconfig_registryreports to PostHog. When such a report names abrowser_session_id, the server now also posts it to the Kernel API's newPOST /browsers/{id_or_name}/site-reportsendpoint using the caller's token, so the outcome is attached to the session with its browser and proxy configuration.site-report-forwarder.tsmaps the feedback fields onto the site-report request (outcome, challenge type, provider, reproducibility, task, notes, config-registry attribution). The feedback schema only carries the registrable domain, so the report URL is the site root.Depends on kernel/kernel#5002 being deployed. Until then the forward fails quietly and the PostHog path keeps working, so this is safe to merge in either order.
Testing
bun testforsite-report-forwarder,feedback,analytics,prompts,register: 84 passbunx tsc --noEmitcleanbun run format:checkflagsAGENTS.md, which is unformatted onmain)🤖 Generated with Claude Code