New tasks are forcibly assigned to the current user when no assignee is specified
Source references: 3The creation workflow interprets ordinary requests such as “help me create a task” as requiring the current logged-in user to be the assignee, even when the user only asked for creation and did not choose an assignee. It retrieves the current user's open_id and writes it into the task.
The task may unexpectedly enter the user's assigned workload, changing responsibility, task lists, reminders, and teammates' understanding of ownership.
The risk is supported, though narrower than the title: for phrases such as “create a task for me” or ordinary “help me create a task,” the workflow assigns the logged-in user even when no assignee was explicitly chosen, retrieving and writing that user's open_id. This may create an unintended assignment and notifications. The document also requires confirming task details and intent before writing; users can ask that the assignee always require explicit confirmation or preview via 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.Show 2 other places
| `--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.