AI Assistant: better disabled behaviour
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When the Inspector loads, if Apollo is unavailable, the user will be locked out of editing
Two problems with this:
- It is not at all clear that the UI is disabled, or why, so it just looks broken
- If Apollo comes available again as second after the page loads, the UI won't re-enabled itself
This likely affects offline mode (obviously the assistant should not work offline, but the UI should appear disabled)
I'd love to see stronger disabling of the text input, and some visualisation that Apollo is disconnected/offline, and maybe some kind of regular polling to check apollo's availability.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Inspector load path and how Apollo availability controls the assistant UI. Check the text input's disabled state and the offline or reconnection path; done means the disconnected state is obvious, editing is strongly disabled, and the UI re-enables when Apollo becomes available again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100