# thread_view: Clearer authentication states \(\#45230\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/abb199c85e466222b00d476b8a837fa4c3b3bee1)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: abb199c85e466222b00d476b8a837fa4c3b3bee1

Requested commit: abb199c85e466222b00d476b8a837fa4c3b3bee1

Commit: abb199c85e466222b00d476b8a837fa4c3b3bee1

Tree: 4fbdc6358fb23ee9415315cba35b6d3bc7607b63

Author: Ben Brandt

Committer: GitHub

## Message

```
thread_view: Clearer authentication states (#45230)

Closes #44717

Sometimes, we show the user the agent's auth methods because we got an
AuthRequired error.

However, there are also several ways a user can choose to re-enter the
authentication flow even though they are still logged in.

This has caused some confusion with several users, where after logging
in, they type /login again to see if anything changed, and they saw an
"Authentication Required" warning.

So, I made a distinction in the UI if we go to this flow from a concrete
error, or if not, made the language less error-like to help avoid
confusion.

| Before | After |
|--------|--------|
| <img width="1154" height="446" alt="Screenshot 2025-12-18 at 10 
54@2x"
src="https://github.com/user-attachments/assets/9df0d59a-2d45-4bfc-ba85-359dd1a4c8ae"
/> | <img width="1154" height="446" alt="Screenshot 2025-12-18 at 10 
53@2x"
src="https://github.com/user-attachments/assets/73a9fb45-4e6f-4594-8795-aaade35b2a72"
/> |


Release Notes:

- N/A

---------

Co-authored-by: Danilo Leal <daniloleal09@gmail.com>
Co-authored-by: Miguel Raz Guzmán Macedo <miguel@zed.dev>
```

## Parents

- [cebbf77491faa05f04e9939450e718405fdad93a](https://git.cafe/gitcafe/zed/commit/cebbf77491faa05f04e9939450e718405fdad93a?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/abb199c85e466222b00d476b8a837fa4c3b3bee1?format=markdown)