Get started / Overview

Kosuke documentation.

Sensei runs the execution in the cloud and turns it into a generative experience across all your devices. You keep the decisions. Software is where Kosuke starts: describe a change, Sensei builds it on a branch of your GitHub repository, you try it in a live Preview, and your team merges the pull request.

Open app.kosuke.ai and follow the Quickstart, or watch the Sensei tutorial first.

How a change reaches your repository

  1. Import a GitHub repository as a project.
  2. The import starts the project's first deploy. The deploy agent works out how to run your app and starts it in a sandbox. This happens once per project.
  3. Press New Session and describe the change in plain language.
  4. The agent works on its own branch and sandbox. Try the change in the Preview, read the diff, and send corrections while it works.
  5. Ask the agent to open a pull request. Merge the pull request on GitHub, and the session moves to Completed.

How Kosuke works follows one session through these steps.

Find your starting point

You want toRead
Take one repository to its first pull requestQuickstart
Ship a change without writing codeMake a change without writing code
Run several changes side by side and review the diffsRun several changes at once, Review the changes
Work in chat sessions every dayChat sessions and tasks, Messages, Up next and steering
Set up AI providers, members and billing as an adminAI providers, Members and roles, Plans and billing
Connect your coding agent to KosukeIntegrate Kosuke
Drive Kosuke from your own coding agent or a scriptConnect your coding agent (MCP), Kosuke CLI, the Kosuke API
Look up a wordGlossary

Get help

Email support@kosuke.ai. For common problems and their fixes, see Troubleshooting.

Next steps