This guide explains how to start a fresh ChatGPT Work session that can connect to an open Etch Builder instance using the Etch Connector.
Once connected, ChatGPT Work can create sections, build layouts, edit components, and make changes directly inside Etch.
Note: These instructions assume you are using the ChatGPT Desktop App with Work enabled.
The Etch Connector supports two different communication methods (called backends) that allow an AI agent to interact with your website.
Bridge is the default and recommended backend for most Etch development.
Instead of clicking buttons inside your browser, the AI communicates directly with Etch through the Etch Connector.
Benefits of Bridge:
Bridge is ideal for tasks such as:
CDP stands for Chrome DevTools Protocol.
Rather than communicating directly with Etch, CDP allows the AI to control your browser much like a person would by clicking buttons, typing into fields, opening menus, navigating pages and inspecting browser content.
CDP is useful when the AI needs to perform tasks outside of Etch.
Examples include:
Recommendation: Unless you specifically need browser automation, use Bridge. It is the recommended backend for most Etch workflows.
Open the ChatGPT Desktop App.
Do not use ChatGPT in your web browser, as the desktop application provides the local computer integration required for the Etch Connector.
If Work is unavailable, ensure you are running the latest version of the ChatGPT Desktop App and that your account has access to Work.
Before continuing, verify that the Work conversation is able to run commands on your computer.
You should see something similar to:
Runs on your computer
If local computer access is unavailable, resolve that issue before proceeding.
Copy and paste the following prompt into your new Work conversation.
I'd like your help working in Etch.
Read the Etch Connector documentation:
https://docs.etchwp.com/etch-connector/usage
https://docs.etchwp.com/etch-connector/ai-agent-guide
Please start the Etch Connector for me, connect to my open Etch Builder instance, and use the recommended Bridge backend unless I specifically request CDP.
Once connected, verify the connection before making any changes.
Do not make changes to my page until I ask.
When you're ready, tell me you're connected and waiting for instructions.
The first time ChatGPT Work connects, it may request permission to:
Approve these requests when prompted.
Open your website in the Etch Builder.
If prompted:
Once connected, Etch should display something similar to:
External AI Agent Connected
Ask ChatGPT Work to make a simple test change.
Create a new Section.
Inside it add an H2.
The heading should read:
Hello from AI
Do not make any other changes.
If the section appears inside Etch, congratulations! Your AI agent is successfully connected and ready to use.
This workflow allows regular ChatGPT to handle the thinking and planning while ChatGPT Work focuses on executing the changes.
To save time, create a reusable prompt that teaches ChatGPT Work about your preferred workflow.
For example:
Doing this means every new Work session already understands how you prefer to build websites.
Keep one dedicated Etch Work conversation pinned in ChatGPT.
Once connected and familiar with your workflow, you can continue using the same Work conversation instead of creating a new one every time you work in Etch.
During my testing, this approach appeared to use significantly fewer Work resources than repeatedly creating new Work sessions and reconnecting to Etch. It also performed well using the GPT-5.6 Luna Light model.
Note: This reflects my experience at the time of writing (September 19, 2026). ChatGPT models, Work capabilities and resource usage may change over time, so your experience may differ in the future.