Kosuke documentation
Kosuke runs an AI coding agent on your GitHub repository in a cloud sandbox. You describe a change in a chat session. The agent writes the code on a branch of its own, and you try the result in a live Preview of your app. The session ends as a pull request that your team reviews and merges on GitHub.
Open app.kosuke.ai and follow the Quickstart, or watch the walkthrough first.
How a change reaches your repository
- Import a GitHub repository as a project.
- Press Deploy. The deploy agent works out how to run your app and starts it in a sandbox. You do this once per project.
- Press New Session and describe the change in plain language.
- The agent works on its own branch and sandbox. Try the change in the Preview, read the diff, and send corrections while it works.
- Press Open PR. 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 to | Read |
|---|---|
| Take one repository to its first pull request | Quickstart |
| Ship a change without writing code | Make a change without writing code |
| Run several changes side by side and review the diffs | Run several changes at once, Review the changes |
| Work in chat sessions every day | Chat sessions and the board, Messages, Up next and steering |
| Set up AI providers, members and billing as an admin | AI providers, Members and roles, Plans and billing |
| Drive Kosuke from your own coding agent or a script | Connect your coding agent (MCP), Kosuke CLI, the Kosuke API |
| Look up a word | Glossary |
Get help
Ask in the Kosuke Discord, or email support@kosuke.ai. For common problems and their fixes, see Troubleshooting.