Skip to content

optional: nicer apollo errors for lightning users#4879

Draft
taylordowns2000 wants to merge 2 commits into
mainfrom
nicer-errors
Draft

optional: nicer apollo errors for lightning users#4879
taylordowns2000 wants to merge 2 commits into
mainfrom
nicer-errors

Conversation

@taylordowns2000

@taylordowns2000 taylordowns2000 commented Jun 18, 2026

Copy link
Copy Markdown
Member

Description

This PR makes it possible to show more detailed errors to AI chat users. Right now, all a user ever sees (regardless of whether the error is related to billing, AI service provides, or anything else) is this:
image

Validation steps

  1. Boot up lightning with a faulty AI assistant token.
  2. Try to send a message to the AI chat.
  3. See a nicer error.

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our
Responsible AI Policy

Pre-submission checklist

  • I have performed an AI review of my code (we recommend using /review
    with Claude Code)
  • I have implemented and tested all related authorization policies.
    (e.g., :owner, :admin, :editor, :viewer)
  • I have updated the changelog.
  • I have ticked a box in "AI usage" in this PR

@github-project-automation github-project-automation Bot moved this to New Issues in Core Jun 18, 2026
@lmac-1

lmac-1 commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

@theroinaochieng another one that need clarity on how to prioritise/move forward. Not sure if this belongs in an issue that references this PR as an idea for the solution. And then we can prioritise with the issue.

@taylordowns2000

Copy link
Copy Markdown
Member Author

@theroinaochieng another one that need clarity on how to prioritise/move forward. Not sure if this belongs in an issue that references this PR as an idea for the solution. And then we can prioritise with the issue.

Thanks for asking, @lmac-1 . It's possible that this was simply missed during the recent re-implementation, or possible that it was actively de-prioritized. I've updated the description to include this image
image

@theroinaochieng will know 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

2 participants