You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!--
Ensure the title clearly reflects what was changed.
Provide a clear and concise description of the changes made. The PR
should only contain the changes related to the issue, and no other
unrelated changes.
-->
Fixes OPS-3173.
Deployed on UX
The idea is to let LLM decided whether it has enough context or no. In
case AI decides that name is generated we set it as chat name. In case
there is no enough data, we wait for the next LLM response and try to
generate the name once again
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Chat name generation now includes an `isGenerated` flag to indicate
whether a name was successfully generated or a default was used.
* **Bug Fixes**
* Improved chat name generation reliability with enhanced validation and
structured output handling.
* **Chores**
* Updated chat name API response format from `chatName` to include
`name` and `isGenerated` fields for better clarity on generation status.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
You are an AI assistant on the OpenOps platform, where users interact about FinOps, cloud providers (AWS, Azure, GCP), OpenOps features, and workflow automation.
2
2
3
-
Your task:
4
-
Given the following conversation, suggest a short, descriptive name (max five words) that best summarizes the main topic, question, or action discussed in this chat.
3
+
Task:
4
+
Analyze the provided conversation and attempt to produce a concise chat name describing the main topic, question, or action.
5
5
6
-
Guidelines:
7
-
- The name should be specific (not generic like "Chat" or "Conversation"), and reflect the user's intent (e.g., "AWS Cost Optimization", "Create Budget Workflow", "OpenOps Integration Help").
8
-
- Limit the name to five words or less.
9
-
- Respond with only the chat name.
6
+
Rules:
7
+
- If you can confidently produce a specific, helpful name (not generic like "Chat" or "Conversation"), set `isGenerated` to true and provide `name`.
8
+
- The `name` must be five words or fewer
9
+
- If there is insufficient information, the content is unclear, or you cannot determine a good name, set `isGenerated` to false.
10
+
11
+
Notes:
12
+
- Keep the name short and specific.
13
+
- Avoid quotes, punctuation-heavy outputs, or trailing spaces in the name.
0 commit comments