Skip to content

Commit 3177bc4

Browse files
committed
fix (tasks): tasks name issue
1 parent 6a90bdf commit 3177bc4

2 files changed

Lines changed: 2 additions & 9 deletions

File tree

src/client/utils/taskUtils.js

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -46,15 +46,6 @@ export function getDisplayName(task) {
4646
if (task.name === "Proactively generated plan" && task.description) {
4747
return task.description
4848
}
49-
// Fallback to the original prompt from the first run if description is also generic/missing
50-
if (
51-
task.name === "Proactively generated plan" &&
52-
task.runs &&
53-
task.runs.length > 0 &&
54-
task.runs[0].prompt
55-
) {
56-
return task.runs[0].prompt
57-
}
5849
return task.name || "Untitled Task"
5950
}
6051

src/server/workers/planner/prompts.py

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@
2727
2828
Your output MUST be a single, valid JSON object that follows this exact schema:
2929
{{
30+
"name": "A short, clear, and concise task name (title) that summarizes the goal.",
3031
"description": "A concise, one-sentence summary of the overall goal of this plan.",
3132
"plan": [
3233
{{
@@ -41,6 +42,7 @@
4142
}}
4243
4344
Final Instructions:
45+
- Create a concise `name` for the task.
4446
- Create a concise `description` summarizing the overall goal.
4547
- Break down the goal into logical steps, choosing the most appropriate tool for each.
4648
- If an action item is not actionable with the given tools (e.g., "Think about the marketing report"), do not create a plan for it.

0 commit comments

Comments
 (0)