I’m doing well, thanks for asking! I’m the assistant for cacbot.com, so I can help with questions about the Cacbot WordPress plugin, such as creating conversations, configuring settings, or troubleshooting replies. What would you like to know?
How does Cacbot work?
What are hidden post meta data?
Hidden post meta is custom field data attached to a WordPress post whose key begins with an underscore, such as _cacbot_conversation. WordPress does not show these keys in the default Custom Fields box in the editor, so they are usually used by plugins and themes to store internal settings or state.
On a Cacbot site, the plugin uses hidden meta to control how a conversation behaves. Examples:
– _cacbot_conversation: set to exactly 1 on a regular post to make it a conversation (every cacbot-conversation post is recognized without it).
– _cacbot_system_instructions: plain-text instructions sent along with the conversation.
– _cacbot_default_response: a fixed reply posted immediately instead of a generated one.
– _cacbot_suppress_llm_response: when set to 1, stops new comments from being queued for generation.
– _cacbot_max_replies: closes comments once the approved comment count reaches the limit.
– _cacbot_comment_form_placeholder_text: changes the placeholder text of the comment box.
The plugin also maintains _cacbot_interlocutor_user_id and _cacbot_respondent_user_id itself to record the participants.
Site administrators or trusted code can manage the writable ones, and Cacbot’s metadata REST route only accepts an allowlist of keys. Let me know if you’d like details on any specific key.
How many of them are there?
WordPress itself has no fixed number of hidden meta keys. Any plugin or theme can add its own keys starting with an underscore, so the count depends on which plugins are active and what they store.
For Cacbot, these are the behavior-affecting keys I know of:
– _cacbot_conversation
– _cacbot_system_instructions
– _cacbot_default_response
– _cacbot_suppress_llm_response
– _cacbot_max_replies
– _cacbot_comment_form_placeholder_text
The plugin also maintains two participant keys itself: _cacbot_interlocutor_user_id and _cacbot_respondent_user_id. That makes eight in total.
Cacbot also recognizes some compatibility keys for companion services, such as _cacbot_model, _cacbot_reply_strategy, _cacbot_max_archives and a few _cacbot_action_enabled_* keys. Their presence does not mean the matching features are available. Anchor Posts, if active, adds its own keys like _cacbot_anchor_post and _cacbot_linked_to.
I can’t give you an exact total beyond this, since the compatibility keys and companion plugins vary by installation.
What is Cacbot?
Cacbot stands for “Comments Are a ChatBOT.” It is a WordPress plugin that turns a post’s comments into a conversation with an AI assistant. Your messages and the assistant’s replies are stored as ordinary WordPress comments, so the site’s usual post, comment, moderation and privacy controls apply to them.
Here is how it works in brief:
– When a logged-in user posts an approved comment on a conversation, the plugin queues a background job (WP-Cron).
– The job asks a remote AI-processing service to write a reply.
– The reply is posted back as a threaded comment.
Site owners can set global and per-conversation system instructions, a fixed default response, and a limit on how many comments a conversation may hold.
If you have questions about how it works or how to set it up, just ask.
Hello
Hello! I’m the assistant for cacbot.com. I can help with questions about the Cacbot WordPress plugin, such as creating conversations, configuring settings, or troubleshooting replies. What would you like to know?
Hello. How are you today?
Hello! I’m doing well, thanks for asking. I’m the website assistant for cacbot.com. How can I help you with Cacbot today?
What is Cacbot?
Cacbot is a WordPress plugin that turns comments into conversations with a remote AI-processing service. Human comments on eligible posts are sent for processing, and the generated replies are stored as ordinary threaded WordPress comments, so site owners can use WordPress’s existing post, comment, and moderation tools.
The name stands for “Comments Are a ChatBOT.” It can also be used on a dedicated conversation post type, and it can be set to return a fixed default reply instead of generating one remotely.
If you want to know how to set up a conversation or configure the plugin, I can walk you through that.
Do I need an API key?
No, the Cacbot plugin itself does not read an OpenAI API key or any other model-provider key. It sends each conversation to the remote Cacbot service (by default https://cacbot.com, or the mothership URL set under Settings → CACBot). That service handles the AI processing and returns the replies, which are then stored as WordPress comments.
To connect a site, the plugin uses an application password exchanged with the mothership, so an administrator needs to complete the connection under Settings → CACBot. Which AI provider and models the remote service uses, and whether it needs its own key, depends on that service’s deployment, and I can’t confirm those details from here. If you are running your own mothership, check its documentation for provider credentials.
If the connection shows as incomplete, reconnect from Settings → CACBot and confirm the mothership URL is reachable over HTTPS.