Historical user answer to question is inaccessible
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Historical user answer to question is inaccessible. You can expand the question that was asked (although you cannot see the options that were originally given), but for the user's answer, it's hard-coded to an ellipsis on a single line.
I tried changing my verbosity setting to detailed, and it still looks the same.
Expected: support seeing the entirety of a previous answer to a LLM question.
| Field | Value |
|---|---|
| App version | 1.1.14 |
| OS | macOS 26.5.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
Contributor guide
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 at the /chat entry point and reproduce the issue with a historical LLM question whose answer is longer than one line. Compare the displayed historical answer with the expected behavior: the entirety of the previous answer should be accessible, rather than replaced by an ellipsis.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai, desktop
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100