Skip to content

feat(chat): change available agent error message ( Issue #4034) #4045

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 69 commits into
base: development
Choose a base branch
from

Conversation

Derikyan
Copy link
Contributor

@Derikyan Derikyan commented Jun 6, 2025

Description:

  1. Single agent mode:
    If the agent is unavailable, show:
    "Agent is unavailable. Please change the agent [link ID] to continue."

  2. Compare mode (two agents):
    If both agents are unavailable, show:
    "Agents are unavailable. Please change the agents [link ID] and [link ID] to continue."

  3. When displaying agent names:

    • If the model name is available, show it.
    • If not, show the reference instead.

Issues:

UI changes

Before:
Снимок экрана 2025-06-06 в 19 09 43
Снимок экрана 2025-06-06 в 19 09 35

After:
Снимок экрана 2025-06-11 в 20 02 17
Снимок экрана 2025-06-11 в 20 00 17
Снимок экрана 2025-06-11 в 19 58 41

Checklist:

  • the pull request name complies with Conventional Commits
  • the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
  • the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
  • I confirm that do not share any confidential information like API keys or any other secrets and private URLs

@Derikyan Derikyan self-assigned this Jun 6, 2025
@Derikyan Derikyan added the enhancement New feature or request label Jun 6, 2025
@Derikyan
Copy link
Contributor Author

Derikyan commented Jun 6, 2025

/deploy-review

Environment: review-environment | pipeline
Overlay E2E tests status: success
Chat E2E tests status: failed

@nartovm
Copy link
Contributor

nartovm commented Jun 6, 2025

/deploy-review

Environment: review-environment | pipeline
Overlay E2E tests status: success
Chat E2E tests status: success

@Derikyan
Copy link
Contributor Author

Derikyan commented Jun 7, 2025

/deploy-review

Environment: review-environment | pipeline
Overlay E2E tests status: success
Chat E2E tests status: success

irinakartun
irinakartun previously approved these changes Jun 9, 2025
@Derikyan Derikyan enabled auto-merge (squash) June 9, 2025 10:58
@Derikyan
Copy link
Contributor Author

Derikyan commented Jun 18, 2025

/deploy-review

Environment: review-environment | pipeline
Chat E2E tests status: failed
Overlay E2E tests status: failed

@Derikyan
Copy link
Contributor Author

Derikyan commented Jun 19, 2025

/deploy-review

Environment: review-environment | pipeline
Chat E2E tests status: failed
Overlay E2E tests status: failed

@Derikyan
Copy link
Contributor Author

Derikyan commented Jun 19, 2025

/deploy-review

Environment: review-environment | pipeline
Chat E2E tests status: failed
Overlay E2E tests status: failed

@Derikyan
Copy link
Contributor Author

Derikyan commented Jun 19, 2025

/deploy-review

Environment: review-environment | pipeline
Overlay E2E tests status: success
Chat E2E tests status: success

@Derikyan Derikyan requested a review from IlyaBondar June 19, 2025 11:40
@Derikyan Derikyan disabled auto-merge June 19, 2025 11:41
@Derikyan Derikyan enabled auto-merge (squash) June 19, 2025 11:41
@Derikyan Derikyan disabled auto-merge June 23, 2025 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants