Documentation

Everything you need to install, configure, and operate Conductor. From first session to team deployment.

Getting Started

Installation

Clone the Conductor repository and follow the quick-start guide. The extension installs as an unpacked Chrome extension, giving you full control over the source and deployment timing.

First Session

Open the side panel with Cmd/Ctrl+Shift+S. Pick a model provider, set your session goal, and let Conductor build the initial prompt with page context and available skills.

Provider Keys

Configure your API keys in the settings panel. All keys are stored locally in IndexedDB—Conductor never sends them to a backend or logs them in transcripts.

Core Concepts

Sessions

Each conversation lives in a session. Sessions include the full transcript, captured artifacts, and metadata about which skills were active. You can export, share, or archive sessions at any time.

Skills

Skills are composable capabilities you enable per session—page reading, DOM manipulation, network capture, screenshot analysis. Each skill exposes a set of tools the agent can call.

Bridge Context

The bridge runs in an isolated world script, giving Conductor deterministic control over the page. Clicks, form fills, waits, and extractions stay reversible and auditable.

Artifacts

Ask the assistant to snapshot findings, code snippets, or data extracts. Artifacts live inside the session and can be copied, downloaded, or referenced in follow-up prompts.

Workflow

Streaming Transcripts

Replies stream token-by-token with tool deltas visible inline. You see the agent's reasoning, the tool it's about to call, and its arguments before execution happens.

Intervention

Pause streaming at any point to correct the agent, add context, or abort a tool call. The session stays consistent, and you can resume from the last safe state.

Session Locking

The background worker coordinates locks across windows. If you have Conductor open in multiple tabs, only one session can run at a time, preventing conflicting page edits.

Best Practices

Set Clear Goals

Start each session with a specific objective. The more focused your goal, the better Conductor can filter skills and surface relevant context from the page.

Review Tool Calls

Don't skip the transcript. Each tool call is logged with arguments and results. Reviewing the log after a session helps you catch edge cases and refine your prompts.

Export Sessions

Archive high-value sessions for compliance, team review, or training data. Exported sessions include the full transcript, artifacts, and skill configuration.

Keep Keys Local

Never commit your provider keys to a repo or share session exports that include sensitive data. Conductor's local-first design puts you in control of the secrets.

Need more detail?

Check the Architecture guide for system design or the Tools Reference for a complete list of available page tools and their arguments.