Context Tree

How it works

Every saved context is placed into a hierarchical domain → topic tree:

.gitwhy/contexts/
 │── authentication/                                                                                                                               
 │   │── jwt-implementation/                                                                                                                       
 │   │   └── ctx_a1b2c3d4.md  "JWT implementation setup"                                                                                           
 │   │── oauth-flow/                                                                                                                               
 │       └── ctx_e5f6g7h8.md  "OAuth flow configuration"                                                                                           
 │── database/                                                                                                                                     
     └── migration-strategy/                                                                                                                       
         └── ctx_m3n4o5p6.md  "PostgreSQL migration strategy"        

Domains group related work (authentication, database, payments). Topics narrow the focus within a domain.

Browse the tree

CLI
TUI
Web Dashboard
MCP

git why tree

Output:

main
  authentication/
    jwt-implementation/
      ctx_a1b2c3d4  "JWT implementation setup"
  api-design/
    rate-limiting/
      ctx_i9j0k1l2  "Rate limiting middleware"

In a terminal, git why tree opens an interactive tree browser with expand/collapse navigation.

TUI tree view showing domain and topic hierarchy

Expand and collapse domains and topics to explore contexts across branches.

You: "What contexts exist in the authentication domain?"

Agent: [calls gitwhy_list(domain="authentication")]
GitWhy: [returns domain/topic tree with context summaries]

Auto-categorization

When your agent saves context, it can specify the domain and topic:

gitwhy_save(markdown, domain="authentication", topic="jwt-implementation")

If not specified, GitWhy auto-categorizes based on the title and files changed. Uncategorized contexts go to uncategorized/general/.

Getting Started

Core Features

Sharing & Collaboration

Interfaces

Integration Guide

CLI Reference

Context Format

Plans & Pricing

How it works

Browse the tree

Auto-categorization

​How it works

​Browse the tree

​Auto-categorization

How it works

Browse the tree

Auto-categorization