Document the Browser Feedback extension in the in-app docs#795
Merged
Conversation
The Chrome browser feedback extension (element picker → comment → send to a running agent, paired under Settings → Connections) had no coverage in the in-app docs pane, no ambient tip, and no README feature bullet. - Add a new "Browser Feedback" docs-pane section covering install, pairing, sending feedback, privacy/page-access, and managing connections. - Wire it into docs-sections/index.ts and docs-pane.tsx (MousePointerClick icon, placed after Media & Sharing). - Add an ambient discovery tip (since 0.29.3) linking the new section. - Add a Browser Feedback feature bullet to the README. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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
1 participant
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.
What was audited
Docs-audit deep-dive on
next_focus: the Browser Feedback Chrome extension (apps/browser-extension/,browser-extension-settings.tsx,routes/browser-extension.ts, shipped in PR #783). The feature had no coverage in the in-app docs pane, no ambient discovery tip, and no README feature bullet.What changed
docs-sections/browser-feedback.tsx) covering: installing the developer-preview extension (download ZIP → unzip → Load unpacked), pairing a browser (Dispatch URL + six-digit code approval, per-profile 90-day revocable token), sending feedback (element picker → comment → pick a running agent → Send to agent), privacy & page access (HTTP/HTTPS grant, sanitization of form values/scripts/event handlers/srcdoc/likely-secret URL params, untrusted-context framing, HTTP acknowledgement), and managing connections (Settings → Connections revoke/disconnect). Content verified against the route handlers, the settings component, and the extension README + side-panel UI strings.docs-sections/index.tsanddocs-pane.tsx(MousePointerClickicon, placed after Media & Sharing).browser-feedback(since: 0.29.3) linking the new section, so an easy-to-miss feature buried in Settings → Connections gets surfaced.Validation
pnpm run check(server + web + browser-extension + scripts typecheck) — passpnpm run format:write/prettier --checkon touched files — cleansrc/lib/tips) — 24 passing (tip schema/uniqueness validated)Deferred to next run
Next focus written to the Brain: audit the docs-pane Worktrees section against
apps/server/src/shared/git/worktree.ts(the concurrent-create.git/configlock fix landed in #794). Backlog additions: the browser-extension feature is developer-preview only, so revisit the docs "developer preview" wording once it ships to the Chrome Web Store or gains a non-unpacked install path.🤖 Generated with Claude Code