Search saved contexts by keyword or natural language query. Returns matching context summaries ranked by relevance using hybrid keyword + semantic search. Searches across titles, reasoning, code snippets, file paths, and commit SHAs. Results include local contexts and (if authenticated) cloud workspace contexts including team-shared contexts. Use for finding past decisions, understanding why code was written, or discovering relevant prior work. Use gitwhy_get <context_id> to read the full context. CLI alternative: `git why search "<query>"`.

Upload local contexts to the GitWhy cloud as private (not shared with team). Use after saving contexts locally to back them up to the cloud. Synced contexts remain private until explicitly published with gitwhy_publish. CLI alternative: `git why push <context-id>` (syncs specified contexts as private).

List available context checkpoints. Shows all saved contexts available for multi-agent workflows. Args: limit: Maximum number of contexts to return (default 20, max 100) offset: Number of contexts to skip for pagination (default 0) name_pattern: Filter contexts by name (case-insensitive substring match) include_descriptions: Include full descriptions in output (default False for compact listing) ctx: MCP context (automatically provided) Returns: Dict with list of available contexts and their details Examples: >>> await list_contexts() {'success': True, 'total': 3, 'contexts': [...]} >>> await list_contexts(limit=5, name_pattern='investigation') {'success': True, 'total': 2, 'contexts': [...]}

Provides reference information on the term "beneficiary" or "beneficiaries" Provides reference information on the term "beneficiary" or "beneficiaries" This tools provides reference information in the "referenced_tools" schema @return: a json object

Browse saved contexts and the domain/topic tree structure. Use to discover what contexts exist in this repo. Call with no args to see the domain/topic hierarchy. Add filters to drill down into a specific domain or topic. CLI alternative: `git why tree` (tree view) or `git why log` (list view).

Gets a web app. Requires the resource name in the format: enterprises/{enterpriseId}/webApps/{webAppId}.