> For the complete documentation index, see [llms.txt](https://ce-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ce-docs.keywordrush.com/ai-agents/connect-chatgpt.md).

# Connect ChatGPT

Connect ChatGPT to your site with a ChatGPT project and Work mode — paste one block of text, start a chat, and put jobs on a schedule.

ChatGPT works on your site in **Work** mode: it reads your site's agent guide and calls the WordPress REST API with your application password, the same way Claude does. You keep the login in a ChatGPT **project**, so every Work chat in that project — and every task you schedule from it — can reach your site. There's no plugin to install and nothing to configure in ChatGPT's settings.

{% hint style="info" %}
**Used a Custom GPT before?** OpenAI is retiring Custom GPTs, so Content Egg no longer uses them. A GPT you already set up keeps working until OpenAI switches it off; move to the project setup below before then.
{% endhint %}

### Watch it in action

{% embed url="<https://www.youtube.com/watch?v=PMCbVqLptvw>" %}

The setup below, step by step — the application password, the ChatGPT project and a Work chat — then a first real job: a price-comparison product, its other sizes, and a weekly scheduled check.

**Before you start,** finish [**Turning on Agent Access**](https://ce-docs.keywordrush.com/ai-agents/turning-on-agent-access.md) so you have your WordPress **username** and an **application password**.

### 1. Create a project

In ChatGPT, open the sidebar and create a new **project**. Name it after your site. Leave the memory option on **Default memory**.

### 2. Paste your login into the project's sources

On your site, go to **Content Egg → AI Agents**, open the **ChatGPT** tab and copy the **Project source** text. It already holds your site address, your agent guide link and your username:

```
Content Egg site: https://YOUR-SITE.com/
Agent guide: https://YOUR-SITE.com/wp-json/content-egg/v1/agent-guide
WordPress username: USERNAME
Application password: your-application-password
Read the agent guide before working on the site.
```

<figure><img src="https://4254262503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M3fnB7iKYwDc1Xhr3H3%2Fuploads%2Fgit-blob-47d4fa692a7651da2f6ece491236783157cea5ba%2Fagents-chatgpt-tab.webp?alt=media" alt=""><figcaption><p>The ChatGPT tab on the AI Agents page</p></figcaption></figure>

In your ChatGPT project, open **Sources → Add sources → Paste text**, paste the text, and replace `your-application-password` with your application password. Save it.

{% hint style="warning" %}
The password is now stored in the project and available to every chat and scheduled task in it. That's why you should connect a **dedicated WordPress user** rather than your own admin account — see [**Where your password ends up**](https://ce-docs.keywordrush.com/ai-agents/safety-and-permissions.md#where-your-password-ends-up).
{% endhint %}

### 3. Start a Work chat and test it

Open the project, switch the toggle at the top from **Chat** to **Work**, and try:

> **Using Content Egg, show my active modules and search Amazon for wireless earbuds.**

ChatGPT reads the guide, logs in with the login from the project's sources, and comes back with your active modules and a few products. If it asks to allow internet access, allow it.

If that works, you're connected. See [**Example prompts & workflows**](https://ce-docs.keywordrush.com/ai-agents/prompts-and-workflows.md) for what to ask next.

{% hint style="success" %}
**Just trying it out?** You can skip the project: start a Work chat, paste your **agent guide** link (the **Agent guide** row on the ChatGPT tab) and your username and application password, and ask. The project only saves you from pasting them again in every chat.
{% endhint %}

### Run it on a schedule

ChatGPT can run a job for you on a schedule — daily, weekly, or at your own interval. That's how "an assistant that builds pages when I ask" becomes a publishing routine that runs without you.

Ask for it **in a Work chat inside your project**, describing the whole job and when to run it:

> **Every weekday at 9:00, follow the Content Egg agent guide for my site. Take the next topic from the list below that I haven't covered yet — search my existing posts first — write the article, add a relevant product from Content Egg to each section, set a featured image, and leave it as a draft.**
>
> * Burr Grinder vs. Blade Grinder: Which Is Better?
> * …

ChatGPT creates a scheduled task. It runs in the cloud, so your computer doesn't have to be on, and it reads the login from the project's sources like any chat in the project. Your tasks are listed under **Scheduled** in the sidebar, where you can edit them, pause them, or run one now to test it.

{% hint style="warning" %}
**Every run starts fresh, with no memory of the last one.** Left to itself it can write the same article twice — so give it a **topic queue** and tell it to check your existing posts before picking the next topic, as in the example above.
{% endhint %}

Two things to decide before you turn one loose:

* **Publish, or leave a draft?** Publishing every day is the point for a topic queue you've already approved. If you'd rather review first, end the job with "leave it as a draft" — or connect a WordPress user without publish rights, and it can't publish either way.
* **Keep the cadence sane.** Every run spends your affiliate networks' API quota, and ChatGPT limits how many scheduled tasks you can have and how often they run, depending on your plan. Nothing needs to run hourly.

{% hint style="info" %}
**Your off switch:** revoking the application password stops every chat and scheduled task using it, immediately.
{% endhint %}

### Using the ChatGPT desktop app

The desktop app works the same way, with one difference: its Work mode runs requests from your own computer, and it asks before each one by default. Choose **Work**, then set the permission menu under the message box to **Full access** so it doesn't stop to ask on every request.

{% hint style="warning" %}
**Full access** lets ChatGPT run commands and change files anywhere on your computer, not just reach your site. Use it in the chats where you work on your site.
{% endhint %}

A scheduled task that runs on your computer only runs while the desktop app is open. For jobs that should run whatever your computer is doing, create them in the browser — they run in the cloud.

### Prefer to keep the password out of ChatGPT? (advanced)

**Codex** — OpenAI's coding agent — can connect to your site over **MCP**, with your login kept in an environment variable on your computer instead of in a chat or project. See [**Connect any other assistant**](https://ce-docs.keywordrush.com/ai-agents/connect-other.md#codex).

### If something goes wrong

* **"I can't reach that site" / "Could not resolve host" / a DNS error**
  * In the browser: make sure the chat is in **Work** mode, not Chat, and that **Settings → Data controls → Work network access** is on.
  * In a project created with **Project-only memory**: those projects have no Work mode, so their chats can't reach your site. Create a new project with **Default memory**.
  * In the desktop app: set the permission menu under the message box to **Full access**. With **Ask for approval**, ChatGPT can read the agent guide and still fail on every action.
* **"Unauthorized" / 401** — use the **application password**, not your normal login password, check the username in the project's source text, and confirm Agent Access is switched on.
* **Requests blocked, 403 or timeouts** — a firewall or security plugin may be blocking ChatGPT. Its requests come from changing cloud addresses, so allow the paths rather than an IP: `/wp-json/content-egg/` and `/wp-json/wp-abilities/`. See [**If writes fail but reads work**](https://ce-docs.keywordrush.com/ai-agents/advanced.md#if-writes-fail-but-reads-work).
* **You changed the application password** — update the text in the project's sources. Run your scheduled tasks once to check they pick up the new one.
* **It can search but can't build or edit** — building and editing require **Content Egg Pro**.
