Skip to content

feat: Show provider information in the UI (#408)#483

Open
zainabnaseer1164 wants to merge 5 commits intonextcloud:mainfrom
zainabnaseer1164:feat/show-provider-info-in-ui
Open

feat: Show provider information in the UI (#408)#483
zainabnaseer1164 wants to merge 5 commits intonextcloud:mainfrom
zainabnaseer1164:feat/show-provider-info-in-ui

Conversation

@zainabnaseer1164
Copy link

Shows which AI provider will process each task type in the Assistant UI, so users know which provider handles their request.

Copy link
Member

@julien-nc julien-nc left a comment

Choose a reason for hiding this comment

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

Hi! Thanks for the PR!

  • Could you explain a bit more what you did?
  • Could you provide a screenshot (useful to get an idea of what should be checked/tested)?
  • Could you sign your commits? You can set a global GPG key for git (see the GPG Introduction section of https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work) and then follow the instructions of the failing DCO GitHub action)
  • Could you generate the OpenAPI specs? (the openapi composer script does that)
  • Could you move the new provider info in a place where the layout is not affected? Like next to the task type title? Right now it takes a lot of vertical space.
  • There's something wrong with some characters, can you check that?
Image

Feel free to ask questions if something I said was not clear.

'optionalInputShapeEnumValues' => [],
'optionalInputShapeDefaults' => [],
'optionalOutputShape' => [],
'optionalOutputShapeEnumValues' => [],
Copy link
Member

Choose a reason for hiding this comment

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

Is that fixing something else?

Copy link
Author

Choose a reason for hiding this comment

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

@julien-nc

It was added only to keep the chatty-llm task type in line with other task types that already have optionalOutputShapeEnumValues. It wasn’t fixing a bug or part of the provider-info feature. The current branch doesn’t add it; only preferredProviderName is added there.

@zainabnaseer1164 zainabnaseer1164 force-pushed the feat/show-provider-info-in-ui branch from 9f16d8c to 70e19d7 Compare March 4, 2026 05:29
- Compute preferred provider per task type in AssistantService
- Add preferredProviderName to task type API response
- Display provider name next to task type title in assistant form

Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
Made-with: Cursor
Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
- Add preferredProviderName (string|null) to TaskProcessingTaskType schema
- Matches API response for issue nextcloud#408

Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
Made-with: Cursor
Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
… load

- TaskTypeSelect: show 'TaskName · ProviderName' in dropdown and tooltip
- ContextChatInputForm: default contextChatIndexingComplete to false for standalone page
- AssistantTextProcessingForm: remove extra blank line (lint)

Refs: nextcloud#408
Made-with: Cursor
Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
@zainabnaseer1164 zainabnaseer1164 force-pushed the feat/show-provider-info-in-ui branch from 53d717b to 52fb038 Compare March 4, 2026 09:35
@zainabnaseer1164
Copy link
Author

Is that fixing something else?

Hi! Thanks for the PR!

  • Could you explain a bit more what you did?
  • Could you provide a screenshot (useful to get an idea of what should be checked/tested)?
  • Could you sign your commits? You can set a global GPG key for git (see the GPG Introduction section of https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work) and then follow the instructions of the failing DCO GitHub action)
  • Could you generate the OpenAPI specs? (the openapi composer script does that)
  • Could you move the new provider info in a place where the layout is not affected? Like next to the task type title? Right now it takes a lot of vertical space.
  • There's something wrong with some characters, can you check that?
Image Feel free to ask questions if something I said was not clear.

@julien-nc

Could you explain a bit more what you did?
Implemented #408: backend adds preferredProviderName per task type; API/OpenAPI expose it.
UI shows it next to the task type title and in the dropdown as “TaskName · ProviderName”.
Also fixed the standalone Assistant page by defaulting contextChatIndexingComplete.

Could you provide a screenshot?
I have attached the screenshot for your reference showing the provide name next to task.
image

Could you sign your commits?
DCO sign-off has been added to all commits on this branch.

Could you generate the OpenAPI specs?
Openapi.json already includes preferredProviderName in this PR.

Could you move the new provider info next to the task type title?
Provider is shown next to the task type title in the top bar on the same line.

There’s something wrong with some characters – can you check that?
I’ll fix display so apostrophes (e.g. “OpenAI’s”) show correctly instead of wrong one. So I will do it once I get approval from your side.

Copy link
Member

@julien-nc julien-nc left a comment

Choose a reason for hiding this comment

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

Thank you for the adjustments!

Openapi.json already includes preferredProviderName in this PR.

But the OpenAPI CI action is still failing because the specs were not generated again so they are out of date.

UI shows it next to the task type title and in the dropdown as “TaskName · ProviderName”.

I think adding the provider name in the dropdown is a bit too much. It is enough to have it in the form title. Wdyt?

I’ll fix display so apostrophes (e.g. “OpenAI’s”) show correctly instead of wrong one.

I can see it's displayed correctly now, did you fix it already?

Image

So I will do it once I get approval from your side.

Sure if there is still a visual issue, you have my approval to fix it.

<EditableTextField :initial-text="selectedTaskType.name ?? ''" />
<span v-if="selectedTaskType.preferredProviderName"
class="session-area__top-bar__provider">
{{ t('assistant', 'Provider:') }} {{ selectedTaskType.preferredProviderName }}
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
{{ t('assistant', 'Provider:') }} {{ selectedTaskType.preferredProviderName }}
{{ t('assistant', 'Provider: {name}', { name: selectedTaskType.preferredProviderName }) }}

Better for RTL languages.

Run composer run openapi so committed spec matches CI generator.

Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
Made-with: Cursor
Per review: provider name only next to task type title, not in dropdown.

Signed-off-by: zainabnaseer1164 <zainab.naseer1164@gmail.com>
Made-with: Cursor
@zainabnaseer1164
Copy link
Author

Thank you for the adjustments!

Openapi.json already includes preferredProviderName in this PR.

But the OpenAPI CI action is still failing because the specs were not generated again so they are out of date.

UI shows it next to the task type title and in the dropdown as “TaskName · ProviderName”.

I think adding the provider name in the dropdown is a bit too much. It is enough to have it in the form title. Wdyt?

I’ll fix display so apostrophes (e.g. “OpenAI’s”) show correctly instead of wrong one.

I can see it's displayed correctly now, did you fix it already?

Image > So I will do it once I get approval from your side.

Sure if there is still a visual issue, you have my approval to fix it.

@julien-nc above comments have been tackled along with passing all pending GitHub test.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants