Skip to content
Back to search

cogit

MarketplaceWorks with Claude CodeGitHub

cogit: Cogito, ergo commit. Git for the intent behind agent-written code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/erensrtky/cogit with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/erensrtky/cogit'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/erensrtky--cogit/badge.svg)](/listings/erensrtky--cogit)

HTML

<a href="/listings/erensrtky--cogit"><img src="/api/listings/erensrtky--cogit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need Node 22.13+, Claude Code 2.1.275+ and a git repository.

npm install -g @cogit/cli

Then, in Claude Code:

/plugin install cogit --marketplace erensrtky/cogit

To get plugin updates on their own, turn on auto-update once: `/plugin` → Marketplaces → cogit → Enable auto-update. Claude Code leaves it off for marketplaces outside its own.

If the map stays empty, run `cogit doctor`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "cogit",
  3. "description": "cogit: Cogito, ergo commit. Git for the intent behind agent-written code.",
  4. "owner": { "name": "Eren Sertkaya" },
  5. "plugins": [
  6. {
  7. "name": "cogit",
  8. "source": { "source": "github", "repo": "erensrtky/cogit", "ref": "plugin" },
  9. "description": "Records what each session decided and why, and renders it as a static map."
  10. }
  11. ]
  12. }
README.md · README · 182 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center"><img src="docs/images/cogit-mark.svg" width="96" alt="cogit"></p>
  2. # cogit
  3. **Git for the intent behind agent-written code.**
  4. <p align="center">
  5. <a href="https://www.npmjs.com/package/@cogit/cli"><img src="https://img.shields.io/npm/v/@cogit/cli?label=npm" alt="npm version"></a>
  6. <a href="https://github.com/erensrtky/cogit/stargazers"><img src="https://img.shields.io/github/stars/erensrtky/cogit" alt="GitHub stars"></a>
  7. <a href="LICENSE"><img src="https://img.shields.io/github/license/erensrtky/cogit" alt="MIT licence"></a>
  8. <a href="docs/guide/getting-started.md"><img src="https://img.shields.io/badge/works_with-Claude_Code-D97757" alt="Works with Claude Code"></a>
  9. <a href="docs/guide/codex.md"><img src="https://img.shields.io/badge/works_with-Codex_CLI-000000" alt="Works with Codex CLI"></a>
  10. </p>
  11. <p align="center"><img src="docs/images/cogit-descartes.jpg" width="360" alt="René Descartes with git branches running through his hair"><br><i>Cogito, ergo commit.</i></p>
  12. cogit records every message you send to an AI coding agent as a *thought commit*: what you
  13. asked, what came of it, and the message it answered. Your code commits point back to the
  14. thought behind them, so `cogit why` takes any line of code back to the reason it exists.
  15. Agent memory helps your agent remember. cogit helps you understand.
  16. It runs as a plugin in your coding agent and works through its hooks, so the record is written
  17. while you work, not reconstructed from the diff afterwards.
  18. **[Click through a saved map](https://erensrtky.github.io/cogit/demo/)**: no install, no server.
  19. It's the page `cogit open` writes, built from sample data and read-only.
  20. ## Why
  21. I started by copying code out of ChatGPT, then moved to browser tools, editor extensions and now
  22. terminal agents. Each step moved the code further from me, and I kept feeling something was
  23. slipping away. When you write code yourself, it sinks in bit by bit: you know why that table
  24. exists and why you wrote that class. When an agent writes it, that feeling goes away.
  25. The information isn't really gone. It sits in your messages, the agent's replies and your commits,
  26. just in separate places. cogit ties them together, so you can always walk back and see why
  27. something was done. It helps most when you juggle projects: I run 5-10 agents at once across 2-3
  28. of them, and a few minutes later I can lose track of what I did where.
  29. <img src="docs/images/why-abstraction.png" alt="A conceptual chart from machine code to software factories: abstraction keeps rising, while how much of the why you can still trace falls sharply once AI starts writing code. cogit keeps what falls away.">
  30. It's bigger than one person's memory: a reviewer sees what changed, not why.
  31. [More, with research and sources](docs/guide/why.md).
  32. cogit isn't:
  33. - **Agent memory** (OpenViking, Mem0): that helps your agent recall what you talked about.
  34. - **A token saver** (RTK, Headroom): that sends the model less.
  35. - **A code map** (graphify): that shows how a codebase fits together.
  36. - **An orchestrator** (Herdr, Conductor): that runs many agents at once.
  37. - **A planning framework** (BMAD, Spec Kit): that decides what to build next.
  38. - **An AI review bot** (CodeRabbit, Greptile): that comments on whether a diff looks right.
  39. It answers the one question they leave open: why is this code the way it is? I use several of
  40. them alongside it.
  41. ## See it
  42. <img src="docs/images/map.png" alt="The map: sessions as a git graph, each with its messages, branches, commit chips and a left off here marker">
  43. *Your sessions as a git graph — one row per message, the decision behind it, and where you left
  44. off.*
  45. <img src="docs/images/shape.png" alt="A message opened on its Shape tab: a flowchart of what the change does, under the tabs Intent, Shape and Code">
  46. *A message that landed commits opens as Intent, Shape and Code: why it happened, a picture of
  47. what the change does, and the diff.*
  48. <img src="docs/images/tasks.png" alt="The Tasks panel: suggested items with Accept and Dismiss, open items with Done, and a Done section">
  49. *Tasks — work that came up in a session and didn't get finished, caught when the session closes.
  50. You accept, dismiss or close each one.*
  51. <img src="docs/images/files.png" alt="The Files view: a changed file opened, listing the messages that touched it with each message's reason and the option it rejected">
  52. *A changed file opens its history: every message that touched it, and the reason behind each —
  53. including the option that was rejected.*
  54. ## What it does
  55. - **Every message becomes a thought commit**: the question, the outcome, the decisions with
  56. their reasons and the options that were rejected, and which earlier message it continues.
  57. - **A map of your sessions**: a git graph of your conversations with branches, decisions, a
  58. "Your turn" inbox, and Resume and Fork buttons that copy the command to reopen a chat or
  59. continue it as a new one.
  60. - **Commits point back to their reason**: a `Thought:` trailer on each commit;
  61. `cogit show <sha>`, `cogit blame` and `cogit why` follow it back.
  62. - **Intent, Shape, Code**: a message that landed commits shows why it happened, a small
  63. picture of what the change does (a diagram, a before/after or interface table, an example
  64. or plain steps), and the diff, in one place.
  65. - **Tasks**: when a session ends, a small model catches the work that came up and didn't get
  66. finished as a few user-level items; you accept, dismiss or close them (`cogit captures`, and
  67. on the map). Off by default: `cogit config set captures true`.
  68. - **Pull request descriptions with the decisions**: `cogit pr` writes the goal, the
  69. decisions and the rejected options, never the raw chat. `cogit pr --install-action` adds a
  70. GitHub Action that posts them on every pull request.
  71. - **Teams share the record through git**: after a pull, your teammates' sessions are on the
  72. map too, with who ran them and what changed most.
  73. - **The agent's own reasons, or the cheapest record**: a small model records in the
  74. background and never interrupts the agent. By default, when a session ends, the model it ran
  75. on reopens the whole conversation and corrects the record with what only it saw, for about
  76. one more message. Economical leaves it all to the small model: under 2 cents per 20 messages
  77. in our measurement.
  78. - **No server, no account**: it runs on your machine. Nothing leaves it unless you say so: `cogit
  79. init` asks whether to share the record (titles, decisions and reasons) with your team. If you
  80. do, `git push` sends it to your own repository, outside your branches, so it never shows up in
  81. a pull request or `git status`. Your chats stay local, `cogit prune` deletes old sessions, and
  82. key and token patterns are redacted.
  83. - **The agent gets the context too**: a new session starts where the last one left off, and
  84. the agent can look up what was decided and rejected with `cogit why`. It works alongside
  85. memory tools; it doesn't replace them.
  86. ## Install
  87. You need Node 22.13+, a git repository, and Claude Code 2.1.275+ or Codex CLI 0.167+.
  88. ```bash
  89. npm install -g @cogit/cli
  90. ```
  91. Then, in Claude Code:
  92. ```text
  93. /plugin install cogit --marketplace erensrtky/cogit
  94. ```
  95. To get plugin updates on their own, turn on auto-update once: `/plugin` → Marketplaces →
  96. cogit → Enable auto-update. Claude Code leaves it off for marketplaces outside its own.
  97. In Codex, from a terminal:
  98. ```bash
  99. codex plugin marketplace add erensrtky/cogit --sparse .agents
  100. codex plugin add cogit@cogit
  101. ```
  102. Then start Codex in a project and accept the hooks review it shows; Codex asks again after
  103. every cogit update. Details in [Codex](docs/guide/codex.md).
  104. If the map stays empty, run `cogit doctor`.
  105. ## Quick start
  106. ```bash
  107. cd your-project
  108. cogit init # a few questions: git, transcript retention, team setup, language
  109. ```
  110. Work with Claude Code or Codex as usual; recording needs nothing from you. Then open the map:
  111. ```bash
  112. cogit open .
  113. ```
  114. ## Guide
  115. - [Getting started](docs/guide/getting-started.md): what `init` asks, your first session,
  116. setting up a team
  117. - [The map](docs/guide/map.md): sessions, branches, the inbox, files, search,
  118. resuming and forking a session
  119. - [Reading the lineage](docs/guide/reading-the-lineage.md): `log`, `show`, `blame`, `why`,
  120. `search`
  121. - [Pull requests](docs/guide/pull-requests.md): `cogit pr`
  122. - [Teams and git](docs/guide/teams-and-git.md): what is shared, the trailer, the hooks
  123. - [Recording and cost](docs/guide/recording-and-cost.md): who writes the record, what it
  124. costs
  125. - [Loops, sandboxes and agent factories](docs/guide/loops-and-sandboxes.md): recording
  126. `claude -p` loops and sandboxed runs
  127. - [Codex](docs/guide/codex.md): installing in Codex, the hooks review after each update,
  128. `codex exec`, limits
  129. - [Privacy](docs/guide/privacy.md): what is recorded and what never leaves your machine
  130. - [Settings](docs/guide/settings.md): every setting, explained
  131. - [Troubleshooting](docs/guide/troubleshooting.md)
  132. - [FAQ](docs/guide/faq.md): questions people asked after the launch
  133. - [Why cogit](docs/guide/why.md): AI made code faster and review slower
  134. The record format is in [docs/format.md](docs/format.md).
  135. ## Licence
  136. MIT — see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.