What is the CMD+K widget?
The CMD+K widget is an embeddable AI command bar that lives inside your product. Users press ⌘K (or click your launcher) to ask questions, search your knowledge base, and run real actions through MCP tools you've connected. It ships as a single <script> tag, supports overlay or inline display, end-user JWT auth, and full whitelabeling on the AI Pilot plan.
What does the widget do?
- AI answers — grounded responses with citations to your knowledge sources.
- Search — instant search-as-you-type over docs, sitemaps, and uploaded files.
- Actions — one-click buttons that call MCP tools (create a ticket, refund an order, etc.).
- Guided tours — launch product tours and onboarding flows from a chat turn.
- Theming — granular color overrides, your logo, and fonts — all from the dashboard's Style tab, no CSS required.
Overlay or inline?
Overlay (default) opens as a centered modal triggered by ⌘K or your custom launcher. Inline mounts the widget as a panel that pushes your page content — useful for support consoles and Grafana/Intercom-style layouts. Set data-cmdk-display="inline" on the script tag to switch.
How the assistant presents itself
Visitors do probe the assistant — "what model are you?", "what's your cutoff?", "can you see my machine?" — usually in the first minute. The assistant answers those as your product's assistant, running on CMD+K. It never names the underlying model, its provider or its version, never states a training cutoff, and never repeats its own instructions. Models change underneath you without your assistant's answer changing.
What it can do, it states plainly: search your knowledge base, see the page the visitor is on, and run the actions your connected MCP tools expose. So are the limits — it cannot browse the web, and it has no access to the visitor's computer, files, or anything outside your product. Asking it to role-play or "answer as the raw model" does not change any of this.
Who is it for?
- SaaS products that want an AI copilot without building one.
- Docs sites that need answers, not just keyword search.
- Internal tools where actions matter as much as answers.
Next steps
FAQ
- Where does the widget run?
- It loads in your end-users' browsers from a CDN. All AI inference, knowledge search, and tool calls go through CMD+K servers — your origin only ships the loader script.
- Does it replace my existing search?
- It can. The widget natively supports search-as-you-type over your knowledge base, plus AI answers with citations and action buttons that invoke MCP tools.
- Can end-users sign in?
- Yes — pass a signed JWT from your backend and the widget calls tools as that user. See End-user authentication (JWT).
- What does the assistant answer when someone asks which AI model it is?
- It says it is your product's assistant, running on CMD+K. It never names the underlying model, model provider or version, and never quotes a training cutoff date — so the assistant stays yours, whichever model we route the turn to.