OpenStation
wp-admin forgets. OpenStation doesn’t. You know the moment. You’re deep in a post and you need one image from the Media Library. You click over, find it, click back, and everything you had going is gone. Your scroll position, your half-typed thought, the three other things you had queued up in your head. That’s not a bug you hit. That’s the design. wp-admin shows you one screen at a time, and every navigation throws the last one away. It has worked this way since 2003, like a fridge that empties itself every time you close the door. WordPress has rebuilt almost everything else. The editor, the site editor, the patterns, the styles. The admin’s one-screen-at-a-time model is the layer nobody touched. OpenStation touches it. Install it and admin screens become draggable, resizable windows. Edit a post while the Media Library sits open next to it. Drag an image from one window straight into the other. Keep comments open in the corner. Reload the browser and your window layout — open pages, positions, sizes, and window states — comes back where you left it. OpenStation itself is free, GPL, and opt-in per user. One click in the admin bar turns it on for you. One click turns it off. Nobody else on your site sees anything change, and deactivating the plugin restores the classic admin exactly. No Core patches and no lock-in. Optional AI providers may charge for their service. Built and maintained by Automattic, the company behind WordPress.com, Jetpack, WooCommerce, and Tumblr. Work on more than one thing at once Admin pages open as windows, including pages added by most other plugins. Drag them, resize them, snap them, tile them, minimize them to a taskbar. The admin menu becomes a dock of icons. Two editors open at once is one click away. Never lose your place Moving between open windows leaves each page in place. Across reloads, OpenStation remembers your open pages, window positions, sizes and states, virtual desktops, and focus. Closing a window with unsaved changes warns you first. A desk you can actually put things on Drop posts, media, and links right onto the wallpaper. Sort them into folders. Trash them to a Trash that actually holds things. The stuff you’re working on this week can just sit out where you can see it. One desktop per job Virtual desktops, the way your operating system does them. One for writing. One for the store. One for comment triage. One for that redesign you keep poking at. Switch between them without closing anything. Find anything with Cmd+K The full WordPress command palette, plus slash commands from your plugins, all under one keystroke. Turn on the optional AI assistant and you can ask it things like “which post had the comment asking for the recipe?” and it searches your own content to answer. (Requires an AI provider configured in Settings → Connectors on WordPress 7.0+. Details under “External services” below.) See how your site fits together The Corkboard is an interactive, zoomable map of how your posts, pages, and products link to each other. Pan around it. Find the orphans. Find the hubs. Running a store? Orders, Products, Coupons, and Customers become browsable folders with stock and sale ribbons. Open a customer to see their lifetime spend and what they buy most. Follow a product to its buyers, or a coupon to who redeemed it. Make it yours Wallpapers, from color presets to animated scenes to your own photo. Live widgets pinned to the desktop: drafts, stats, recent comments, a focus timer. Uploadable desktop themes, including a built-in Legacy theme that brings the old WordPress blue back in one click. And Mio, a soft-body desk companion that drifts across your wallpaper and gets bumped around by your windows. Off by default. You’ll turn it on. For developers Extend OpenStation through documented PHP and JavaScript APIs. Register windows, icons, wallpapers, widgets, commands, and settings tabs through stable openstation_register_* PHP APIs and a typed JavaScript API; customize dock items through documented hooks; add AI tools with the WordPress Abilities API. Copy-paste examples live in the developer docs on GitHub. External services No external service is required for OpenStation’s desktop interface. The optional AI Assistant and two user-initiated enrichment features make the external requests described below. AI Assistant The optional AI Assistant sends data to the AI provider you configure in WordPress’s Settings → Connectors (for example OpenAI, Anthropic, or Google). Generation is routed through WordPress 7.0’s built-in AI Client, which supplies the credentials stored in Connectors. The plugin never handles an API key itself. With no provider configured in Connectors, no external AI requests are made. When the AI Assistant is enabled and a user invokes it (via Cmd+K or the slash-command palette): What is sent: the user’s prompt, the conversation history for the active session, and tool-call metadata. The plugin’s built-in tools (search_posts, search_pages, search_comments) run WordPress’s native keyword search and may include excerpts of the matching posts/pages/comments in tool results, which are then sent back to the provider as part of the agentic loop. When it is sent: on user-initiated AI requests, and (if an administrator enables “Score new comments with AI”) on comment-save hooks for spam analysis. Posts, pages, and taxonomy terms are not sent automatically. Why it is sent: to obtain model completions and tool-call decisions that drive the AI Assistant. Who provides the service: whichever provider you configured in Settings → Connectors. Which provider (and endpoint) receives the data depends entirely on that configuration. Review the chosen provider’s own terms and privacy policy (e.g. OpenAI, Anthropic, or Google). URL shortcut favicons When an authorized user creates a desktop shortcut to an external URL, OpenStation asks that URL for its page HTML and favicon so the shortcut can display the site’s icon. The request is made from your WordPress server and sends the requested URL, the server’s IP address, an OpenStation user-agent string, and normal HTTP request metadata to the operator of that site. This happens only when a user creates the shortcut. The destination site’s terms and privacy policy apply. WordPress.org plugin information When an authorized user opens or refreshes parts of OpenStation’s Plugins window, OpenStation may request public plugin details, update metadata, and review excerpts from WordPress.org. These requests send plugin slugs, the site’s locale, and normal HTTP request metadata to WordPress.org. This information is used only to display and manage plugins. Review the WordPress.org Privacy Policy. OpenStation’s OAuth relay does not contact a service by itself. Third-party plugins that configure the relay may contact their own providers and are responsible for disclosing those services. Credits OpenStation is brought to you by Automattic. The plugin is open source under GPLv2-or-later; contributions are welcome on GitHub. Third-party libraries The plugin bundles the following third-party JavaScript library, loaded on demand only when a feature that needs it is in use: PixiJS (MIT License) — used by the Corkboard window, built-in canvas wallpapers (e.g. the animated WordPress logo), the Mio desk companion, and the Inkfall typing game. PixiJS is loaded from the plugin’s own assets/vendor/ directory; no CDN requests are made. Data files The Inkfall game’s word list (assets/games/inkfall/words.txt) is generated from the following sources (attribution also ships in the file’s header): FrequencyWords by Hermit Dave (CC-BY-SA 4.0) — English word-frequency ranking derived from the OpenSubtitles corpus. english-words by dwyl (Unlicense) — used as a validity filter. LDNOOBW English list (CC-BY 4.0) — used as an exclusion filter.
Top keywords
- wordpress15×1.17%
- ai14×1.10%
- openstation13×1.02%
- open9×0.70%
- pages8×0.63%
- provider7×0.55%
- site7×0.55%
- window7×0.55%
- admin6×0.47%
- ai assistant6×0.47%
- assistant6×0.47%
- click6×0.47%
Recomaze – AI Chat Agent, AEO & GEO
Recomaze does two things for a WordPress site, and they feed each other. An AI chat agent on the site. A conversational agent that answers visitor questions from your own catalog, policies and knowledge base – not generic AI answers – recommends the right product, and carries the visitor toward checkout. AEO and GEO. AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) are two names for the same discipline: getting a site retrieved, understood and cited by AI assistants when they generate an answer. Recomaze tracks whether AI actually mentions you, fixes the reasons it does not, and publishes the content and machine-readable signals that make you quotable. The loop between them is the point. The chat agent sees every question your visitors ask, including the ones it could not answer. Those failures become a work list for the AEO side – and content published for AEO comes back as knowledge the agent can answer from. Traditional SEO competes for a position on a page of links. AEO competes to be inside the generated answer. A page can rank well in Google and never be quoted by an AI assistant, usually because nothing on it can be parsed into a clear, checkable claim. The AI chat agent Answers from your own content – the agent replies from your catalog, knowledge base and policies, in your brand voice, instead of improvising. Recommends products in conversation – it surfaces the right item as part of the answer and links the visitor to it. Your styling – colors, placement, wording and the launcher are yours to set, so the agent looks like part of the site. Preview mode – turn the agent on for administrators only and try it on the live site before any visitor sees it. Conversation analytics – conversations, visitor journeys, KPIs and insights, so you can read what people actually ask. Campaigns – run targeted on-site campaigns through the agent. Gaps: what the agent could not answer Every conversation the agent handles badly is recorded as a gap and sorted into four buckets: information missing, feature or product missing, cannot guide, and out of scope. A gap is not a report you read and forget – each one carries a fix, and the fix is a button: Missing information becomes a knowledge base article the agent can answer from next time. A losing topic becomes an AI Visibility article drafted on that exact question. A vague product becomes a product rewrite in the Content Generator, focused on the attributes the visitor asked about. A policy question becomes a policy update in your knowledge base. You can mark a gap resolved or dismiss it. The list is filtered by period, so you can see whether last month’s holes actually got closed. AI Visibility Visibility scans – ask the buying questions that matter in your niche and record which brands the AI names in the answer. Tracked prompts – keep a set of questions under continuous tracking and watch each one trend over time. Competitor tracking – see which brands take the mentions you do not, add competitors deliberately, and exclude ones that are not really rivals. Cited sources – see which pages an AI actually pulled from when it answered. Mentioned vs cited – being named and being used as a source are different results, and they are reported separately. Funnel coverage – see which stage of the buying journey your content covers and where it stops. Scan history and wins/losses – what moved since the last scan, in both directions. Trending in your chat – questions rising in your own visitor conversations, promoted into tracked prompts. Content that answers the question Content Generator – draft articles against the questions you are losing, then publish them straight into WordPress posts. Page templates – reusable structures for the page types that earn answers, run across topics. Content Checker – check a draft against what answer engines can actually extract from it, and apply the fixes. Optimized text pages and product content – rewrite titles, descriptions and Q&A so an AI can lift a fact instead of guessing at marketing copy. Prompt templates – reusable generation prompts, so output stays consistent with how you write. Scheduling and images – schedule a publish, and get image suggestions with the draft. Multi-language – generate the same content in several languages. Catalog and context Catalog Quality – scan products, score how AI-ready each one is, and fix them individually or in bulk. Import – bulk upload products and content. Knowledge Base – the source of truth the agent answers from: policies, shipping, returns, anything a visitor asks. AI Company ID – what you sell, who you sell to and how you talk, built once and pushed to everything the agent and the content generator produce. Connectors and integrations – connect the site so Recomaze can publish back to it, and plug into the rest of your stack. Agentic Commerce Feed – publish a machine-readable product feed for AI shopping agents. llms.txt – served automatically at /llms.txt and /llm.txt, the emerging convention for telling AI crawlers what a site is and what it offers. No file to write by hand. AI crawler log – every fetch of your llms.txt is recorded, so you can see which AI crawlers came, how often, and when they started. Answer schema – Article and FAQPage JSON-LD published in the page head, so an answer engine can lift a question and its answer directly. If Yoast or Rank Math already emits the Article, Recomaze steps aside and publishes only the FAQ, so the page never carries two. SEO fields filled in for you – articles published by Recomaze arrive with the focus keyphrase, SEO title and meta description already written into Yoast SEO’s and Rank Math’s own fields. AI copilot in the admin – ask it to do the work and it runs the steps for you. Dashboard – one AI-readiness score, the setup steps still open, and the latest articles, gaps and insights. Where your site can appear Recomaze prepares content for the assistants people actually ask, including ChatGPT, Claude, Perplexity, Google Gemini, Google AI Overviews and Microsoft Copilot. These are independent services; Recomaze is not affiliated with or endorsed by any of them, and no plugin can guarantee a mention in a generated answer. What Recomaze does is remove the reasons a site gets skipped: thin content, no machine-readable summary, no structured answers, nothing published against the question being asked. How it works Install, activate, and connect the site to Recomaze from the WordPress admin. Recomaze reads your site and builds your AI Company ID: what you offer, who for, in what voice. It scans AI assistants for the questions in your niche and reports where you stand against your competitors. It fixes what it can – content, product text, knowledge base, llms.txt, schema – and drafts what is missing. The chat agent goes live, and every question it cannot answer comes back as a gap with a fix attached. WooCommerce optional Recomaze runs on any WordPress site. A content site that wants the chat agent and the AEO work installs it and never touches a product. When WooCommerce is active, the catalog features switch on as well: product scanning and scoring, bulk product rewrites, product recommendations in chat, the product feed and order tracking. External Services This plugin connects to the following external services: Recomaze API Domain(s): https://api.recomaze.ai https://stagingapi.recomaze.ai (for testing and staging environments) Purpose: The API is used to retrieve user-specific product recommendations, update user preferences, and refresh authentication tokens. Data Sent: Plugin token (used for authentication) Store domain (to identify the WooCommerce store) Interaction events such as user preferences or clicks Product details from orders, including: Product names Product characteristics (e.g., categories, attributes) Product prices Terms of Use: https://recomaze.ai/tos/ Privacy Policy: https://recomaze.ai/privacy-policy/ Recomaze Tracking UI Domain(s): https://trackui.recomaze.ai https://stagingtrackui.recomaze.ai (for testing and staging environments) Purpose: The tracking service is used to display UI components such as recommendation popups and gather anonymous usage metrics to optimize recommendations. Data Sent: Client ID associated with the WooCommerce store. Recomaze Admin Service Domain(s): https://admin.recomaze.ai Purpose: This service is used to send logs for monitoring and debugging purposes. Data Sent: Plugin events and API interaction logs. Recomaze Collector Service Domain(s): https://collector.recomaze.ai Purpose: The collector service is used to retrieve reports for analytics and recommendations. Data Received: Analytics reports and performance insights.