Add Brave CDP automation, replace Oracle browser mode
Connects to user's running Brave via Chrome DevTools Protocol to automate ChatGPT interaction. Uses puppeteer-core to open a tab, send the prompt, wait for response, and extract the result. No cookies, no separate profiles, no copy/paste. Just connects to the browser where the user is already logged in. One-time setup: relaunch Brave with --remote-debugging-port=9222 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
72
node_modules/devtools-protocol/pdl/domains/Extensions.pdl
generated
vendored
Normal file
72
node_modules/devtools-protocol/pdl/domains/Extensions.pdl
generated
vendored
Normal file
@@ -0,0 +1,72 @@
|
||||
# Copyright 2017 The Chromium Authors
|
||||
# Use of this source code is governed by a BSD-style license that can be
|
||||
# found in the LICENSE file.
|
||||
#
|
||||
# Contributing to Chrome DevTools Protocol: https://goo.gle/devtools-contribution-guide-cdp
|
||||
|
||||
# Defines commands and events for browser extensions.
|
||||
experimental domain Extensions
|
||||
# Storage areas.
|
||||
type StorageArea extends string
|
||||
enum
|
||||
session
|
||||
local
|
||||
sync
|
||||
managed
|
||||
# Installs an unpacked extension from the filesystem similar to
|
||||
# --load-extension CLI flags. Returns extension ID once the extension
|
||||
# has been installed. Available if the client is connected using the
|
||||
# --remote-debugging-pipe flag and the --enable-unsafe-extension-debugging
|
||||
# flag is set.
|
||||
command loadUnpacked
|
||||
parameters
|
||||
# Absolute file path.
|
||||
string path
|
||||
returns
|
||||
# Extension id.
|
||||
string id
|
||||
# Uninstalls an unpacked extension (others not supported) from the profile.
|
||||
# Available if the client is connected using the --remote-debugging-pipe flag
|
||||
# and the --enable-unsafe-extension-debugging.
|
||||
command uninstall
|
||||
parameters
|
||||
# Extension id.
|
||||
string id
|
||||
# Gets data from extension storage in the given `storageArea`. If `keys` is
|
||||
# specified, these are used to filter the result.
|
||||
command getStorageItems
|
||||
parameters
|
||||
# ID of extension.
|
||||
string id
|
||||
# StorageArea to retrieve data from.
|
||||
StorageArea storageArea
|
||||
# Keys to retrieve.
|
||||
optional array of string keys
|
||||
returns
|
||||
object data
|
||||
# Removes `keys` from extension storage in the given `storageArea`.
|
||||
command removeStorageItems
|
||||
parameters
|
||||
# ID of extension.
|
||||
string id
|
||||
# StorageArea to remove data from.
|
||||
StorageArea storageArea
|
||||
# Keys to remove.
|
||||
array of string keys
|
||||
# Clears extension storage in the given `storageArea`.
|
||||
command clearStorageItems
|
||||
parameters
|
||||
# ID of extension.
|
||||
string id
|
||||
# StorageArea to remove data from.
|
||||
StorageArea storageArea
|
||||
# Sets `values` in extension storage in the given `storageArea`. The provided `values`
|
||||
# will be merged with existing values in the storage area.
|
||||
command setStorageItems
|
||||
parameters
|
||||
# ID of extension.
|
||||
string id
|
||||
# StorageArea to set data in.
|
||||
StorageArea storageArea
|
||||
# Values to set.
|
||||
object values
|
||||
Reference in New Issue
Block a user