> ## Documentation Index
> Fetch the complete documentation index at: https://docs.backant.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Kairos is an autonomous Claude Code harness. Keep Claude Code working on your repo around the clock — with memory that survives across sessions.

Kairos is the autonomous Claude Code harness in the BackAnt suite. It wraps your existing Claude Code installation and keeps it working against any git repository you point it at, on your own machine, without supervision.

<Info>
  Kairos ships as the `backant-kairos` npm package. Most users install it via `npx backant-kairos` from inside the repo they want it to work on.
</Info>

## What it does for you

While you sleep, in another window, on a long flight — Claude Code is still working:

* **Closes your issue backlog.** Reads issues, implements them, opens PRs.
* **Addresses PR review feedback.** Reviewer left a comment at 11pm? Patch ready by morning.
* **Fixes failing CI.** When a check goes red, Claude Code investigates and pushes a fix.
* **Applies refactors across the codebase.** Rename a field, update a convention — Claude Code carries it through every file.
* **Catches regressions before they merge.** Reviews diffs against what it knows about the codebase, flags the ones that contradict prior decisions.
* **Plans multi-PR work.** Breaks larger changes into shippable epics, sequences them, ships one at a time.

You wake up to a queue of PRs ready for your review.

## What makes it different from vanilla Claude Code

Two features:

<CardGroup cols={2}>
  <Card title="Persistent memory" icon="brain">
    Decisions, conventions, validated assumptions, and prior failures survive across sessions. Recall is hybrid — lexical, semantic, and lifecycle signals — and runs entirely on your machine.
  </Card>

  <Card title="Offline consolidation" icon="moon">
    Periodically, Kairos runs a *dream pass* — a structured consolidation that links related observations, distills durable lessons, and stages candidates for your review.
  </Card>
</CardGroup>

## Local-first by design

Embeddings, indexing, and recall happen on your machine. No codebase content is sent to a third party for memory operations. The only outbound traffic is:

* Claude reasoning calls via your existing Claude Code installation
* GitHub operations via `gh` against the repos you authenticate
* A small periodic heartbeat to validate your BackAnt subscription

See [Privacy and data](/kairos/privacy) for the full breakdown.

## When to use it

Kairos pulls weight on long-running codebases where:

* Conventions need to be re-applied across many changes
* Recurring chores (flaky tests, PR feedback, refactors) add up
* You want Claude Code to remember yesterday's decisions and apply them today

For one-shot exploration, a regular Claude Code session is the right fit.

## Next steps

<CardGroup cols={2}>
  <Card title="Installation" icon="download" href="/kairos/installation">
    Install Kairos and walk through the first-run setup.
  </Card>

  <Card title="Daily use" icon="terminal" href="/kairos/daily-use">
    Start, stop, watch, and inspect the harness.
  </Card>
</CardGroup>