Skip to content
Aymar Agents

On-screen assistant SDK

Diagnostics

View as Markdown

If the copilot doesn’t arm itself when you expected it to, check in this order:

  1. The widget’s boot response: it always carries a copilot block with enabled, mode, manifestStatus, needManifest and, if applicable, reason. It’s the source of truth — never guess from what’s on screen.
  2. Is the copilot turned on for that channel instance (the Platform → Channels → Copilot)?
  3. Does the fingerprint match? Compare it in the channel’s “Copilot” section against what your SDK is computing locally.
  4. Does your allowedWidgetOrigins really include the origin your widget loads from?
  5. The conversation’s timeline (inbox): every plan proposed, delivered, completed, cancelled or failed gets logged there — useful for seeing what happened with a specific plan without access to the server’s technical logs.