Skip to content

Assistant

View as Markdown
Open in ChatGPT (opens in a new tab) Open in Claude (opens in a new tab) Open in Perplexity (opens in a new tab) Open in Grok (opens in a new tab) Open in Copilot (opens in a new tab) Open in Le Chat (opens in a new tab)

SleekView has no AI chat or AI settings of its own any more. The workspace assistant takes their place: open it with the assistant button in the workspace header, in the suite and in the standalone plugin alike.

Working on a View

While a View is open in its editor, the assistant can work on it directly:

  • read the View as it stands, including your unsaved changes and the selected layout;
  • change the View’s settings – its data source, post type, conditions and whether it is disabled – or one layout’s name, type, data filters, settings and conditions;
  • replace the whole View with a new configuration, keeping its ID;
  • select a layout, so the preview shows it.

Everything it changes goes into the editor’s unsaved draft, so the preview and the inspector show the result straight away and you can review it. It saves or discards the draft only when you ask it to. Without an open View editor it asks you to open one.

Ask in terms of your content: “Add a Kanban layout for the projects post type, with a column for each Status term”, or “Hide the author column in the table”.

Running commands

The assistant can also run SleekView’s WP-CLI commands: list Views and admin pages and show their configuration, delete one, and read and change the settings. Before deleting it shows what will happen and waits for your approval. Admin pages are reached only this way; the assistant has no editor tools for them.

Provider keys

The assistant needs a key for at least one AI provider. Keys belong to the whole site and every SleekWP product shares them:

  • In the suite, open the global settings with the Settings button beside the theme selector in the sidebar header, and choose the AI section.
  • In the standalone plugin, open View’s Settings screen, which holds the same AI section.

The section has one field each for OpenAI, Anthropic, Google and OpenRouter. A saved key is stored encrypted and never shown again; it appears masked with a Remove action. Requests go from your site to the provider, which bills you directly.

Keys saved in the AI settings of SleekView 1.x move to the AI section once, for each provider that has no key there yet; a key already there is kept. Without any key the assistant’s message field stays disabled, and earlier conversations stay readable.

Each provider issues keys in its own console:

Stay in the Loop!  

Be the first to hear about new updates, special offers, and helpful tips, delivered straight to your inbox.

We respect your inbox (and your privacy). Read our privacy policy.