Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

fix: tighten task tool usage guidance

Browse Source
This commit is contained in:
Keisuke Hirata 2026-05-23 05:11:48 +09:00
parent 8662ca404f
commit 4dec7f916f
No known key found for this signature in database
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
crates/tools/src/task.rs
View File

@ -252,24 +252,25 @@ struct TaskUpdateTool {
store: TaskStore, store: TaskStore,
} }
const CREATE_DESCRIPTION: &str = "Create a session-lifetime task for short-term current-work \ const CREATE_DESCRIPTION: &str = "Create a session-lifetime task only when user-visible \
tracking, not project management. Tasks are user-visible real-time status for work with a \ progress tracking is genuinely useful: multiple active tasks must be remembered, or the work \
concrete goal that needs multiple meaningful steps, such as implementation, debugging, \ will involve long edits, long-running commands, extended investigation, or interruption-prone \
investigation, or structured review. Do not create tasks for simple questions, brief answers, or \ coordination. Do not create a task just because a request has several steps, and do not create \
single-step actions. Input only `subject` and `description`; `taskid` is assigned automatically \ one for short questions, quick checks, single reviews, or one-off commands. Prefer updating an \
and initial `status` is `pending`."; existing active task over creating a duplicate. Input only `subject` and `description`; `taskid` \
is assigned automatically and initial `status` is `pending`.";
const LIST_DESCRIPTION: &str = "List every session-lifetime task, including completed and \ const LIST_DESCRIPTION: &str = "List every session-lifetime task, including completed and \
deleted entries. Tasks are user-visible real-time status for short-term current-work tracking. \ deleted entries. Tasks are user-visible real-time status for short-term current-work tracking. \
Takes an empty object as input."; Takes an empty object as input.";
const GET_DESCRIPTION: &str = "Get one session-lifetime task by `taskid`. Tasks are \ const GET_DESCRIPTION: &str = "Get one session-lifetime task by `taskid`. Tasks are \
user-visible real-time status for short-term current-work tracking. Returns an error if the task \ user-visible real-time status for short-term current-work tracking. Returns an error if the task \
does not exist."; does not exist.";
const UPDATE_DESCRIPTION: &str = "Update an existing session-lifetime task as progress changes \ const UPDATE_DESCRIPTION: &str = "Update an existing session-lifetime task when meaningful \
between meaningful steps. Tasks are user-visible real-time status for multi-step work; keep \ progress changes between substantial steps. Tasks are user-visible real-time status, so avoid \
status current with `pending`, `inprogress`, `completed`, or `deleted`. Provide `taskid` and at \ churn for trivial substeps. Keep status current with `pending`, `inprogress`, `completed`, or \
least one of `status`, `subject`, or `description`; deletion is logical (`status = deleted`). If \ `deleted`. Provide `taskid` and at least one of `status`, `subject`, or `description`; deletion is \
an unexpected problem blocks progress, do not force the next step: leave the task as-is, \ logical (`status = deleted`). If an unexpected problem blocks progress, do not force the next \
summarize the problem to the user, and end the turn."; step: leave the task as-is, summarize the problem to the user, and end the turn.";
#[async_trait] #[async_trait]
impl Tool for TaskCreateTool { impl Tool for TaskCreateTool {