Browser4 Aider Configuration

Expert guidance for AI-assisted development on Browser4, a high-performance browser automation framework. This skill provides comprehensive context for working with Browser4's multi-module Maven architecture, Kotlin codebase, and browser automation APIs.

Project Overview

Browser4 is a lightning-fast, coroutine-safe browser automation framework with:

Core Principles

When working on Browser4, always follow:

1. **最小改动 (Minimal changes)** - Make the smallest change necessary

2. **保持风格 (Maintain existing style)** - Follow established patterns

3. **清晰日志 (Clear logging)** - Use structured logging with placeholders

4. **自动校验与测试 (Automated validation)** - Ensure tests pass and coverage is maintained

Build Commands

Quick Build (Skip Tests)

**Unix/macOS:**

```bash

./mvnw -q -DskipTests

```

**Windows (cmd):**

```cmd

mvnw.cmd -q -DskipTests

```

Test Core Module

**Unix/macOS:**

```bash

./mvnw -pl pulsar-core -am test -Dsurefire.failIfNoSpecifiedTests=false

```

**Windows (cmd):**

```cmd

mvnw.cmd -pl pulsar-core -am test -D"surefire.failIfNoSpecifiedTests=false"

```

**Note:** Windows requires quoting `-D` parameters with dots: `-D"key.with.dots=value"`

Build Scripts

Module Structure

Key APIs and Components

Browser Automation

Agentic Sessions

Configuration

- `docs/config.md`

- `docs/rest-api-examples.md`

Logging Standards

Follow the structured logging format defined in `docs/log-format.md`:

```kotlin

// ✅ GOOD - Use placeholders

logger.info("Task {} finished in {} ms", taskId, cost)

// ❌ BAD - Avoid string concatenation

logger.info("Task " + taskId + " finished in " + cost + " ms")

```

Kotlin Style Guide

Example:

```kotlin

/**

* Loads a page with the specified options.

*

* @param url The target URL

* @param options Load options for browser behavior

* @return The loaded page

* @throws BrowserException if loading fails

*/

fun loadPage(url: String, options: LoadOptions): Page {

// implementation

}

```

Testing Standards

Test Location

Speed Targets

Coverage

Definition of Done

Before considering any task complete:

1. ✅ Build and relevant tests pass with no new noisy logs/warnings

2. ✅ New/changed logic includes main path + at least 1 edge case test

3. ✅ No secrets/private endpoints committed; inputs are validated

4. ✅ No arbitrary version drift (follow parent BOM)

5. ✅ Public behavior/config changes are documented

6. ✅ Performance impact assessment (if >~5% potential impact)

Common Troubleshooting

Permission Issues (Linux/macOS)

```bash

chmod +x mvnw

```

JDK Version Mismatch

Ensure you're using the JDK version required by the repository (check `pom.xml` or `.sdkmanrc`)

Windows Parameter Escaping

Always quote `-D` parameters with dots:

```cmd

mvnw.cmd test -D"key.with.dots=value"

```

Port Conflicts

Default port 8182 is occupied:

```properties

Override in application.properties

server.port=8183

```

Browser/CDP Issues

Log Storms (CDP Retries)

References

Aider-Specific Configuration

Recommended Aider settings for this project:

```yaml

Uncomment in .aider.conf.yml to use

model: gpt-4-turbo-preview

edit-format: diff

auto-commits: true

dirty-commits: false

```

Usage Tips

1. **Before making changes:** Read existing code to understand patterns and style

2. **Building:** Use the provided build scripts for your platform

3. **Testing:** Run relevant module tests before committing

4. **Logging:** Always use structured logging with placeholders

5. **Documentation:** Update docs when changing public APIs or configuration

6. **Performance:** Consider and document performance implications