← Back to Blog

See how your project got here: commits, sessions and tests on one timeline

November 9, 2026 · 5 min read

Ask "what happened on this project last week?" and the answer is spread across tools. Commits are in Git, the reasoning is in a dozen coding-agent sessions, the test results scrolled off a terminal, and the release is a tag somebody pushed on Friday. git log tells you what changed, but not which session produced it, whether the tests passed afterwards, or what's still waiting to be pushed.

L2Cache already records your agent sessions, commands and Git activity on your Mac. Each project in its Projects section brings those together in one place: a Project Story of commits, sessions and runs, a short overview of where things stand, and milestones that say exactly how sure they are.

Project Story: graph and timeline

Open a project and the Project Story section has two views:

• Graph: the project's commit graph, with branches and merges, and a detail panel for the selected commit. It says plainly when something unusual is going on: a detached HEAD, a merge or rebase in progress, a shallow clone, or no remote.
• Timeline: the same history as a list, with everything else that happened around it.

The timeline mixes kinds of events that normally live apart:

So you can see that a failing test run came right after a particular session, and that the fix landed two commits later.

Read from .git, never run

L2Cache reads your repository's files directly: the reflogs and the object store inside .git. It never runs git, never writes to the repository, and drops author and committer identities as it reads. Repositories are found by listing the projects folder you add in Settings; worktrees and submodules count too. If a project has no Git history, the timeline still shows its sessions and runs.

Where the project stands

Above the story, a short overview sums up the project in plain lines. Each line links to the evidence behind it: the branches, commits or runs it's counting. Depending on the project, you'll see lines such as:

• Working on the current branch, and how many commits landed in the last 7 days
• Merges, active branches and recent releases by tag
• Uncommitted files, with when that was last seen
• Commits only on this Mac: work that hasn't been pushed
• Branches pushed but not merged, and unmerged branches idle 30+ days
• Failed commands this week, and unfinished agent tasks
• Commits since the last passing build or test, or No successful build or test recorded on this branch

That last line is the one that saves you from shipping on hope: it tells you how much has changed since anything was last verified.

Milestones that say how sure they are

L2Cache picks out the moments worth remembering: a branch started, a branch merged, tests fixed, a version released, or a big day with an unusual amount of work. Work on one branch is grouped into a journey: when it started, how many commits and sessions it took, and where it was merged.

The important part is that every milestone carries a label saying where the claim comes from:

Milestones are sorted into In progress, Completed this week, Shipped and Earlier, plus Needs evidence for claims nothing confirms yet and Pinned for the ones you want to keep in view.

You stay in charge of the story. You can pin, hide or rename a milestone, correct its type, move it to another project or add a note. The actions on each one depend on what it is and what data backs it: Compare with previous release and Copy release recap for a release, Inspect failure and Continue fixing for a broken build, Open merge commit for a merge, Resume or Open recovery point for unfinished work.

Needs attention

L2Cache's Today page has a Needs attention card that pulls the loose ends from every project into one list:

• The last run failed on a branch you're working on.
• Unpushed commits that exist only on this Mac.
• Waiting for review: branches that are pushed but not merged.
• Idle branches that haven't moved in 30 days, and groups of related branches that may be the same piece of work.

Several items of the same kind in one project collapse into a single line, so the card stays short.

Sharing it

• Weekly recap: a draft built from the last seven days of milestones. Include or leave out items, edit the wording, then Copy as Markdown or Copy for Slack. Mask names swaps project and branch names for neutral ones when you're sharing outside the team.
• Project standup: Copy project standup gives you the last two days of commits and merges, and what's still open, ready to paste.
• Presentation mode: masks project names, paths, prompts and commands on screen while you share it.

All local

Everything here is built from files already on your Mac: your repositories, your agents' session files and L2Cache's own history. Nothing is uploaded, and L2Cache doesn't need access to GitHub or any other host to build it.

For the time side of the same activity, how many hours went to which ticket, see a timesheet and standup from your coding activity. For a picture of how this fits into a working day, see a day in the life of a Mac developer.

The short version

• Project Story shows commits, agent sessions, test runs, recovery points and deploys on one graph and timeline.
• L2Cache reads .git directly. It never runs or writes Git.
• Every milestone is labelled Git verified, Test verified, You noted or L2Cache inferred.
• Needs attention gathers failed runs, unpushed commits and unmerged branches across projects.