File a task and start it later

Ask Sensei to file a task. Tasks live in the workspace's Tasks page, above Files in the sidebar, with Todo, In progress and Done columns. Done shows the last 7 days. There is no New session button or ⌘J shortcut.

File

kosuke tasks list <orgId> --status todo,in_progress
kosuke tasks create <orgId> --hint-project <projectId> --title "Migrate jobs" --description "Move the jobs table and backfill existing rows." --priority high

Check existing descriptions before filing. With a hint, the response includes the task id and session id. The task shows no repository while Todo; the draft keeps its hint internally. Members and Sensei may omit the hint when the repository is unknown. Sandbox and Cron callers must supply the hint and a reason. A hint pointing at a YOLO project files a Backlog item instead.

Edit

kosuke tasks update <orgId> <taskId> --description "Move jobs, backfill rows and remove old columns."

A task without a session has a text-only description, with no attachments or artifacts until it starts.

Start

Open the task modal and press Start. A former Backlog task is fixed to its draft's repository, with “Filed for ”. Otherwise choose a deployed Collaboration repository, then Start.

kosuke tasks start <orgId> <taskId> --project-id <projectId> --skill ship

Only members and Sensei may start tasks. A refused start leaves the task Todo and shows why inline; retry after resolving the refusal. Concurrent starts create one execution. Once started, Open chat opens the conversation.

Sensei keeps the first-deploy rule: when asked to start work before the first Deploy lands, it files with --start-when-deployed and waits for the automatic start.

The older kosuke sessions create <projectId> --status backlog remains supported. MCP ship can target its session, but cannot target a task without a session; use tasks start for that task.

See Tasks reference and Chat sessions.