中风险
未指定负责人时会强制把新任务分配给当前用户
原文依据：3 处发现了什么
创建流程把“帮我创建一个任务”等普通请求解释为必须将当前登录用户设为负责人，即使用户只要求创建任务、并未选择负责人。它还会读取当前用户的 open_id 并写入任务。
为什么需要注意
新任务可能意外进入用户的负责事项，影响责任归属、任务列表、提醒和团队对负责人的判断。
该风险有依据，但适用范围比标题更窄：当用户说“给我创建”或普通的“帮我创建”时，流程把当前登录用户设为负责人，即使用户没有明确选择负责人，并会读取其 open_id 后写入任务。这可能造成意外负责人分配及通知。文档同时要求确认摘要、截止日期、负责人和清单，并在写入前确认意图；用户可要求作者把负责人作为明确确认项，或先用 dry-run 预览。
1. Confirm with the user: task summary, due date, assignee, and tasklist if necessary. - **Crucial Rule for Assignee**: If the user explicitly or implicitly says "create a task for me" (给我创建一个任务), or "help me create a task" (帮我新建/创建一个任务), you MUST assign the task to the current logged-in user. You can get the current user's `open_id` by executing `lark-cli auth status` (it already outputs JSON by default, so do not add `--json`) or `lark-cli contact +get-user` first, extracting `.identities.user.openId` (from `auth status`) or `.data.user.open_id` (from `contact +get-user`), and then passing it to the `--assignee` parameter.2. Execute `lark-cli task +create --summary "..." ...`3. Judge success by `ok == true` in the stdout JSON (the success envelope has no `code` field — do not test `code == 0`), then report the result: task ID (`data.guid`) and summary.查看另外 2 个位置
| `--description <text>` | No | Detailed description of the task || `--assignee <id>` | No | Assignee ID. Use user `open_id` like `ou_xxx` for people, or app ID like `cli_xxx` for apps. || `--follower <id>` | No | Follower ID. Use user `open_id` like `ou_xxx` for people, or app ID like `cli_xxx` for apps. |> [!CAUTION]> This is a **Write Operation** -- You must confirm the user's intent before executing.