CodeBot Docs

CodeBot is a floating AI chat widget for WordPress — built for developer-facing sites that need smart, code-aware support without the clutter of a bloated helpdesk plugin.

The widget renders markdown, highlights code blocks, adds one-click copy buttons, and speaks developer. Drop it on any WordPress site in under 5 minutes.

Requirements #

Installation #

Quick Start #

After activation and license entry, the fastest path to a working widget:

1. Paste your API key

Go to CodeBot → Settings → API Configuration. Select your provider, then paste your key.

COPY# OpenAI key format
API Key: sk-proj-xxxxxxxxxxxxxxxxxxxxxxxx
# Anthropic key format
API Key: sk-ant-api03-xxxxxxxxxxxxxxxxxxxxxxxx

2. Choose a model

Select the AI model from the dropdown. gpt-4o-mini or claude-haiku-3-5 are the fastest and cheapest for most support use cases.

3. Save & preview

Click Save Settings, then visit any page on your site. The CodeBot widget will appear in the bottom-right corner. Click the >_ icon to open it.

License Activation #

CodeBot uses license keys to verify your plan and enforce site limits. Keys are issued by virtualsky.io via WooCommerce Software Add-on.

Activating a license

Deactivating / moving to another site

Go to CodeBot → License and click Deactivate. This frees up a slot so you can activate on a different domain. Deactivation requires a working internet connection.

License API endpoint

The plugin communicates with our licensing server at:

COPYhttps://virtualsky.io/?wc-api=software-api

Make sure your server can reach this URL outbound over HTTPS (port 443).

Admin Settings #

All settings are under WordPress Admin → CodeBot → Settings.

API Configuration

Widget Behavior

Appearance

AI Models #

CodeBot supports models from both OpenAI and Anthropic. You can switch models at any time without re-entering your API key.

System Prompt #

The system prompt shapes how CodeBot behaves — its persona, expertise, tone, and scope. This is the most powerful customization available. Available on Pro and Agency.

Accessing the prompt editor

CodeBot → Settings → System Prompt. Enter any instructions in the text area and save.

Example: Developer support bot

COPYYou are CodeBot, a senior developer support assistant for [Your Product].
## Your expertise
- [Your Product] API, SDK, and configuration
- WordPress plugin development
- REST APIs, webhooks, and authentication
- PHP, JavaScript, and common dev tooling
## Rules
- Always respond with working code examples where relevant
- Use markdown. Format code blocks with the correct language tag
- If you don't know, say so — do not guess
- Escalate billing questions: "Please email support@yourdomain.com"
- Keep responses concise and actionable

Tips for a great system prompt

Be specific — generic instructions produce generic responses. Name your product, describe your stack, and list what topics the bot should and shouldn’t answer.

Set a persona — give the bot a name and a voice. This reduces “I’m an AI” boilerplate and makes responses feel more intentional.

Define escalation — tell the bot when to hand off to a human, and how (email, support link, etc.).

Appearance #

CodeBot uses a dark terminal aesthetic by default. Accent color, title, and icon are configurable. Full CSS override is available on Pro+.

Changing the accent color

Set accent_color in the Appearance tab. This updates the widget border glow, send button, cursor blink, and link colors simultaneously via CSS custom property injection.

COPY/* The plugin injects this into the widget iframe */
:root {
--cb-accent: #00e5a0; /* your accent_color value */
}

Custom CSS (Pro+)

Any CSS added to the Custom CSS field is injected into the widget scope. Useful for overriding fonts, padding, or component-level styles.

COPY/* Example: change widget font to match your site */
.cb-widget {
font-family: 'Your Font', monospace;
}
.cb-header {
border-radius: 0; /* flat header */
}

Visibility Rules #

Control exactly where CodeBot appears — by page type, post ID, or user role.

Show on all pages

Default behavior. Widget renders on every front-end page.

Show on specific pages

In Settings → Visibility, switch to Specific Pages mode. Enter post IDs or page slugs, one per line:

COPY# Show only on docs and support pages
/docs/
/support/
42        # page ID
product   # page slug

Logged-in users only

Enable logged_in_only to hide the widget from guests. Useful if CodeBot is a paid feature for your customers.

Exclude pages

Switch to Exclude Pages mode to show everywhere except listed pages. Common use: exclude checkout, login, and WooCommerce account pages.

White Label #

Available on Agency. Remove all CodeBot branding and present the widget as your own product.

Plan Comparison #

All plans are one-time purchases. Buy on virtualsky.io →

Troubleshooting #

Widget not showing

Check that the plugin is Activated (not just installed) and that your license is active. If using visibility rules, verify the current page matches an allowed page/slug.

API errors / no response

Go to CodeBot → Settings and use the Test Connection button. Common causes:

• Invalid or expired API key — regenerate at your provider’s dashboard
• Insufficient API credits — top up your OpenAI or Anthropic account
• Server can’t reach the API — check firewall / outbound HTTPS rules

License activation fails

Verify your server can reach virtualsky.io outbound on port 443. Some managed hosts block outbound HTTP. Also confirm you haven’t exceeded your plan’s activation limit.

COPY# Test outbound connectivity from your server
curl -I https://virtualsky.io/?wc-api=software-api

Widget appears but doesn’t respond

Open browser devtools → Network tab. Send a message and look for a POST to /wp-admin/admin-ajax.php. If it returns a 403, a security plugin (like Wordfence) may be blocking the AJAX action. Add codebot_chat to your security plugin’s allowlist.

Styles broken / widget looks off

A theme or page builder may be injecting global CSS that bleeds into the widget. Enable the Widget Isolation Mode option in Settings → Appearance to scope all styles to the widget container.

FAQ #