WP Cortex v0.14.0

Added

• Admin chat: the assistant can now work with any block in the block editor, not only text. On request it inserts a block the editor allows in the post, including the site's custom and ACF blocks, or a registered block pattern (for example "insert the hero" or "add a hero with the title ..."), moves a block before, after or inside another block, and duplicates blocks. The new list_block_types tool lets it find blocks and patterns by name; edit_content got the operations insert_block, insert_pattern, move, duplicate and set_fields. A pattern's headings and paragraphs and the simple fields of an ACF block (text, textarea, WYSIWYG, number, email, URL, select, radio, true/false, range) can be filled as the block is inserted, and those fields changed later; repeaters, images and other complex fields are left for you to fill. The assistant also sees the field values of ACF blocks and the main attributes of other blocks (for example an image's URL). As before, everything is applied in the editor only and nothing is saved until you save the post. list_block_types can be switched off under Settings > Chat tools.
• Admin chat: more of the post's settings can be changed from the chat while the post is open in the block editor. edit_post now also sets the template, the parent page and order (page-like post types), the author and the featured image (an image already in the Media Library, found by its title or file name; when several match the assistant asks which one). As before, the change is made in the editor only and you save the post.
• Admin chat create_terms tool: the assistant can create tags, categories and terms of other taxonomies that do not exist yet, optionally under a parent category. Because this writes to the site, it shows an action card first and creates the terms only after you confirm it; they are then added to the post in the editor. It can be switched off under Settings > Chat tools.
• Visitor chat setting Conversation memory (public_chat_history, Settings > Visitor chat): how many previous messages of the conversation the assistant sees when it answers, from 2 to 100. The default is 50, up from the fixed 12 until now, so the assistant no longer loses the start of a longer conversation; the total text sent stays capped, so a longer memory cannot be abused to run up provider costs.
• Admin chat tools that save the post open in the block editor, on request: save_post (Save draft / Update), publish_post (publish now, or schedule for a date), set_post_status (switch to draft or pending review) and preview_post (a preview link in the chat). The post is saved by the editor itself, as if you clicked its button. A draft is saved right away; updating a published post, publishing, scheduling and taking a published post offline run only after you confirm the action card in the chat. "Change the title and save" works in one message. The assistant never saves on its own, only saves the post that is open in the editor, and cannot trash or delete posts. Each tool can be switched off under Settings > Chat tools.
• Admin chat reload_page tool: asking the assistant to reload or refresh the page reloads the page you are on, with the chat kept open. It does not reload while the page has unsaved changes (the post in the block editor, or ACF fields); the assistant asks you to save them first.

Changed

• Admin chat: the assistant can take up to 15 steps (tool calls) per message, up from 7, so longer requests in the editor fit in one message.

Fixed

• Chat: a request that needs more steps than allowed no longer ends with "The assistant needed too many steps to answer" and the loss of everything done so far. The assistant now uses its last step to say what it did, what is left and what it could not do, and the changes it already made are kept.