The code viewThe repository with AI in the margin. Built for the specific problem of agents writing a lot of code quickly: understanding what a file is for, what changed, why, and which card did it, without leaving Grid Console.The treeEvery repository in the project, real folders, collapsible, with per-file status: touched by a card, indexed, or not yet indexed. File icons match the language. Files an agent has touched carry the card key that touched them.The fileThe center pane is a code viewer, not an editor: syntax highlighting through tree-sitter, folding, blame, and the language server your project already uses for symbols and references. Above the first line sits a short, generated header: Goal of this file, How it achieves it, and Talks to, with every reference clickable.·Callers and dependencies are shown inline against the lines they belong to, with the call site line number: click to jump straight there, in this file or another.·Where a method has many callers the margin collapses them into a count you can open, so a widely used function does not drown the file.·Plain-language notes appear between the lines where the code is doing something non-obvious. Good existing comments are styled, not replaced.·Select or hover a method and the explanation follows your cursor. The model that writes these is pickable (Haiku for speed, Sonnet for depth).History with the whyNot a list of commits. Each change is grouped by the card that made it, with the card’s intent, the sections of the plan it satisfied, and what changed from that plan. That is the difference between git log and knowing why your file looks like this.Cards on this projectThe right pane lists the cards for the project, with cards that touched the open file grouped on top. Open one and you get the card information in the upper half and its conversation below, the same two panes as the session view. Switching files keeps you on the same card.Right-click, and going back to your editorThe context menu carries the usual moves plus Grid Console’s: explain this, find callers, capture a card here, blame this line, open in editor. Plugins can add their own entries. Open in editor opens the card’s worktree at the current line in VS Code, Cursor, an IntelliJ IDE, Zed, Neovim, or any command you configure.