Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

fix: improve AI Bridge request logs UI/UX#21252

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
jakehwll wants to merge30 commits intomain
base:main
Choose a base branch
Loading
fromjakehwll/ai-bridge-request-logs-improvements

Conversation

@jakehwll
Copy link
Contributor

@jakehwlljakehwll commentedDec 12, 2025•
edited
Loading

Closes#21052 and is related to#21218

This pull request implements a bunch of changes the team requested to improve the overall user experience when navigating to the Request Logs page. Since these are mostly UI changes, screenshots do a much better job of showing what's different than me trying to explain everything in words, so I've included them below.

Warning

More globally we've changed how we're rendering<PaginationHeader />, therefore we've renamed it to<PaginationAmount />. This will effect multiple layouts however its a global improvement we're intentionally looking to make.

Preview

ai-bridge-improvements

Changes

  1. Date formatting set to a standardised way including the month as aMMM (i.eDec)
  2. Names and avatars are now rendered larger, furthermore they render the.name field falling back on.username.
  3. Font-size increased fromtext-xs totext-sm to increase overall legibility globally.
  4. Initiator is now rendered inside of a<Badge /> and gives longer names a chance to render.
  5. Models are now rendered in a<Badge /> alongside their icons.
  6. Input/Output tokens are in a shared<Badge />-group alongside truncation (when necessary).
  7. Badge from5 is rendered with the proper name being visible on hover (for use if truncated).
  8. Move globally theShowing X of X counts to the bottom of the tables (effects other components outside of AI Bridge).
  9. Icons are now included within the dropdown for theProvider filter.
  10. Truncation of elements is now handled so larger prompts don't cause the table to require further scrolling.
  11. New merged Input/Output<dt> element with the badge
PositionPull-request
✅fix: improve AI Bridge request logs UI/UX
feat: add AI Bridge request logs model filter
fix: promote AIBridge fromExperimentalHandler

chatgpt-codex-connector[bot] reacted with thumbs up emoji
@jakehwlljakehwll changed the titlefix: AI Bridge request logs UI/UX improvementsfix: improve AI Bridge request logs UI/UXDec 12, 2025
<>
<TableRow
className="select-none cursor-pointer hover:bg-surface-secondary"
className="select-none cursor-pointer"
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Need to have a discussion here if we still want to have ahover: effect. It directly clashes with the<Badge /> backgrounds. I can't say I love that.. YOMV.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Let's stick to the default hover style for tables and only highlight the borders (e.g. see the workspace list)

jakehwll reacted with heart emoji
Copy link
Member

@matifalimatifali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I am not sure if showingInitiator is a good idea in UI. We do not use this word anywhere in Coder UI, and it may confuse users on what is this new term,

@chrifro and@dannykopping for your thoughts?

Comment on lines +28 to +38
constcustomisedDateLocale:Intl.DateTimeFormatOptions={
// Hide the year from the date
year:undefined,
// Show the month as a short name
month:"short",
day:"numeric",
hour:"2-digit",
minute:"2-digit",
second:"2-digit",
hour12:true,
};
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

We need to decide if we're going to standardise against this, feels strange to have it just in the<RequestLogsPageView />. YOMV but I don't love the fact that we're no longer just relying on the browser to decide the output. Especially enforcing 12 hour time.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I agree we need to standardise it. What are the downside of not using the browser to decide the output? How do other companies solve this?

My take: The date format of e.g. Dec 15, highly increases readability through different local standards. So I'd very much like to make that the new standard. For the time, I'm less opinionated and we can follow whatever works best on the technical side. Does that work for you? :)

Once we agreed, could you open a follow-up issue to update the change globally?

@jakehwlljakehwll marked this pull request as ready for reviewDecember 15, 2025 01:11
@chrifro
Copy link

I am not sure if showingInitiator is a good idea in UI. We do not use this word anywhere in Coder UI, and it may confuse users on what is this new term,

@chrifro and@dannykopping for your thoughts?

agreed. I'm also in favor of keeping "users" for consistency

@dannykopping
Copy link
Contributor

I am not sure if showingInitiator is a good idea in UI. We do not use this word anywhere in Coder UI, and it may confuse users on what is this new term,
@chrifro and@dannykopping for your thoughts?

agreed. I'm also in favor of keeping "users" for consistency

The terminology was very carefully chosen. We're leaving the door open for the future when non-human actors might initiate requests. Let's please keep it as initiator.

@matifali
Copy link
Member

I am not sure if showingInitiator is a good idea in UI. We do not use this word anywhere in Coder UI, and it may confuse users on what is this new term,
@chrifro and@dannykopping for your thoughts?

agreed. I'm also in favor of keeping "users" for consistency

The terminology was very carefully chosen. We're leaving the door open for the future when non-human actors might initiate requests. Let's please keep it as initiator.

OK, I am OK with this. I was mainly concerned about introducing a new term without describing what it means. Let's also document this and add a tooltip with the link. This will help users discover it on their own without sending us questions.

dannykopping reacted with thumbs up emoji

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

Reviewers

@matifalimatifalimatifali left review comments

@chrifrochrifrochrifro left review comments

@jaaydenhjaaydenhAwaiting requested review from jaaydenh

@aslilacaslilacAwaiting requested review from aslilac

At least 1 approving review is required to merge this pull request.

Assignees

@jakehwlljakehwll

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AI Bridge: Truncate long prompts in request logs view

5 participants

@jakehwll@chrifro@dannykopping@matifali
[8]ページ先頭
©2009-2025 Movatter.jp