Git for the intent behind agent-written code. Records what your coding agent decided and why, and links every commit to it.
JavaScript ai-codingclaudeclaude-codeclaude-code-pluginclicoding-agentsdeveloper-toolsgitllmtypescript
cogit guide
The README shows what cogit is and how to start. This guide explains each part in detail.
| Page | What it covers |
|---|---|
| Getting started | Install, what cogit init asks, your first session, setting up a team |
| The map | Sessions, branches, the "Your turn" inbox, files, search, resuming or forking a session, the people filter |
| Reading the lineage | log, show, blame, why, search in the terminal, and how the agent uses them |
| Pull requests | cogit pr: a review-ready description with the decisions behind the code |
| Teams and git | What is shared, the Thought: trailer, the git hooks, teammates' records |
| Recording and cost | Who writes the record, the side model, what it costs |
| Privacy | What is recorded, what never is, what leaves your machine |
| Settings | Every setting with a plain-language explanation |
| Troubleshooting | Nothing is recorded, the map looks old, the port is taken, and more |
| Why cogit | The review bottleneck AI coding created, with sources |
The record format itself (the .cogit/ layout, message ids, events, the trailer) is in
docs/format.md, with JSON Schemas in docs/schema/.