all repos — sz-chrome-remote-cdp @ master

pi-browser-harness, patched to drive a Chrome on another host over CDP, with castle_cdp_search web search

.github/ISSUE_TEMPLATE/feature_request.md (view raw)

 1
 2
 3
 4
 5
 6
 7
 8
 9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
---
name: Feature request
about: Suggest an improvement or new browser-control capability
title: "[Feature]: "
labels: enhancement
assignees: ""
---

## Problem Statement

What problem are you trying to solve? Describe the workflow, limitation, or browser-control gap.

## Proposed Solution

Describe the behavior you would like to see. If this is a new browser tool, include the proposed `browser_*` name, inputs, and expected output if you have a preference.

## Alternatives Considered

What alternatives or workarounds have you tried? For example, could this be handled with `browser_execute_js`, `browser_http_get`, or `browser_run_script` today?

## Additional Context

Add examples, screenshots, links, or related Chrome DevTools Protocol details that would help explain the request.