cordyceps: Instructions file for GitHub Copilot

Copilot Instructions

Browser-Use Context Implementation for Chrome Extension

Core Requirements

• Environment: Chrome extension side panel with custom Cordyceps engine (Playwright-like but Chrome extension compatible)
• No Playwright Dependencies: Must use Cordyceps APIs and Chrome extension APIs exclusively
• CSP Compliance: No dynamic code execution, no eval(), no new Function()
• Extension Limitations: Work within browser security model and extension permissions

API Mapping Guidelines

1. Page Management

// Replace Playwright context/pages with Cordyceps BrowserWindow
// Playwright: context.newPage()
// Cordyceps: browserWindow.newPage()
// Chrome Extension: Use chrome.tabs API for tab management

2. Element Interaction

// Replace Playwright ElementHandle with Cordyceps Locator/ElementHandle
// Playwright: elementHandle.click()
// Cordyceps: locator.click() or elementHandle.click()
// Use existing Cordyceps element interaction patterns

3. Network Monitoring

// Replace Playwright network events with chrome.webRequest
// Playwright: page.on('request', handler)
// Chrome Extension: chrome.webRequest.onBeforeRequest.addListener()
// Implement _waitForStableNetwork using chrome.webRequest API

4. Screenshot Functionality

// Use Cordyceps screenshotter instead of Playwright
// Playwright: page.screenshot()
// Cordyceps: page.screenshot(progress, options)
// Already implemented in Cordyceps system

5. Cookie Management

// Replace Playwright cookies with chrome.cookies API
// Playwright: context.cookies()
// Chrome Extension: chrome.cookies.getAll()
// File operations must use chrome.storage or chrome.downloads

6. Navigation & History

// Use Cordyceps navigation methods
// Playwright: page.goBack()
// Cordyceps: page.goBack(options)
// Leverage existing navigation tracking in Cordyceps

Implementation Patterns