About this block

Assistant Empty State is the panel the user sees before sending a first message. A centered Acme mark sits above the heading and a short prompt, then four example chips drawn from real product tasks: Which customers renewed in Q2 with an open ticket, Summarise the changes in Apollo since the last deploy, List team members who have not logged in this month, and What does ACM-9041 block and who owns it. Below that a two-column panel shows what the assistant can see, projects, tickets, directory, and activity log, and what it cannot do yet under a Roadmap badge, write to production, access billing, or send on your behalf.

examplePrompts, canSee, and cannotDo are three const arrays. Showing both lists in the same view is what sets accurate expectations before the first message, not after the first refusal.

When to use

Reach for this block as the initial state of the assistant view before any thread exists. Replace it with the assistant chat panel once the user submits a first message.

A natural flow around it on an Application Pro page:

Before

• App shell

After

• Prompt composer
• Assistant chat panel

What you can display

One strong use is the AI assistant zero-state onboarding panel. Other empty-state shapes:

• Role-scoped prompts. Different example chips shown to admins vs members based on their access level.
• Recent threads. Replace the example chips with the last three conversations when a returning user has history.
• Feature gate. A single upgrade call to action when the workspace plan does not include AI.

Tip: example prompts should be tasks the signed-in user actually has permission to run, a chip that returns an access error on the first click destroys trust.