Skip to main content

Run several changes at once

Work is filed as a task by Sensei. Open Tasks above Files in the workspace sidebar: Todo, In progress and Done (last 7 days). Cards open the task modal; Open chat opens the execution. The New session button and ⌘J / ⌘⇧J shortcuts are gone.

File with kosuke tasks create <orgId> --hint-project <projectId> --title "<title>" --description "<work>". Check duplicates with kosuke tasks list <orgId> --status todo,in_progress; Sensei can use kosuke tasks list --status todo,in_progress. Only members and Sensei may omit the hint. Sandbox and Cron callers need a hint and --reason. Start with kosuke tasks start <orgId> <taskId> --project-id <projectId> --skill ship. A draft starts in its original repository. MCP ship needs a session target; a task without a session must use tasks start.

See File now, start later and Tasks endpoints. Legacy sessions create --status backlog remains supported.

Task lists are paginated. Follow meta.pagination.nextCursor with --cursor until null, and read each full description with kosuke tasks get <workspaceId> <taskId> before judging overlap; lists omit draft prompts.

Run several changes at once, each in its own chat session. Every session works on its own branch, with its own sandbox and Preview. You review one while the agent works on the next. Your plan sets how many sandboxes run at the same time.

Start several sessions​

Ask Sensei to file each change as a task. Open each task modal, set its Repository row in the Run group, then press Start: Start stays disabled until a Repository is set.

Track them on the Tasks page​

The workspace Tasks page has one column per status: Todo, In progress, Done and Archived. Each card shows its Assignee and, once one is open, its pull request with the state of its checks. The sidebar lists each repository's sessions too.

Filter the Tasks page by Repository, Assignee or priority, or search by title. Chat sessions and tasks covers every status and move.

Review one while the agent works on the next​

Open a session whose turn has finished. The other sessions keep working.

  1. Open the Changes tab. Pick Last Turn, Uncommitted, Remote commits or Branch to choose which changes you see.
  2. Comment on any line that needs work. Unresolved comments go out with your next message.
  3. Open the Preview tab and try the change in the running app.
  4. Send your feedback, or press Open PR when the change is ready.

Review the changes covers the diff, comments and editing files by hand.

Read a failing service's logs​

When something breaks in the Preview, read the logs of the service that failed.

  1. In the Preview tab, press Show logs, or press Ctrl+`.
  2. Pick Full logs, Setup or one service.
  3. Press the filter icon, Toggle log filter, and type to keep only the lines you need.
  4. Press Copy logs and paste the lines into your message to the agent.

Drive sessions from your terminal​

Starting and filing sessions, reviewing the diff and its comments, and opening a pull request also work from the Sensei CLI and from your coding agent through the MCP server. Service logs can only be read in the app. For example, this files a Todo task:

kosuke tasks create <orgId> --hint-project <projectId> --title "Sort invoices by date" \
  --description "Sort the invoices table by date, newest first."

To open a pull request from a script, send /kosuke:open-pr to the session as a message, or $kosuke:open-pr when the session runs a Codex model. Through the MCP server, the submit tool picks the right one for you.

Next steps​