Personal tasks.

Your Personal space is a workspace only you belong to, so its tasks use the Tasks routes. The /api/personal-tasks endpoints below are deprecated: they keep working for CLIs released before personal reached the workspace routes, and will be removed. Do not build on them.

Your Personal space

kosuke tasks list|create|get|update|delete|move|start personal reads your Personal space id with kosuke user personal-space get (GET /api/user/personal-space, which answers { data: { id } } and makes the space on first use), then calls the same workspace route with that id as workspaceId. Every flag of the workspace command works, and the answers are workspace tasks. GET /api/tasks lists your Personal space beside your workspaces.

Only you reach your Personal space: another member's credential is refused with 403, and their GET /api/tasks never lists your tasks. Sensei reaches it for you. A session or Cron credential acts in its own workspace and has no Personal space, so personal is refused there.

kosuke tasks create personal --title "Send Q3 invoices to Giulia" --due-on 2026-11-03
kosuke tasks list personal --status todo,in_progress --include-open-count true
kosuke tasks update personal <taskId> --status in_progress
kosuke tasks move personal <taskId> --org-id <workspaceId>

Create needs only title; description is optional and defaults to an empty string. All legacy create, update, list, move and start inputs remain available.

Two things to know about the workspace routes:

• ifRevision accepts the task's descriptionRevision, which tasks get prints; a sessionless task also accepts its updatedAt for compatibility. A changed task answers 409 TASK_CONFLICT.
• Errors carry the TASK_* codes of Tasks.

Deprecated endpoints

What follows describes /api/personal-tasks, for a client that still calls it.

The task

A personal task has no repository, branch, sandbox or pull request. Sensei works on it in its thread.

File and edit

Create takes title and optional description, priority, status, dueOn and threadId. It answers 201 with { data: PersonalTask }. A threadId must name one of your own Sensei threads. From a Sensei Turn, the task joins the Turn's thread unless threadId names another.

Update takes any of the same fields. Send dueOn or threadId as null to clear it. Add ifRevision, the task's updatedAt as you read it, to write only over the task you read. When the task changed since, nothing changes and the answer is 409 with the current task in task. Delete answers 204.

List

List answers { data: PersonalTask[], meta: { pagination: { pageSize, hasMore, nextCursor } } }, newest first. Pass nextCursor as cursor for the next page. limit is at most 100.

Move into a workspace

Move takes orgId, a workspace you belong to. The personal task becomes that workspace's Todo task, with its title, description and priority, and you as its Assignee. A due date becomes the description's last line, such as Due 3 Nov 2026. The personal task is removed in the same step. Move answers { data: { orgId, taskId } }, where taskId is the new workspace task.

Limits

• A Done personal task does not move.
• A workspace task never becomes personal.
• Sandbox, Cron and Slack credentials reach no personal task. Sensei can file, read, edit and move them, but not delete one.

Errors

Responses and errors has the full table.

Next steps

• Tasks
• Sensei