Skip to content
Docs / Your first build log

Build logs

Your first build log

Commit, run kairo review, read the draft, and publish it. The whole flow, start to finish.

The flow
  1. git commit

  2. kairo review

  3. AI generates a draft

  4. Review

    Read it in the terminal

  5. Edit

    Optional: change the title or summary

  6. Publish

    Type P, then confirm with Y

  7. Visible on Kairo

    Project page and feed

Before you begin#

  • You’re signed in — kairo whoami prints your account.
  • The repository is connected to one of your Kairo projects: on the project’s page, click Connect repository and pick it.
  • Your local clone has an origin remote on GitHub. Check with git remote -v.

Walkthrough#

  1. Commit your work

    git add .
    git commit -m "Add the AI writer"
    

    kairo review always works on your latest commit — HEAD.

  2. Run kairo review

    kairo review
    

    Run it anywhere inside the repository. To run it for another directory, pass -C <path>. It first shows the commit it found:

      ada/lighthouse  main
    
      79de83c  Add the AI writer
               Ada Lovelace · committed 5 minutes ago · 9 files, +612 -14
    
    ✓ Project Lighthouse
    

    Project Lighthouse means Kairo matched the repository to your project. If the commit already has a build log, the CLI says so, prints its link and stops there.

  3. The AI generates a draft

    Kairo’s AI writer drafts a title, a summary and a few tags from the commit. This can take up to a minute; the spinner shows how long it has been.

    ✓ Draft ready. Read it through before you publish.
    
      Generated   24 Sept 2026, 14:03 (just now)
      Model       not reported by Kairo
    
      ────────────────────────────────────────────────────────
    
      Added the AI writer behind kairo review
    
      Kairo now drafts a build log from the latest commit. The CLI
      sends the commit's shape to the backend, a model writes a title
      and a summary, and the draft is shown here before anything is
      published.
    
      #ai  #cli
    
      ────────────────────────────────────────────────────────
    
      [P] Publish   [E] Edit   [D] Discard
    
      >
    

    The draft is saved on your machine as soon as it arrives, so it survives a closed terminal. See Draft recovery.

  4. Review it

    Read it the way a follower would. The AI only knows your commit message and the size of the change — not what the code does — so the summary is a starting point, not the final word.

    Type a letter and press Enter: P to publish, E to edit, D to discard. The full word works too (publish).

  5. Edit it (optional)

    E opens the editor, where you can change the title or the summary, then go back to the draft. Details on the Editing page.

  6. Publish it

    Type P. The CLI asks once more, naming exactly where the build log is going:

      Publish “Added the AI writer behind kairo review”
      to Lighthouse (ada/lighthouse)?
      It will appear on the project's page and in the feed.
    
      [Y] Yes   [N] No  >
    

    Y publishes. N takes you back to the draft, unchanged.

  7. See it on Kairo

    ✓ Published to Kairo.
    
      Project     Lighthouse
      Repository  ada/lighthouse
      Commit      79de83c
      Build log   https://joinkairo.vercel.app/buildlogs/cm1x2y3z4a5b6c7d8e9f0
    

    The build log is now on your project’s page and in the build log feed. Open the link to see it.

What gets published#

The title and summary exactly as they were on screen when you confirmed, linked to that commit. Nothing the AI wrote goes anywhere without that confirmation.

One build log per commit

Kairo keeps one build log per commit per project. Publishing the same commit again — after a dropped connection, say — ends at the same build log instead of creating a second one, so pressing P again is always safe.

Changed your mind?#

D discards the draft. Nothing is published, and the saved copy is deleted. Run kairo review again later to get a fresh draft for the same commit.