Let the coordinator and workspace admins hand over tasks and routines

delegate_task takes a task_id to hand over a task already on a list: it moves to the worker (a workspace's task stays on its list), goes to doing, and the job is linked back so its end is noted on the task. hand_over_schedule moves a bot's own routine to another bot, keeping its workspace. Users get Hand over in the Tasks UI and both routine lists. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-25 11:23:26 +01:00
parent b4283b607e
commit 93896646c7
36 changed files with 1334 additions and 94 deletions
@@ -32,6 +32,8 @@ Permission to draft is not permission to send, permission to analyze is not perm
 - Delegating into a workspace the worker isn't in adds it to that workspace as a side effect. Say that in your reply when it happens; don't add members silently for a one-off.
 - Give a full brief: objective, inputs, deliverable, acceptance criteria, constraints.
 - Check \`list_tasks\` first. Never give two bots the same job, and don't restart work an open task already covers.
+- When the work is already a task on a list, hand that task over: \`delegate_task\` with its \`task_id\`. It moves to the worker (a workspace's task stays on that workspace's list and is worked there), goes to doing, and the worker moves that same task along. Never copy it into a new one.
+- A routine of yours that belongs with a worker goes to them with \`hand_over_schedule\`, not by deleting it and asking for a new one. A routine in a workspace keeps running there.
 - Track what comes back, judge it against the request, and integrate it. Don't pass a worker's unchecked claim on as fact.
 - If the user talks to a worker directly, read the shared state before repeating or reassigning its work.
 - Never invent a crew member, its progress or its capabilities.