Configuring ExploreChimp Agents

Overview

ExploreChimp is composed of multiple agents, each responsible for a specific aspect of exploration and analysis. You can configure each agent independently from the project settings to control their behavior, focus areas, and testing strategies.

Accessing Agent Settings

1. Navigate to Settings → Project Settings
2. Click on the ExploreChimp tab
3. Expand the agent section you want to configure
4. Click "Save Changes" at the top of the page to save your configuration

The settings are organized into two groups: core agents and special purpose agents.

---

Core Agents

Screen Discovery Agent

The Screen Discovery Agent is the primary exploration agent responsible for navigating your application and discovering screen states.

Initial URL

The starting URL for screen-state discovery explorations.

https://app.example.com/dashboard

Test Data Prompt

Default test data available to the agent during explorations. Use this to provide login credentials or other data the agent needs to interact with your application.

Login credentials: user@example.com / password123
Use the "Guest" account for checkout flows.

---

Bug Source Analytics Agent

The Bug Source Analytics Agent analyzes captured data from explorations to surface bugs across network, screenshot, and other data sources.

API Regex to Capture

A regular expression pattern to filter which API endpoints are captured and analyzed. Only API calls matching this pattern will be included in network analysis.

Example: ^https://api\.example\.com/.* — captures all calls to api.example.com

Leave this blank to capture all API calls.

Screenshot Analysis Default Viewports

Select which viewport sizes to use when capturing screenshots during explorations:

Viewport	Resolution	Plan
Desktop	1366 × 768	Free
Wide-screen	1920 × 1080	Paid
Mobile	375 × 812	Paid
Tablet	768 × 1024	Paid

Additional viewports (Wide-screen, Mobile, Tablet) require a paid plan.

---

Special Purpose Agents

Theme Tester Agent

The Theme Tester Agent runs explorations across multiple UI themes (e.g., Light and Dark mode) to catch visual regressions that only appear in specific themes.

Theme Change Strategy

Controls how the agent applies each theme before running the test. Choose the strategy that matches how your application handles themes:

• Custom Action (default) — The agent navigates within your app to change the theme (e.g., via a settings page). Optionally provide Theme Selection Instructions to guide the agent to the right location.

  Click the settings icon in the top-right corner, then select the theme from the dropdown.

• Cookie — The theme is set via a browser cookie before the test begins. Requires:

  • Cookie Name — e.g., theme
  • Cookie Domain — e.g., example.com

• Local Storage — The theme is set via localStorage before the test begins. Requires:

  • Local Storage Key — e.g., theme

Themes

The list of themes to test. Each theme will be applied in a separate test run. Enter theme names as tags (press Enter or use commas to add multiple).

Default: Light, Dark

Default Viewports

The viewport sizes used for theme testing. You can either:

• Configure viewports independently (same options as Bug Source Analytics)
• Enable "Sync with Screenshot Analytics viewports" to automatically use the same viewports configured in the Bug Source Analytics Agent

---

Localization Tester Agent

The Localization Tester Agent runs explorations across multiple locales to verify that your application renders correctly and completely in different languages and regions.

Locale Change Strategy

Controls how the agent applies each locale before running the test:

• Browser Locale (default) — The browser locale is set via Playwright before the test begins. Best for apps that rely on the browser's Accept-Language header.

• Custom Action — The agent navigates within your app to change the locale (e.g., via a profile or language settings page). Optionally provide Locale Change Instructions to guide the agent:

  Click the profile icon, select Language, then choose the locale from the dropdown.

• Cookie — The locale is set via a browser cookie before the test begins. Requires:

  • Cookie Name — e.g., locale
  • Cookie Domain — e.g., example.com

• Local Storage — The locale is set via localStorage before the test begins. Requires:

  • Local Storage Key — e.g., locale

Locales

The list of locales to test. Each locale will be applied in a separate test run. Select from standard locale options or type a custom locale tag (e.g., en-US, es-ES, fr-FR, ar-SA, he-IL).

Default Viewports

The viewport sizes used for localization testing. You can either:

• Configure viewports independently (same options as Bug Source Analytics)
• Enable "Sync with Screenshot Analytics viewports" to automatically use the same viewports configured in the Bug Source Analytics Agent

---

Best Practices

1. Provide test data: Give the Screen Discovery Agent login credentials and any other data it needs to explore authenticated parts of your app
2. Narrow API capture with regex: Use the API Regex filter in the Bug Source Analytics Agent to focus on your own APIs and reduce noise from third-party calls
3. Use Browser Locale when possible: For the Localization Tester, Browser Locale is the simplest strategy if your app respects the browser's language header
4. Sync viewports: Enable viewport sync on the Theme and Localization Tester agents to keep all agents consistent with your Bug Source Analytics viewport configuration
5. Provide navigation instructions for Custom Action strategies: When using Custom Action for theme or locale switching, clear step-by-step instructions help the agent reliably find the right settings in your UI