FAQ

No. The AI only writes a draft. Publishing takes two answers from you — P, then Y to confirm the destination — even when the post-commit hook started the review. Without a terminal to ask, nothing is published. See Security.

No. The CLI sends a description of the commit — repository name, hash, branch, message, author and the number of files and lines changed. No diff, no file contents, no file names. See what is sent.

Yes — the title and the summary, before you publish. Type E at the draft. Suggested tags can’t be edited, and aren’t published. See Editing a draft.

Nothing is lost. The draft was saved on your machine when it was generated, and every edit since. Run kairo review in the same repository to reopen it — as long as you haven’t made a new commit in the meantime. See Draft recovery.

Yes. kairo uninstall removes the post-commit hook from a repository and leaves the rest of your hook as it was. To remove the CLI itself, sign out first so the token is revoked, then uninstall the package:

kairo logout
npm uninstall -g kairo-cli

See Uninstall for the full steps.

Yes, one per project. Each Kairo project connects to one GitHub repository, and a repository can belong to only one project. Connect each repository to its own project, and run kairo install in each one where you want automatic build logs. kairo review works out the project from the repository you run it in.

Yes. Run kairo login on each one. Every machine gets its own token, and signing out on one doesn’t affect the others.

Not from the CLI. kairo review always works on the latest commit (HEAD). You can still write any build log by hand on the website.

You get the same build log back. Kairo keeps one build log per commit per project, and reviewing a commit that already has one prints its link instead of writing a new draft.

Not yet. Kairo finds your project from a GitHub origin remote, and repositories are connected through Kairo’s GitHub App.