Skip to main content
Every page in the dashboard has a floating Support button in the bottom corner. Tapping it opens an AI support agent that knows the platform, your workspace, and the public docs. It’s the fastest way to get an answer, file a bug, or kick off a feature request without leaving the dashboard. The support agent is a dedicated Claude agent that’s separate from the agents you build — it has read access to your workspace shape (which agents you have, what plan you’re on, recent errors), the support docs corpus, and a small set of action tools for filing bug reports and feature requests on your behalf.

​
What it can do

  • Answer questions about the platform — pricing, plan limits, API behavior, what a tool does, how a feature works. It pulls live answers from the docs you’re reading right now.
  • Diagnose workspace problems — “Why did my schedule fail last night?”, “Why is this agent burning AI credits?” — it can look at your agents, sessions, schedules, and recent escalations.
  • File a bug report — when something is broken, hit File a bug. The widget collects a description, captures the page you’re on, and writes a bug_reports row that goes straight into our triage queue.
  • File a feature request — under-served use case? Hit Request a feature. Same pattern — the widget structures the request and routes it to product.
  • Open a support session — for longer conversations, the widget keeps a session history so you can come back to a thread later. Sessions are listed on the home view inside the widget.

​
What it can’t do

The support agent is intentionally read-only on most of your workspace. It can answer questions about your agents but it can’t deploy them, change schedules, mint API keys, or charge cards on your behalf. Anything that mutates workspace state still goes through the dashboard UI or the Builder.

​
Where it lives

The widget is mounted in the dashboard layout, so it’s available on every authenticated page. The home view (the first thing you see when you open the widget) shows three primary actions and a list of any in-progress sessions:
  • Ask a question — opens a fresh support chat.
  • File a bug — structured bug report intent.
  • Request a feature — structured feature request intent.

​
How it’s stored

Behind the scenes the widget creates rows in support_sessions, support_messages, bug_reports, and feature_requests. Each row is workspace-scoped and gated by RLS — only your workspace members can read what you submitted.

​
Help button

If you used to hit a separate Help button in the sidebar, it’s been rewired to open the same support widget. There’s only one in-product support surface.

​
Next steps

Health status

When something looks broken, check the status page first.

The Builder

For building agents, not for diagnosing the platform.