Repository navigation
v1.3.0
A Home for the project, a Graph view, and what cogit itself costs
Added
-
The map has a Graph view beside the git view: the work recorded on the project's code, peeled like an onion. It opens on all the sessions; a click goes inside a session to its branches and inside a branch to its messages, each in a lane colour, and the trail above it or Esc steps back (Open in place opens them where they are instead). Parts are linked when they touched the same code files, a rare file counting for more than one everything touches. Picking a file in the Files panel narrows it to the work on that file and the files it imports or is imported by; All files goes back. A ringed part landed a commit; Show files draws the files and their imports, Show commits the commits as squares. Clicking a message opens its card, the same one the git view opens. The git view's own buttons stay in place, disabled, so the toolbar does not move. The map remembers per project, in the browser, which view and side panel were open and where you were in the Graph view, so a refresh or a switch between the views comes back to it. The import links come from the code graph graphify writes; cogit only reads it, and
cogit initsays whether it found one, offers to build one when graphify is installed (--graph/--no-graph), or prints how to add it. -
A message's card has a folded Related section: up to three other branches, in this or another session, that worked on the same code files, rare files counting for more, with the files they share. A click opens that branch's message that touched most of them.
-
In the git view, picking a file in the Files panel fades the sessions and messages that did not touch it, while the panel is open; All files clears it. The picked file is the same one the Graph view is drawn around, so switching views keeps it.
-
The map has a Home view beside the git and Graph views: the project at a glance. On top, messages and thought commits per day; in the middle the decisions recorded (and how many the agent took on its own, without asking), the options turned down, what cogit itself cost, and the five most discussed files (a click opens the git view on that file); below, a year of thought commits a square a day, like a GitHub profile, where a square opens that day's first one.
-
cogit notes what its own background runs cost (recording, the closing review, Shapes, captured work): the cost and tokens Claude Code reports for each run go to
.cogit/state/spend.jsonl, local to the machine and never shared. The map's Home adds them up.
Changed
- The map's Files list shows code files only, in both views: documents, config, lockfiles and build folders are left out (by the code graph when there is one, by name otherwise), and it has a search box.
cogit log --filestill answers for any path.