> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/workflows/ai-chat.md). # AI Chat Make requests, reference pages, attach images, read live progress, approve, undo and save chats as Playbooks. Open **WP AI Manager > AI Chat**. Describe what you want; the assistant reads the site through tools and shows every change. ## Start a conversation An empty chat shows **What should we work on?** with starter prompts. A starter that contains a blank (such as a page name) goes into the composer for you to finish, rather than being sent. Examples: * Create a new landing page called "…" for … Use my Brand Kit. Build it as a draft and show me before publishing. * Write the SEO title and meta description for this page, in my brand voice. * Update text across my site: replace "…" with "…". Show me every match before changing anything. * Put a product category on sale. Ask me which category and what percentage, and preview the change first. * Create a contact form with name, email, phone and message, and add it to my Contact page. ## The composer | Action | How | | --------------------------------- | ------------------------------------------------------------------ | | Reference a page, post or product | Type **@** and pick from the list | | Run a command or playbook | Type **/** for slash commands | | Attach images | **+** then **Upload from computer** or **Pick from Media Library** | | Choose the model | **Best quality** or **Faster, lower cost**, per message | | Stop a reply | The **X** button beside Send ("Cancel this reply") | | New chat | **New chat**, or Cmd+Shift+K / Ctrl+Shift+K | In the @ and / menus, arrow keys move, Enter or Tab picks and Esc closes. ## While it works Every wait shows a plain-language step label from the start ("Reading your request", then for example "Checked page structure. Planning the next step") and a timer for the whole turn. Tool calls collapse into **Used a tool** rows you can expand. The header shows the agent status and token use. ## Results, approvals and undo * **Result cards** show what a tool did, with preview and edit links. A draft preview uses WordPress's own preview link. * **Approval needed** cards pause broad or risky writes. See [Approvals, Undo and History](/documentation/work-safely/approvals-undo-and-history.md). * **Undo** on a result, or **Undo last change**, reverses a recorded write. * **Requirement** cards name a missing plugin, setting or license, with the button to fix it. * **Allow X in this chat** cards appear when a needed tool is switched off. See [Tools and permissions](/documentation/reference-and-help/tools-and-permissions.md). * A **Task run** card appears when the request starts an agent Task. Use **Open run details** to review proposals in Tasks. * **Remember this?** proposes a memory. **Remember it** sends it to Site Knowledge for approval; **No thanks** dismisses it. Whole-page builds and redesigns go through the **Draft Sandbox**: a copy of the page is edited and you **Review and publish**. A large page may ask you to **Back up and continue** first. ## Content journey For a blog post, Chat shows progress cards in one thread: **Content brief** (with **Regenerate**), **Write the draft** (saved as a private draft post), then SEO title options, meta description, Open Graph fields and keyword placement checks, with **Save to the page** through the active SEO plugin. **Suggested gaps to cover** are suggestions, not competitor data. ## Conversations * Conversations save automatically and appear in the sidebar. **Search conversations** filters them. * The **Conversation actions** menu on each chat lets you rename or delete it. * The address bar carries the conversation ID, so a reload or bookmark returns to it. * Two tabs on the same conversation take turns; the second waits rather than mixing replies. * Rate a conversation with the thumbs up or down once there is a reply. ## Save as playbook **Save as playbook** turns the current conversation into a private reusable Playbook. Give it a name. If you make it recurring, it also creates an automation; open **Playbooks > Tasks and runs** to choose how often it runs. Recurring runs default to preview, so they never change the site without review. ## If Chat cannot do something * **No AI provider connected**: use **Open Connectors**. * **Activate your license** / **Your license expired**: use the button on the card. * A turn that stops at its step limit: say "continue", or split the job into smaller requests. See [Troubleshooting](/documentation/reference-and-help/troubleshooting.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.3techagency.com/documentation/workflows/ai-chat.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.