Troubleshooting installation

Here are some common situations in which you may find yourself disgruntled while installing Command AI and not seeing what you expect.

First confirm that you have actually installed Command AI, and aren't just using the extension to preview an experience. Using the extension only makes Command AI available to you on your local browser. Installing Command AI for real makes Command AI available to the application/site where you have installed it for all users.

Second,

• Check for a "launcher", an icon that usually appears in the bottom-right of the screen. Clicking it should open Copilot/HelpHub or Spotlight
• Try "cmd +k" to open Spotlight. If neither of these options work, it's time to dig in with more advanced steps below.

Why doesn’t any launcher show up?

Check your console for errors and warnings.

• If you see CORS errors, then make sure to add our CSP directives to your allowlist as detailed here.
• If you see a warning that you need to "boot" Command AI, then make sure that your code for window.CommandBar.boot() is being called. Command AI won't start until boot is called.
  • Once booted, cmd/ctrl+k should open Spotlight
    • If you've disabled spotlight: you can use window.CommandBar.openHelpHub() to open HelpHub instead
• Otherwise, if you see neither of the errors above, try entering window.CommandBar in your browser dev console:
  • If the result is undefined, then inspect the either the CB snippet or init() call

I added a nudge, but I don’t see it?

When designing nudges, you might want to experience them directly in your product. To do this, make sure you click Preview from the Studio or Extension. Doing this will ensure the experience shows up as it would for a user who meets all targeting criteria.