Skip to content

[UX]: make onboarding and dashboard errors more actionable #125

@MatrixAdventurer

Description

@MatrixAdventurer

Summary

Many onboarding and dashboard errors are technically accurate but not actionable enough for end users.

Problem

Messages like these often leave users unsure what to do next:

  • invalid API key
  • email not received
  • no memories found
  • auth failed
  • connection failed

Suggested improvement

For user-facing onboarding/dashboard errors, include the next recommended action directly in the message.

Examples:

  • Invalid API key -> tell the user where to create/regenerate one
  • Email not received -> suggest Spam/Junk/Promotions + resend
  • No memories found -> suggest checking filters or usage page
  • Connection failed -> suggest verifying API URL / key

Why this matters

  • Reduces support burden
  • Lowers onboarding drop-off
  • Makes the product feel more reliable and self-explanatory

Expected behavior

Important user-facing errors should explain both:

  1. what went wrong
  2. what the user should do next

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions