Repository navigation
v1.1.0
Every message gets a summary
Every message now gets a one-line summary of what came of it, so a message that only discussed or advised no longer keeps just its title. Existing setups get it once; turn it off again with cogit config set messageSummaries false.
This page also covers 1.0.1, which had no page of its own: fixes from testing 1.0 end to end (a live Claude Code session pushed through a real remote, a 10,000-session map, git 2.20 and your own git hooks).
Upgrade: npm i -g @cogit/cli@1.1.0 and claude plugin update cogit. Your git hooks update on your next chat message.
1.1.0
Changed
- Every message now gets a one-line summary of what came of it (
messageSummariesis on by default, and turned on once for existing setups). Without it, a message that only discussed or advised kept nothing but its title, so the map and search lost what the agent said. Turn it off withcogit config set messageSummaries false; it then stays off.
Fixed
- With a hooks folder shared by every repository (a global
core.hooksPath), cogit's hooks no longer act in repositories that are not the project: a commit there no longer takes the project'sThought:trailer, and a push there no longer announces the project's records. - With Husky, cogit's hook blocks no longer vanish for good after
npm install(Husky rewrites.husky/_): the next chat message puts them back.cogit hooks uninstallis remembered, so blocks you removed on purpose stay out. - A session the side model left untitled takes its first thread's title (or its first message's) at session end, instead of showing only its id on the map and in
cogit log;cogit logalso stops printing such an id twice.
1.0.1
Fixed
- A git hook of your own that ended with
exit 0, or read the push's input, no longer stops cogit: its block now sits at the top of the hook, hands git's input on to your lines, and adds theThought:trailer after them. Existing hooks move on the next chat message; a Python or Node hook is left alone andcogit doctorsays so. git push --dry-runno longer sends the record (Linux and macOS).- The first download of a team's records shows git's progress meter without one line per session (300 sessions printed over 600 lines), and when it fails,
cogit doctorshows git's reason instead of "the download failed". - After upgrading from a version that committed the record,
cogit doctorasks you to commit the rewritten.cogit/.gitignoretoo; without it teammates and new clones saw.cogit/sessions/ingit status. - A map with thousands of sessions no longer freezes on "Unfold all" and "Fold all": only the open sessions near the screen are drawn, and the session list no longer does quadratic work (10,000 sessions: 11 s down to 2 s).
cogit init --helpandcogit config git --helpnamed the removedcommitpolicy; they now sayshareorignore.cogit prandcogit show <sha>no longer tell a reviewer that a teammate's thought is "not recorded yet" when it may never arrive: for someone else's commit they say it is not in this clone's record, because its author has not pushed it or it came from a fork.cogit buildin a fresh clone of a shared project downloads the team's sessions first, instead of writing an empty map.- The map's outline follows the search: it marks and scrolls to the hit you are on, and scrolls to a message you click on the map.
- Git older than 2.29 can download the team's records again: cogit no longer passes it
--no-write-fetch-head, and a failed download names git's error instead of a line of its usage text. - A Shape diagram in the message panel keeps legible text: it shrinks to the panel's width but not below half size, and a tall or wide one scrolls inside its box instead of shrinking until the labels cannot be read.
- A message is no longer lost from the record when the side model gets one of its fields wrong, or (in mixed mode) writes a field that belongs to the agent: only that field is left out, and the message keeps its title, summary and the rest.
- A chat that commits into another repository no longer stamps that commit with a
Thought:trailer the other repository can never resolve: the trailer is added only when the chat runs in the project being committed (or in that working tree). - The agent is told at session start that the
Thought:trailer comes from cogit, so it stops warning you about a line it did not write.