Skip to main content

Run several changes at once

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​

Open the project's board and press New Session (⌘J), or New Backlog (⌘⇧J) to file work for later.

  1. In the dialog, choose Start now or Backlog.
  2. Describe the change. Attach a screenshot or a file if it helps.
  3. Press Start session, or Add to backlog.

Repeat for each change. To start a Backlog session later, open its card and press Start session, or drag it to Active.

When every sandbox slot is taken, Kosuke opens the Sandbox Limit Reached dialog. Pick the sessions to stop, and the new one starts. Preview and sandboxes explains the dialog, and Plans and billing lists the limits.

Track them on the board​

The board has one column per status, from Backlog through Active, Under Review and Completed to Archived. Archived stays hidden until you add it in the status filter. Each card shows its Assignee and, once one is open, its pull request with the state of its checks.

Filter the board by status, Assignee, priority or label, or press / to filter by title. Chat sessions and the board covers every column 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 Kosuke CLI and from your coding agent through the MCP server. Service logs can only be read in the app. For example, this files a Backlog session:

kosuke sessions create <projectId> --title "Sort invoices by date" \
  --content "Sort the invoices table by date, newest first." --status backlog

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​