Team Context Sync

How it works

GitWhy contexts start private — visible only to you. When you share them, your team can browse all shared contexts organized by repository, domain, and topic.

Dashboard showing shared team contexts organized by repo and domain

Browse shared contexts by repo and domain — with search, filters, and team activity in one view.

CLI
MCP
Dashboard

# Sync a context as private (cloud backup)
git why push <context-id>

# Sync and share with team
git why push <context-id> --share

# Sync multiple contexts
git why push ctx_a1b2c3d4 ctx_e5f6g7h8 --share

See the CLI reference for all flags and options.

Sync as private:

Agent: [calls gitwhy_sync()]
GitWhy: Synced 2 context(s) to cloud (private)

Share with team:

Agent: [calls gitwhy_publish(ids='["ctx_a1b2c3d4"]')]
GitWhy: Published 1 context(s) as shared

What your team sees

Your team can browse all shared contexts at app.gitwhy.dev, organized by:

Repository — sidebar navigation
Domain and Topic — tree navigation within each repo
Context cards — title, agent, commit count, time ago

Dashboard context cards with search and filters

Each card shows the title, agent, commit count, files changed, and domain path. Click any card to see the full structured context:

Read the full story, reasoning, and decisions — with tags, branch, agent, and visibility metadata.

Why it matters

When a teammate asks “why was the auth middleware built that way?”, the answer is already there — not buried in someone’s chat history.

Getting Started

Core Features

Sharing & Collaboration

Interfaces

Integration Guide

CLI Reference

Context Format

Plans & Pricing

Team Context Sync

How it works

What your team sees

Why it matters

See also

​How it works

​How to share

​What your team sees

​Why it matters

​See also

How it works

How to share

What your team sees

Why it matters

See also